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

[BROKER 3.0.0]One retention file create at lunch #56

Closed
Tpo76 opened this Issue Jul 13, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@Tpo76

Tpo76 commented Jul 13, 2016

With broker 3.0.0 one retention file of 8 Byte is create '/var/lib/centreon-broker/central-rrd-master_central-rrd-master-output.retention'

If you stop broker, erase this file and start broker. It will created again

@ganoze ganoze added this to the 3.0.0 milestone Oct 11, 2016

@ganoze ganoze self-assigned this Oct 11, 2016

@ganoze

This comment has been minimized.

Show comment
Hide comment
@ganoze

ganoze Oct 11, 2016

Collaborator

Indeed there is an issue. When the initialization of the base endpoint is very fast (RRD for instance), the failover thread do not get a chance to provide its events. For the RRD endpoint this only means that the retention file does not get deleted but this could lead to much bigger issues : in case of weird thread scheduling delays the retention events of any endpoint could be unprocessed !

Thank you for pointing it out.

Collaborator

ganoze commented Oct 11, 2016

Indeed there is an issue. When the initialization of the base endpoint is very fast (RRD for instance), the failover thread do not get a chance to provide its events. For the RRD endpoint this only means that the retention file does not get deleted but this could lead to much bigger issues : in case of weird thread scheduling delays the retention events of any endpoint could be unprocessed !

Thank you for pointing it out.

ganoze added a commit that referenced this issue Oct 12, 2016

core: wait for failover initialization when launching them.
In some weird scheduling conditions the failover events do not get
a chance to get read back.

References #56.

@ganoze ganoze closed this Nov 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment