Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Later
-
None
-
None
-
None
Description
Currently, the duplicate detection logic does not differentiate if the two duplicate updates are from the same rs or different RS.
Have seen issues where a duplicate notification from the same RS, causes the assignment to be considered a duplicate assignment. ... and the region ends up being assigned to no one.
Keep track of where the regions are opened, and make the duplicate detection more accurate.