getsentry / getsentry/self-hosted

clickhouse broken after upgrade to 24.5.1 from 23.6.2 (from 22.1.0)

Open
#3,118 10 comments 0 reactions 0 assignees View on GitHub
Improvement
Dominant language
Shell
Stars
9.6k
Forks
2k
Avg merge
1d 3h
Merged PRs (30d)
12

Description

### Self-Hosted Version

23.6.2

### CPU Architecture

x86_64

### Docker Version

24.0.5

### Docker Compose Version

2.27.1

### Steps to Reproduce

I've a self hosted sentry instance with version 22.1.0 and want to migrate it to current 24.5.1
After (a successful) upgrade to the required intermediate step 23.6.2 it breaks the clickhouse container with the following errors:

clickhouse-1 | 2024.06.06 21:25:11.570376 [ 1 ] {} Application: Caught exception while loading metadata: Code: 48. DB::Exception: Data directory for system database exists, but metadata file does not. Probably you are trying to upgrade from version older than 20.7. If so, you should upgrade through intermediate version. (NOT_IMPLEMENTED), Stack trace (when copying this message, always include the lines below):

Are there any undocumented intermediated steps to upgrade 23.6.2 to latest?

### Expected Result

Working 24.5.1 instance

### Actual Result

clickhouse-1 | 2024.06.06 21:25:11.563935 [ 1 ] {} Application: Listen [::]:9009 failed: Poco::Exception. Code: 1000, e.code() = 0, DNS error: EAI: Address family for hostname not supported (version 23.8.11.29.altinitystable (altinity build)). If it is an IPv6 or IPv4 address and your host has disabled IPv6 or IPv4, then consider to specify not disabled IPv4 or IPv6 address to listen in element of configuration file. Example for disabled IPv6: 0.0.0.0 . Example for disabled IPv4: ::
clickhouse-1 | 2024.06.06 21:25:11.570376 [ 1 ] {} Application: Caught exception while loading metadata: Code: 48. DB::Exception: Data directory for system database exists, but metadata file does not. Probably you are trying to upgrade from version older than 20.7. If so, you should upgrade through intermediate version. (NOT_IMPLEMENTED), Stack trace (when copying this message, always include the lines below):
clickhouse-1 |
clickhouse-1 | 0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000c61ff37 in /usr/bin/clickhouse
clickhouse-1 | 1. DB::Exception::Exception(int, FormatStringHelperImpl::type>, String const&) @ 0x00000000074a9bcd in /usr/bin/clickhouse
clickhouse-1 | 2. DB::checkUnsupportedVersion(std::shared_ptr, String const&) @ 0x00000000122dd350 in /usr/bin/clickhouse
clickhouse-1 | 3. DB::loadSystemDatabaseImpl(std::shared_ptr, String const&, String const&) @ 0x00000000122e540b in /usr/bin/clickhouse
clickhouse-1 | 4. DB::loadMetadataSystem(std::shared_ptr) @ 0x00000000122e43de in /usr/bin/clickhouse
clickhouse-1 | 5. DB::Server::main(std::vector> const&) @ 0x000000000c6b7f1d in /usr/bin/clickhouse
clickhouse-1 | 6. Poco::Util::Application::run() @ 0x0000000015b50a66 in /usr/bin/clickhouse
clickhouse-1 | 7. DB::Server::run() @ 0x000000000c6a6dde in /usr/bin/clickhouse
clickhouse-1 | 8. Poco::Util::ServerApplication::run(int, char**) @ 0x0000000015b5fb79 in /usr/bin/clickhouse
clickhouse-1 | 9. mainEntryClickHouseServer(int, char**) @ 0x000000000c6a3baa in /usr/bin/clickhouse
clickhouse-1 | 10. main @ 0x000000000712c42f in /usr/bin/clickhouse
clickhouse-1 | 11. ? @ 0x00007fa85a1cd083 in ?
clickhouse-1 | 12. _start @ 0x000000000635186e in /usr/bin/clickhouse
clickhouse-1 | (version 23.8.11.29.altinitystable (altinity build))

### Event ID

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the upgrade from Sentry 23.6.2 to 24.5.1 with the reported Docker and Docker Compose versions, then inspect the ClickHouse container logs in the issue. Review the documented upgrade path for any required intermediate versions. Done means the instance reaches a working 24.5.1 state without the system-database metadata error.

Written by the indexing model from the issue text.

Assessment

Tech stack
clickhouse, docker, docker-compose
Domain
databases, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.