mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
ed5d60f758
This test was unstable for two reasons: - Nothing verified whether the two workers had checked in with the proxy, meaning that messages between the workers and proxies could get lost. This adds an extra node_up event that the proxy generates synthetically, with values recognizable to the manager, once the proxy sees both workers connected. This is a test-level workaround for what should really be a cluster-is-ready event in the cluster framework proper. - More subtle: the Intel framework makes the manager send its current min_data_store to newly connected workers, which in the case of this tests introduces a race: since the data store, arriving at the worker, replaces the existing value, it could actually remove already established items if timing was right. This would lead to the count in the test reaching 3, assuming that 3 intel items are available, when in reality it was less, causing the Intel::seen() call to do nothing. We now disable the sending of the data store upon connect, via the global added in the previous commit. This also expands the test slightly so that both workers call Intel::seen() for the items inserted by the other worker. This is added validation for the second point above, because in the presence of that race one occasionally sees one log entry make it, and the other fail.
7 lines
384 B
Text
7 lines
384 B
Text
### BTest baseline data generated by btest-diff. Do not edit. Use "btest -U/-u" to update. Requires BTest >= 0.63.
|
|
### NOTE: This file has been sorted with diff-sort.
|
|
new_indicator: 1.2.3.4 inserted by manager
|
|
new_indicator: 123.123.123.123 inserted by worker-1
|
|
new_indicator: 4.3.2.1 inserted by worker-2
|
|
new_item triggered for 4.3.2.1 by worker-2 on worker-2
|
|
seeing 123.123.123.123
|