-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't use hazelcast executor in task scheduling #10122
Comments
vbradnitski
added a commit
that referenced
this issue
Apr 20, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 20, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 20, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 21, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 21, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 21, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 21, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 21, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 21, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 21, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 24, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 25, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 25, 2023
vbradnitski
added a commit
that referenced
this issue
Apr 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use IScheduledExecutorService from Hazelcast to schedule tasks in clustered environments. But it seems to be not stable in some dynamic clusters. So we can't rely on it and the process should be reimplemented.
https://enonic.zendesk.com/agent/tickets/6345
The text was updated successfully, but these errors were encountered: