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

Clickhouse server no longer initializes default database #59989

Closed
jktng opened this issue Feb 14, 2024 · 2 comments · Fixed by #59991
Closed

Clickhouse server no longer initializes default database #59989

jktng opened this issue Feb 14, 2024 · 2 comments · Fixed by #59991
Labels
potential bug To be reviewed by developers and confirmed/rejected.

Comments

@jktng
Copy link
Contributor

jktng commented Feb 14, 2024

Hey folks, as of this morning's v24.1.4.20 release it looks like the database initialization step is erroneously skipped.

I have a Github test workflow that launches a Clickhouse container from the latest image, and as of <5 hours ago the default database is no longer being created on container start. This corresponds with when we began pulling the 24.1.4.20 image.

At a glance, #59808 looks relevant. Is this check supposed to be inverted?

@jktng jktng added the potential bug To be reviewed by developers and confirmed/rejected. label Feb 14, 2024
@th0th
Copy link

th0th commented Feb 14, 2024

I am not sure if it is the same issue, but when running in docker CLICKHOUSE_DB environment variable seems to ignored, and instead a database with name default is created. I noticed when my tests start to fail 😅

@littlebtc
Copy link

littlebtc commented May 14, 2024

We also hit it in 23.12.x branch. After seeing comment and looking for source code, it seems that the following version had #59808 backported but not have this (#59991) backported:

  • 23.3
  • 23.8
  • 23.12 (also 23)
  • 24.1

Using Docker with the version listed above will still hit this issue. If you need any workaround to continue using those versions, see the referenced pull requests in #59808.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
potential bug To be reviewed by developers and confirmed/rejected.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants