[
https://issues.apache.org/jira/browse/GEODE-9484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531895#comment-17531895
]
Anilkumar Gingade commented on GEODE-9484:
------------------------------------------
[~mivanac]
The PR/Fix for this issue is showing up NPE in internal tests. Here is the
stack trace:
java.lang.NullPointerException
at
org.apache.geode.internal.tcp.TCPConduit.getFirstScanForConnection(TCPConduit.java:958)
at
org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:477)
at
org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:277)
at
org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:543)
at
org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:348)
at
org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:293)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2067)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1994)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2031)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1088)
at
org.apache.geode.internal.cache.CreateRegionProcessor.initializeRegion(CreateRegionProcessor.java:115)
at
org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1176)
at
org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1107)
at
org.apache.geode.internal.cache.HARegion.initialize(HARegion.java:323)
at
org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3103)
at
org.apache.geode.internal.cache.HARegion.getInstance(HARegion.java:246)
at
org.apache.geode.internal.cache.ha.HARegionQueue.<init>(HARegionQueue.java:365)
at
org.apache.geode.internal.cache.ha.HARegionQueue$BlockingHARegionQueue.<init>(HARegionQueue.java:2233)
at
org.apache.geode.internal.cache.ha.HARegionQueue$DurableHARegionQueue.<init>(HARegionQueue.java:2478)
at
org.apache.geode.internal.cache.ha.HARegionQueue.getHARegionQueueInstance(HARegionQueue.java:2015)
at
org.apache.geode.internal.cache.tier.sockets.MessageDispatcher.getMessageQueue(MessageDispatcher.java:166)
at
org.apache.geode.internal.cache.tier.sockets.MessageDispatcher.<init>(MessageDispatcher.java:146)
at
org.apache.geode.internal.cache.tier.sockets.CacheClientProxy.createMessageDispatcher(CacheClientProxy.java:1685)
at
org.apache.geode.internal.cache.tier.sockets.CacheClientProxy.initializeMessageDispatcher(CacheClientProxy.java:1677)
at
org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.initializeProxy(CacheClientNotifier.java:502)
at
org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.registerClientInternal(CacheClientNotifier.java:406)
at
org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:221)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$ClientQueueInitializerTask.run(AcceptorImpl.java:1896)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeClientQueueInitializerThreadPool$1(AcceptorImpl.java:678)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
at java.lang.Thread.run(Thread.java:750)
> Data inconsistency in replicated region with 3 or more servers, and one
> server is down
> ---------------------------------------------------------------------------------------
>
> Key: GEODE-9484
> URL: https://issues.apache.org/jira/browse/GEODE-9484
> Project: Geode
> Issue Type: Improvement
> Components: client/server, regions
> Affects Versions: 1.13.0
> Reporter: Mario Ivanac
> Assignee: Mario Ivanac
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> We have configured replicated region with 3 or more servers, and client is
> configured with read timeout set to value same or smaller than member timeout.
> In case while client is putting data in region, one of replicated servers is
> shutdown, it is observed that we have data inconsistency.
>
> We see that data part of data is written in server connected with client, but
> in remaining replicated servers it is missing.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
