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

do not change the timestamp of a node upon receipt of spoofed data #189

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

plaguedbypenguins
Copy link
Contributor

centrally collected out-of-band data (eg. from BMCs or a blade
chassis) which is then spoofed into the gmond network does not mean
that the node is actually up. unfortunately ganglia's notion of a node
being "up" is based upon the time when data was last received by the
gmond network - the "REPORTED" field in gmond's xml. fix this problem
by not updating the node's timestamp in gmond if the data source is
spoofed data.

users that wish to refresh a node's timestamp with spoofed data
(eg. if a node consists of only spoofed data) can use the -H option
to gmetric to explicitly send a heartbeat message and keep the node
in the "up" state.

centrally collected out-of-band data (eg. from BMCs or a blade
chassis) which is then spoofed into the gmond network does not mean
that the node is actually up. unfortunately ganglia's notion of a node
being "up" is based upon the time when data was last received by the
gmond network - the "REPORTED" field in gmond's xml. fix this problem
by not updating the node's timestamp in gmond if the data source is
spoofed data.

users that wish to refresh a node's timestamp with spoofed data
(eg. if a node consists of only spoofed data) can use the -H option
to gmetric to explicitly send a heartbeat message and keep the node
in the "up" state.
@vvuksan
Copy link
Member

vvuksan commented Feb 12, 2015

This may be an unintended consequence however I imagine some people may be relying on this functionality. I am hesitant to merge this.

How about adding a config option that defaults to the old behavior however it can be enabled via your code.

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

Successfully merging this pull request may close these issues.

2 participants