As you can see from the namespace and the object names, it's not our code
which causes the stack overflow. It's Kryo code which you're calling and
thus we have not control over it.
And in fact, I doubt that the problem is related to the number of elements
in your map but rather to the structure of
Hi,
I have a complex object with a MutableList and a Map containing
thousands of objects. Here is a snippet of the exception. The actual
exception is much longer. There, you can see that the exception is
caused by too many recursive calls. For each recursive call the stack
size increases becau
Hi Hilmi,
I've never seen such a problem. Could you please provide a bit more
background information. Which types are you serializing? Which serializer
are you using? What do you mean with recursion? Maybe you can provide a
simple example program which reproduces the problem.
The thing is that if
Hi,
I am using flink to train a ML model. There, I need to broadcast huge
broadcast variables in each iteration. During the serialization I get a
Stackoverflow exception. If I increase the Stack size then it works
well. The Stackoverflow could be avoided If you do not use recursion in
serializ
