-
Notifications
You must be signed in to change notification settings - Fork 823
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
High CPU Usage after switching to CompatibleFieldSerializer #976
Comments
Hi @ankit-harness. Please create a PR that applies the fix to the kryo-4 branch. I had no plans to release another 4.x version, but I will consider it in this case. |
Thank you @ankit-harness! I will try to release a new Kryo 4 version next week. First I have to look through all improvements that were made to Kryo 5 that could potentially be backported. I have not done a release of 4.x since I took over as maintainer of this project. I hope the release process still works after 4 years ;) |
Eagerly waiting for the release with extra goodness. 😀 |
Hi @theigl , any update on this? |
Not yet. I need a couple of hours of spare time to get the 4.x branch into a releasable state again. I'll let you know when I cut the release. |
@ankit-harness: I have just released 4.0.3. I cherry picked and applied two additional fixes concerning Please verify that this release works for you. |
Thanks a lot @theigl . I will try it out. Is artifact uploaded to maven central repo too? |
Yes. It should make it to central in the next hours. |
Describe the bug
We recently switched to CompatibleFieldSerializer in our codebase. After that we have had few instances where a thread ends up consuming very high CPU in our service. We have to restart our service instance to fix that. Here's the stacktrace for the thread -
I think this issue is same as #838. We wanted to try out the fix done for this issue. But, it's not available in 4.0.2 which is the version we are using. Upgrading to 5.x.x is going to be a huge effort as it has breaking changes.
Can we release 4.0.3 with this fix?
The text was updated successfully, but these errors were encountered: