I have a plugin that was written originally for Elasticsearch 1.x. It has been updated to run in the 2.x series with no problems. When I went to upgrade the plugin to 5.x, I hit a major stumbling block.
In the 2.x version of the plugin I was able to correlate the incoming request with the outgoing response using the
ThreadContext. But this is no longer an option since
ThreadContext was deprecated.
Does anyone know of a way to correlate the incoming request with its outgoing response? The closest I have been able to get to a solution is to use a queue associated with each Netty Channel, pushing on requests and popping them off as responses leave on that channel. But this doesn't have the accuracy I need in our high volume cluster.
Any help is appreciated!