Possible migration bug (2.0.2 to 2.1)
See original GitHub issueI’ve upgraded from 2.0.2 to 2.1 today and found a NullPointerException in the log (otherwise everything is looks okay):
INFO [main] o.c.c.m.MigrationRepository - Found 10 migration scripts
WARN [main] i.c.s.CassandraStorage - Starting db migration from 23 to 25…
INFO [main] o.c.c.m.MigrationRepository - Found 10 migration scripts
INFO [main] o.c.c.m.MigrationTask - Migrated keyspace cassandra_reaper to version 24
INFO [main] i.c.s.CassandraStorage - Migrated keyspace cassandra_reaper to version 24
INFO [main] o.c.c.m.MigrationRepository - Found 10 migration scripts
INFO [main] o.c.c.m.MigrationTask - Migrated keyspace cassandra_reaper to version 25
INFO [main] i.c.s.CassandraStorage - Migrated keyspace cassandra_reaper to version 25
WARN [main] i.c.s.c.Migration016 - altering every table to set `dclocal_read_repair_chance` to zero…
WARN [main] i.c.s.c.Migration016 - alter every table to set `dclocal_read_repair_chance` to zero completed.
INFO [main] i.c.s.c.Migration024 - Altering node_metrics_v3 to use TWCS...
INFO [main] i.c.s.c.Migration024 - node_metrics_v3 was successfully altered to use TWCS.
INFO [main] i.c.s.c.Migration025 - Converting repair_run_by_cluster table...
ERROR [main] i.c.s.c.Migration025 - Failed transferring rows to repair_run_by_cluster_v2
java.lang.NullPointerException: null
at io.cassandrareaper.storage.cassandra.Migration025.migrate(Migration025.java:51)
at io.cassandrareaper.storage.CassandraStorage.initializeCassandraSchema(CassandraStorage.java:302)
at io.cassandrareaper.storage.CassandraStorage.initializeAndUpgradeSchema(CassandraStorage.java:251)
at io.cassandrareaper.storage.CassandraStorage.<init>(CassandraStorage.java:239)
at io.cassandrareaper.ReaperApplication.initializeStorage(ReaperApplication.java:477)
at io.cassandrareaper.ReaperApplication.tryInitializeStorage(ReaperApplication.java:300)
at io.cassandrareaper.ReaperApplication.run(ReaperApplication.java:179)
at io.cassandrareaper.ReaperApplication.run(ReaperApplication.java:98)
at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:43)
at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:87)
at io.dropwizard.cli.Cli.run(Cli.java:78)
at io.dropwizard.Application.run(Application.java:93)
at io.cassandrareaper.ReaperApplication.main(ReaperApplication.java:117)
INFO [main] i.c.ReaperApplication - no JMX connection factory given in context, creating default
INFO [main] i.c.ReaperApplication - creating and registering health checks
INFO [main] i.c.ReaperApplication - creating resources and registering endpoints
INFO [main] i.c.s.SchedulingManager - Starting new SchedulingManager instance
INFO [main] i.c.ReaperApplication - Initializing JMX seed list for all clusters...
INFO [main] i.c.ReaperApplication - Initialized JMX seed list for all clusters.
INFO [main] i.c.ReaperApplication - resuming pending repair runs
INFO [main] i.c.ReaperApplication - Initialization complete!
WARN [main] i.c.ReaperApplication - Reaper is ready to get things done!
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Migrate from 2.1.4 to 2.2.0 · Issue #18894 · apache/airflow
Upgrading image from apache/airflow:2.1.4-python3.7 ... release from version 2.0.2 and this is first time, I'm getting migration problem.
Read more >Migrate from ASP.NET Core 2.0 to 2.1 - Microsoft Learn
This article provides an overview on migration to ASP.NET Core 2.1. It doesn't contain a complete list of all changes needed to migrate...
Read more >Upgrading Airflow to a newer version - Apache Airflow
Newer Airflow versions can contain database migrations so you must run ... Most likely the data was corrupted and left-over from some bugs...
Read more >2.6.x to 2.7.0 Migration Notes [iTop Documentation] - iTop Hub
Root cause: This is a MariaDB issue, providing the versions in which the bug was fixed by them. Strategy: avoid those buggy MariaDB...
Read more >Quartz Migration Guide
There is no major DB schema changes in 3.x version, but mainly code fix, API changes, dependencies, and JDK upgrades. Quartz 1.8.x to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The fix was released.
I’m going to create a patch to skip such cases gracefully instead of trashing the whole migration.