lhotari edited a comment on issue #14436: URL: https://github.com/apache/pulsar/issues/14436#issuecomment-1060324950
> > What's the current assumption of the cause of this issue? > > I'm not working on this issue currently, just because this thread safety issue has existed from the very beginning. If this issue could be reproduced only by Pulsar 2.10, then the cause might not be related to `OpReadEntry`. Ok, so you don't have an assumption of the root cause? @congbobo184 Could you please try running the test case with `-Dio.netty.recycler.maxCapacity=0 -Dio.netty.recycler.maxCapacityPerThread=0` in the broker and in the client (perhaps separately)? [That setting disables the Netty Recycler](https://github.com/netty/netty/blob/51eda20432568ffdf736a673abc6b5a44839413f/common/src/main/java/io/netty/util/Recycler.java#L62-L90). The benefit of the experiment would be that it would reveal new information about the problem if disabling Netty Recycler makes the problem go away. Please be aware that `io.netty.recycler.maxCapacity.default` is not the correct name of the system property. I created #14576 to remove the invalid property name from Pulsar files. -- 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]
