Bug #3408
Review Hazelcast Executor Service error
Status:
Closed
Priority:
Normal
Assignee:
Robert Waltz
Category:
d1_synchronization
Target version:
Start date:
2012-11-26
Due date:
2013-01-19
% Done:
100%
Milestone:
CCI-1.1.1
Product Version:
*
Story Points:
Sprint:
Description
ERROR] 2012-11-26 20:27:55,159 (MemberNodeHarvestJob:execute:105) ExecutionException: com.hazelcast.core.OperationTimeoutException: [BLOCKING_SIZE] Redo threshold[90] exceeded! Last redo cause: REDO_QUEUE_NOT_READY, Name: q:hzSyncObjectQueue
Received this error after multiple Job failures on MemberNodes that were not responding
History
#1 Updated by Robert Waltz about 12 years ago
- Status changed from New to Closed
Unable to determine root cause due to lack of debugging information. Messages began after a an instance disconnected from the cluster and never appeared to reconnect. Seems to be due to inability of executor service to redirect execution to a connected node.
#2 Updated by Robert Waltz almost 12 years ago
- Due date changed from 2012-12-01 to 2013-01-19
- Target version changed from Sprint-2012.46-Block.6.3 to 2013.2-Block.1.1
- Milestone changed from CCI-1.1 to CCI-1.1.1
