LATEST VERSION: 8.1.0 - CHANGELOG
Pivotal GemFire® v8.1

Errors In Delta Propagation

Errors In Delta Propagation

This topic lists the errors that can occur when using delta propagation.

Errors in delta propagation fall into two categories based on how they are handled by the system:
  • Problems applying the delta that can be remedied by requesting the full value in place of the delta. Your put operation does not see errors or exceptions related to this type of delta propagation failure. The system automatically does a full value distribution from the sender to the receiver where the problem occurs. This type of error includes:
    • Unavailable entry value in the receiving cache, either because the entry is missing or its value is null. In both cases, there is nothing to apply the delta to and the full value must be sent. This is most likely to occur if you destroy or invalidate your entries locally, either through application calls or through configured actions like eviction or entry expiration.
    • InvalidDeltaException thrown by fromDelta method, programmed by you. This exception enables you to avoid applying deltas that would violate data consistency checks or other application requirements.
    • Any error applying the delta in a client in server-to-client propagation. The client logs a warning in addition to retrieving the full value from the server.
  • Problems creating or distributing the delta that cannot be fixed by distributing the full value. In these cases, your put operation fails with an exception. This type of error includes:
    • Error or exception in hasDelta or toDelta.
    • Error or exception in a server or peer receiver that fall outside of the situations described above in the first category.