This repository has been archived by the owner on Jul 25, 2022. It is now read-only.
Temporary solution for race between plugin_runner and device-aggregator #1036
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setup
4 servers, aka 2 DC. first pair holds data(active-active), second - metadata(active-passive)
1 IML server.
Network between Lustre client and servers is
IPoIB
via simple switch.Everything goes in monitored mode.
Problem
Sometimes, in logs seen message:
Usually it happens:
The reason seems to be a race condition between
plugin_runner
anddevice-aggregator-daemon
.First of all, there's no dependency declared between these services in
systemd
unit, and connection goes viaHTTP
.Second, since connection proxies by nginx, it returns 502 if service didn't started yet.
Third, if connection from agent is initiated, it doesn't mean device information has already arrive in parallel. Thus, it is useful to wait for the incoming data.
Signed-off-by: Alex Talker alextalker@ya.ru