Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
Discovery Impl 1.1.0
-
None
Description
With extending the TOPOLOGY_CHANGING phase in SLING-3432 and follow-up tickets such as SLING-4634 and SLING-4635, the correctness of TopologyView.isCurrent() is very important: currently it is not always correctly set. This must be fixed.
Attachments
Issue Links
- blocks
-
SLING-3432 pseudo network partition causes job deserialization issue in a cluster (when reading while job is being reassigned)
- Closed
-
SLING-4635 Topology related jobs shouldn't be scheduled if topology is unclear/not available
- Closed
-
SLING-4634 Directly check if view is still current
- Closed
- relates to
-
SLING-4761 Latest view seems to get marked as not current
- Closed