Skip to content

Implement initdb.d mechanism similar to mysql/mariadb initialization #201

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

Closed
wants to merge 2 commits into from

Conversation

pazderak
Copy link

@pazderak pazderak commented Feb 25, 2020

Why

Could be an advantage to have a way how to init DB during container start

How

This patch introduces similar mechanism as MySQL/MariaDB has - when /docker-entrypoint-initdb.d folder is mounted into container, cassandra is started in background and all scripts in given folder are executed. Background process is then stopped and normal startup continues.

Karel Pazdera added 2 commits February 25, 2020 11:25
@pazderak pazderak requested a review from tianon February 25, 2020 10:34
@yosifkit
Copy link
Member

Unfortunately this is not something we want to add to the cassandra image.

Closing with a similar rationale to #94 -- the proper deployment of Cassandra is clustered, and is much more complicated to get right automatically. It is not recommended to use a standalone deployment, and I fear such a feature would encourage folks to do so (since it couldn't possibly work with a cluster properly and/or detect clustered operation). For folks that really want to go there, building something like that on top of the provided image shouldn't be too much work. 

- #31 (comment)

Related to #31, #149, and #182

@yosifkit yosifkit closed this Feb 25, 2020
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.

2 participants