Tested version: ER3, server After invoking: site --cancelpush backupSite on the producer site, status of the push operation seems to get stuck at "SENDING" value (tested by site --pushstatus), even if state transfer is not currently in progress. Invoking site --cancelreceive mainSite on the consumer site works correctly. New invocation of site --push backupsite leads to "X-Site state transfer to '%s' already started!" being displayed. The issue seems to be caused by XSiteStateTransferManagerImpl.siteCollector not being cleared.
Used configuration: distributed caches, site A: 2 nodes, site B: 3 nodes, B is a backup for A. Scenario - Start A,B - Take B offline using takeSiteOffline - Load data into A - Push state into B - CancelPushState B -- PushStateStatus remains stuck at SENDING & new push is not possible
The issue is fixed and push operation can be reinvoked after it had been cancelled. However, push status remains at value "CANCELLED", even if push operation is reinvoked and state transfer is currently in progress. - Sites LON (lonCache) - main, BRN (brnCache) - backup Consider the following scenario: [standalone@localhost:9999 distributed-cache=lonCache] site --push BRN ok [standalone@localhost:9999 distributed-cache=lonCache] site --cancelpush BRN ok [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus BRN=CANCELED [standalone@localhost:9999 distributed-cache=lonCache] site --push BRN ok [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus BRN=CANCELED [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus BRN=OK IMO expected behavior is: [standalone@localhost:9999 distributed-cache=lonCache] site --push BRN ok [standalone@localhost:9999 distributed-cache=lonCache] site --cancelpush BRN ok [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus BRN=CANCELED [standalone@localhost:9999 distributed-cache=lonCache] site --push BRN ok [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus BRN=SENDING [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus BRN=OK This is obviously a bit confusing, can you please confirm this behavior is expected?
Verified, new bz will be created for aforementioned error.