Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings and logic for Bioyino as an agent #88

Open
syatihoko opened this issue Sep 25, 2024 · 0 comments
Open

Settings and logic for Bioyino as an agent #88

syatihoko opened this issue Sep 25, 2024 · 0 comments

Comments

@syatihoko
Copy link

Configured the agent in front of the Bioyino cluster.

By specifying cluster servers (3 nodes) "List of nodes to replicate metrics to"
nodes = ['server1_VIP1:8136', 'server2_VIP1:8136', 'server3_VIP1:8136']

Each Node has 2 VIP addresses.
I thought about improving the reservation and specified both VIPs and got 6 IP addresses in the nodes parameter.
Example: nodes = ['server1_VIP1:8136', 'server2_VIP1:8136', 'server3_VIP1:8136', 'server1_VIP2:8136', 'server2_VIP2:8136', 'server3_VIP2:8136']
As a result, the metrics are doubled - the quantity increases exactly 2 times.

Now I thought that I didn’t understand the logic of the work correctly.
Did I understand correctly? The pre-aggregated metric is sent to the specified number of servers, and if the server is a master, then it processes them without coordinating with other servers. And the other servers receive a duplicate and throw it away?

That is, metrics delivered in this way only to the slave (ingress-metric-peer) will be discarded and will not be sent to other servers (to the master), unlike receiving incoming metrics (directly - ingress-metric)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant