geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Schuchardt (JIRA)" <>
Subject [jira] [Commented] (GEODE-2718) inconsistent reads during network partition
Date Mon, 27 Mar 2017 16:50:41 GMT


Bruce Schuchardt commented on GEODE-2718:

The membership service will need to deliver viewChanged notification to membership listeners
in order for BucketRegion listeners to know if data loss occurred in a single view change.
 Currently they get memberCrashed notifications for individual members but have no way of
knowing if redundant copies of buckets were also lost in the same view.

> inconsistent reads during network partition
> -------------------------------------------
>                 Key: GEODE-2718
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: membership, regions
>            Reporter: Swapnil Bawaskar
> non-persistent partitioned regions exhibit the following behavior:
>  In the event of a network partition where all copies of a bucket end up on the losing
side, a get() operation returns a null. A null can signify that the key did not exist, so
we should be more explicit about the network partition and throw an error like PartitionOfflineException
(which is thrown if the region was persistent).

This message was sent by Atlassian JIRA

View raw message