There are a couple of places in the code base that do not respect that j.u.HashMap + related classes are not thread safe and some parts rely on internals of the implementation of HM, which can change.
We have observed failures like NullPointerException and ConcurrentModificationException as well as wrong behavior.
Affected areas in the code base:
- streaming / concurrent access to LifecycleTransaction (handled in
While the patches for the compaction strategies + TypeParser are pretty straight forward, the patch for TokenMetadata.Topology requires it to be made immutable.