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

(WIP) Bump seshat #469

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

(WIP) Bump seshat #469

wants to merge 3 commits into from

Conversation

the-mikedavis
Copy link
Member

This is the companion change in Ra for rabbitmq/seshat#12

The changes are:

  • Introduce ra_counters:new/3 which wraps the new seshat:new/4 allowing the caller to specify a seshat:label()
  • Add a field counter_label to the Ra server config and mutable config which allows specifying that seshat:label().

In RabbitMQ we can use this when creating a Ra config to specify the queue resource for QQs and the Ra cluster and system names for other servers like Khepri and the stream coordinator.

The commit hash should be replaced when a new hex version is cut.
This new field sets the `seshat:label()` when creating a new counter for
a server (via `ra_counters:new/3` and in turn `seshat:new/4`).

This also deprecates the `counter` field. Having the creator of a Ra
server pass a `counters:counter_ref()` is unergonomic because the caller
must know the `seshat:fields_spec()` with which the counter should be
created.

Also in this change we remove the call to `ra_counters:new/2` from
the `ra_server_proc:config_defaults()` helper. By calling that function
when creating a default, the server process registered a counter
(causing an insertion into an ETS table in seshat) for the server even
if the caller specified a `counter` in the config.
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.

1 participant