geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3055) data mismatch caused by rebalance. waitUntilFlashed return false
Date Sat, 19 Aug 2017 00:11:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133817#comment-16133817
] 

ASF subversion and git services commented on GEODE-3055:
--------------------------------------------------------

Commit d809076d01c28b9b819ab32d6af172004b3f8740 in geode's branch refs/heads/feature/GEODE-1279
from zhouxh
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d809076 ]

GEODE-3055: Should use a conservative fix to only catch the PartitionOfflineEx
to remove the leader region bucket.

Previous fix to catch all RuntimeException is too aggressive.

This closes #723


> data mismatch caused by rebalance. waitUntilFlashed return false
> ----------------------------------------------------------------
>
>                 Key: GEODE-3055
>                 URL: https://issues.apache.org/jira/browse/GEODE-3055
>             Project: Geode
>          Issue Type: Bug
>            Reporter: xiaojian zhou
>            Assignee: xiaojian zhou
>              Labels: lucene
>             Fix For: 1.3.0
>
>
> /export/buglogs_bvt/xzhou/lucene/concParRegHAPersist-0601-171739
> lucene/concParRegHAPersist.conf
> A=accessor
> B=dataStore
> accessorHosts=1
> accessorThreadsPerVM=5
> accessorVMsPerHost=1
> dataStoreHosts=6
> dataStoreThreadsPerVM=5
> dataStoreVMsPerHost=1
> numVMsToStop=2
> redundantCopies=0
> no local.conf
> In dataStoregemfire5_7483/system.log, thread tid=0xdf, putAll Object_11066
> 17:22:27.135 tid=0xdf] generated tag {v1; rv13 shadowKey=2939
> 17:22:27.136 _partitionedRegionPARALLELGATEWAYSENDER_QUEUE_1 bucket : null // brq is
not ready yet
> is enqueued to the tempQueue
> 17:22:27.272 tid=0xdf] generated tag {v3; rv15 shadowKey=3278
> 17:22:33.111 Subregion created: /_PR/_BAsyncEventQueueindex#partitionedRegionPARALLELGATEWAYSENDER_QUEUE_1
> vm_3_dataStore3_r02-s28_28143.log:
> 17:22:33.120 Put successfully in the queue shadowKey= 2939
> 17:22:33.156 tid=0x7fe started query
> 17:22:33.176 Peeked shadowKey= 2939
> So the root cause is: the event is still in tempQueue before it's processed, the query
happened. WaitUntilFlush should wait until tempQueue is also flushed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message