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

Default rexi_per_server to true #1625

Closed
davisp opened this issue Sep 26, 2018 · 0 comments
Closed

Default rexi_per_server to true #1625

davisp opened this issue Sep 26, 2018 · 0 comments

Comments

@davisp
Copy link
Member

@davisp davisp commented Sep 26, 2018

; server_per_node = false

A long time ago we weren't super confident in this feature. Its since been shown to be quite solid and a known performance bottleneck when not enabled. We should probably flip the default.

nickva added a commit to cloudant/couchdb that referenced this issue Sep 26, 2018
This has been solid for years and when not enabled can be a performance
bottleneck.

Fixes apache#1625
nickva added a commit to cloudant/couchdb that referenced this issue Sep 26, 2018
This ensures they will be ready to process requests as soon as the application
starts up. This should make the service available sooner and should help tests
which setup and tear down the services repeatedly, where it would avoid an
annoying retry-until-ready loop.

Per-node servers/buffers are started in the init method of the monitors. There
is not chance of deadlock there because per-node supervisors are started before
the monitors.

Issue apache#1625
nickva added a commit to cloudant/couchdb that referenced this issue Sep 27, 2018
This has been solid for years and when not enabled can be a performance
bottleneck.

Fixes apache#1625
nickva added a commit to cloudant/couchdb that referenced this issue Sep 27, 2018
This ensures they will be ready to process requests as soon as the application
starts up. This should make the service available sooner and should help tests
which setup and tear down the services repeatedly, where it would avoid an
annoying retry-until-ready loop.

Per-node servers/buffers are started in the init method of the monitors. There
is not chance of deadlock there because per-node supervisors are started before
the monitors.

Issue apache#1625
nickva added a commit to cloudant/couchdb that referenced this issue Oct 2, 2018
This has been solid for years and when not enabled can be a performance
bottleneck.

Fixes apache#1625
nickva added a commit to cloudant/couchdb that referenced this issue Oct 2, 2018
This ensures they will be ready to process requests as soon as the application
starts up. This should make the service available sooner and should help tests
which setup and tear down the services repeatedly, where it would avoid an
annoying retry-until-ready loop.

Per-node servers/buffers are started in the init method of the monitors. There
is not chance of deadlock there because per-node supervisors are started before
the monitors.

Issue apache#1625
@nickva nickva closed this in #1627 Oct 2, 2018
nickva added a commit that referenced this issue Oct 2, 2018
This has been solid for years and when not enabled can be a performance
bottleneck.

Fixes #1625
nickva added a commit that referenced this issue Oct 2, 2018
This ensures they will be ready to process requests as soon as the application
starts up. This should make the service available sooner and should help tests
which setup and tear down the services repeatedly, where it would avoid an
annoying retry-until-ready loop.

Per-node servers/buffers are started in the init method of the monitors. There
is not chance of deadlock there because per-node supervisors are started before
the monitors.

Issue #1625
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant