davidnadeau commented on issue #1761: URL: https://github.com/apache/fury/issues/1761#issuecomment-2251214421
I havn't been able to reproduce this issue outside of my company infrastructure, which is k8s running debian 11. I created a small scala app that uses Fury andTwitter Finagle, and in a loop serializes and deserializes randomly generated Features objects on multiple different threads. However, this code was not able to reproduce any errors. The issue only happens at pod startup, I will see a large surge of errors like: ``` java.lang.NullPointerException: Cannot read field "serializer" because "classInfo" is null at org.apache.==fury==.resolver.ClassResolver.getOrUpdateClassInfo(ClassResolver.java:1151) at org.apache.==fury==.resolver.ClassResolver.readClassInfo(ClassResolver.java:1609) at org.apache.fury.Fury.readRef(Fury.java:825) at org.apache.fury.Fury.deserialize(Fury.java:760) at org.apache.fury.Fury.deserialize(Fury.java:682) at org.apache.fury.pool.ThreadPoolFury.lambda$deserialize$9(ThreadPoolFury.java:135) at org.apache.fury.pool.ThreadPoolFury.execute(ThreadPoolFury.java:79) at org.apache.fury.pool.ThreadPoolFury.deserialize(ThreadPoolFury.java:135) ``` and ``` Failed to deserialize key: ��+mxe���(��(�(� due to exception: java.lang.NullPointerException: Cannot read field "serializer" because "classInfo" is null" ``` Then they subside after a few seconds, and fury serialization/deserialization becomes stable. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
