Skip to content

[Fix] Collision checker concurrent handling#78

Open
shivang1234gupta wants to merge 1 commit intoappform-io:mainfrom
shivang1234gupta:fix/collision-checker-concurrent-issue
Open

[Fix] Collision checker concurrent handling#78
shivang1234gupta wants to merge 1 commit intoappform-io:mainfrom
shivang1234gupta:fix/collision-checker-concurrent-issue

Conversation

@shivang1234gupta
Copy link
Copy Markdown

Issue in concurrent execution of collisionChecker
Example:
Thread t1 get the time Xms, Just before the collisionChecker the clock moved to X+1ms
At the same time thread t2 with current time X+1ms started the collisionChecker, Thread t2 will update the currentInstant to X+1
When thread t1 will execute collisionChecker post t2 it will again reset the currentInstant to X, which will reset the bitset and ID collisions will happen for both X as well as X+1 bucket.

For eg -: Last Id = 0E2509151738525100023932
Duplicated Id = 0E2509151738525080023432, This issue will occur if bitset is resetted

import java.util.concurrent.Callable;
import java.util.concurrent.Executors;
import java.util.*;
import java.util.concurrent.*;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Revert wildcard imports with individual imports. This would raise issues on sonar

@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants