We're updating the issue view to help you get more done. 

ReplicaNoProgressException timing is wrong

Description

When Backup full recovery failed with the following message:
2019-06-23 09:55:03,898 WARNING [com.gigaspaces.space.engine.qaSpace.1_1] - Recovery operation failed: com.gigaspaces.internal.cluster.node.impl.replica.ReplicaNoProgressException: No progress in replica stage for the past 60000 milliseconds; Caused by: com.gigaspaces.internal.cluster.node.impl.replica.ReplicaNoProgressException: No progress in replica stage for the past 60000 milliseconds

The actual time that has been pass is 120000 milliseconds.

See here:

2019-06-23 09:53:03,736 INFO [com.gigaspaces.core.common] - Space [qaSpace_container1_1:qaSpace] trying to perform recovery from [jini://*/qaSpace_container1/qaSpace?groups=yuval-pc&ignoreValidation=true&locators=yuval-pc:4174&state=started]. RecoveryChunkSize=200
2019-06-23 09:55:03,898 WARNING [com.gigaspaces.space.engine.qaSpace.1_1] - Recovery operation failed: com.gigaspaces.internal.cluster.node.impl.replica.ReplicaNoProgressException: No progress in replica stage for the past 60000 milliseconds; Caused by: com.gigaspaces.internal.cluster.node.impl.replica.ReplicaNoProgressException: No progress in replica stage for the past 60000 milliseconds
2019-06-23 09:55:03,918 INFO [com.gigaspaces.space.active-election] - Detected primary Space failure during recovery

Full log is attached.

Workaround

None

Acceptance Test

None

Status

Assignee

Unassigned

Reporter

Yuval Dori

Labels

None

Priority

Critical

SalesForce Case ID

12443

Fix versions

None

Commitment Version/s

None

Due date

None

Product

None

Edition

Open Source

Platform

All