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 to starting two Elasticsearch nodes instead of one in "stack up" #1651

Open
jsvd opened this issue Jan 30, 2024 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@jsvd
Copy link
Member

jsvd commented Jan 30, 2024

stack up is extremely useful to manually smoke test the stack, but one thing I miss is sometimes having two nodes instead of one.
This is because some features only show their true potential on multi node setups and also rendering some UI components for a single node isn't enough.

Adding a second node would require tweaking the docker compose template and correctly setting the tls configuration.

@jsvd jsvd added the enhancement New feature or request label Jan 30, 2024
@jsoriano
Copy link
Member

We have to keep in mind that elastic-package happens to be able to manage stacks, but at the end it is intended for package development. In general one node is enough there.

So I wouldn't default to two nodes, but I agree that it can be useful in some cases and we can definitely add an optional setting to start more nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants