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

Add an API function to Chain Monitor to get the current best brick of a chain #3

Open
tatsuya6502 opened this issue Feb 14, 2013 · 0 comments
Milestone

Comments

@tatsuya6502
Copy link
Member

This item is related to hibari/hibari-doc#13

There will be some time that we want to know the current best brick of a chain for system administration purpose. To achieve this from Erlang code, the code has to call brick_chainmon:calculate_best_first_brick(#state{}). However this function is not exported and also requires knowledge of Chain Monitor's internal #state record.

Instead of simply exposing that function, create another function, which doesn't require the knowledge of internal #state record.

brick_chainmon:calculate_best_brick(chain_name())

Once this function is added, we could add an hibair-admin command to get the best brick.

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

No branches or pull requests

1 participant