The (Local|Cluster)PublisherManager returns a SegmentCompletionPublisher which has a subscribe method that takes a Subscriber and consumers to be notified of segment completion or lost. These clasess were designed with the fact that the onNext and segment completion or lost would never be invoked concurrently.

Unfortunately, if the onNext is offloaded to a different thread then it is possible for this to occur causing an issue in PublisherHandler which keeps track of remote requests and responses to get in an incorrect state.

Instead we should change the API of (Local|Cluster)PublisherManager to have a subscribe that takes some sort of wrapper where each event may be an entry or a segment completion or lost. This way callers can more easily handle asynchronous operations when handling the Publisher.