Bug #7932
Synchronization hangs, repeatedly attempting to sync same content
100%
Description
Synchronization stops functioning, repeatedly attempting to synchronize same content. Attempts to shutdown by setting synchronization.active to FALSE in the properties file fails to shut down the process.
e.g.:
[ WARN] 2016-11-14 13:18:01,123 (V2TransferObjectTask:call:232) Task-urn:node:ARCTIC-urn:uuid:ef55f0ef-c5bf-42bf-87ad-fc8f801ade5b - Cannot lock Pid! Requeueing the task. Attempt 486
[ WARN] 2016-11-14 13:18:01,123 (V2TransferObjectTask:call:232) Task-urn:node:ARCTIC-urn:uuid:ef55f0ef-c5bf-42bf-87ad-fc8f801ade5b - Cannot lock Pid! Requeueing the task. Attempt 487
[ WARN] 2016-11-14 13:18:01,123 (V2TransferObjectTask:call:232) Task-urn:node:ARCTIC-urn:uuid:ef55f0ef-c5bf-42bf-87ad-fc8f801ade5b - Cannot lock Pid! Requeueing the task. Attempt 487
Associated revisions
fixes #7932: fixing count incrementation for lock failures.
fixes #7932: fixing count incrementation for lock failures.
History
#1 Updated by Dave Vieglais over 7 years ago
Chris noted in cn.log:
[ WARN] 2016-11-15 13:40:46,545 (?:?:?) [128.111.54.80]:5702 [hzProcess] exception during handling BLOCKING_QUEUE_POLL: java.util.concurrent.TimeoutException: [CONCURRENT_MAP_REMOVE] Operation Timeout (with no response!): 0
com.hazelcast.core.OperationTimeoutException: java.util.concurrent.TimeoutException: [CONCURRENT_MAP_REMOVE] Operation Timeout (with no response!): 0
#2 Updated by Rob Nahf over 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 30
Found bug in the retry code. Was incrementing one attempt counter, but checking another one.
committed fix to 2.3 branch.
#3 Updated by Rob Nahf over 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 30 to 100
Applied in changeset java-client:d1client|r18502.
