Support developer mode #32
Conversation
When developer mode is set, the stargate node joins the ring and defaults the seed list to itself
jorgebay
requested review from
dougwettlaufer,
EricBorczuk and
mpenick
as code owners
|
You can use the following command to start in developer mode: |
|
I've simplified it a little further by setting simple snitch in developer mode, the new command w/ the required parameters is: |
|
I've rolled in a change here to make binding to listen address opt-in. |
| @Option(name = {"--developer-mode"}, description = "Defines whether the stargate node should also behave as a " + | ||
| "regular node, joining the ring with tokens assigned in order to facilitate getting started quickly and not " + | ||
| "requiring additional nodes or existing cluster") | ||
| boolean developerMode = false; | ||
|
|
||
| @Order(value = 15) | ||
| @Option(name = {"--bind-to-listen-address"}, description = "When set, it binds web services to listen address only") |
There was a problem hiding this comment.
Please add these to starctl as well since we also support env vars.
There was a problem hiding this comment.
Good catch, I've added them.
jorgebay
requested review from
dimas-b,
olim7t,
pcmanus and
tomekl007
as code owners
|
@jorgebay These changes need to also be made to the other persistence backends: https://github.com/stargate/persistence-extensions |
|
There was a small discussion on the private repo, tldr: only support it in the built-in C* 3.11 for now. I think it it's valuable for users to have a developer mode that doesn't require an additional cluster. Having 3.11 support for dev mode is good enough for me, but if you think that we need it for dse and C* 4.0 we should file a ticket. |
When developer mode is set, the stargate node joins the ring and defaults the seed list to itself.