tree 22c4a15d4c72a79ec6be90599be5d7224fa3381d
parent 5890e16ec75053c4d82c1d596e415c2401e5d047
author Marcin Czech <maczech@gmail.com> 1639415861 +0100
committer Marcin Czech <maczech@gmail.com> 1639563446 +0000

Fix issue with skipping events from high-availability

ForwarderTask class keeps caller thread object to identify the source
of the event. All events generated by `HTTP POST
/plugins/high-availability/index/change/...` thread are skipped.

The issue is that all threads in HTTP thread pool are named `HTTP-*`
when HTTP call is made thread is renamed to `HTTP POST
/plugins/high-availability/index/change/...`. During the processing
new thread to send the message is created and current HTTP thread is
returned to the pool and it's name is set back to `HTTP-*`.

This means that if the code is not fast enough to check HTTP thread
name before thread is returned to the pool it will get `HTTP-*`
instead of `HTTP POST /plugins/high-availability/index/change/...`
and the event will be forwarded. To avoid this situation keep the
caller thread name instead of thread object.

Bug: Issue 15416
Change-Id: I76f5921793cf844ad638f920127e8f2848a2615e