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.

Sign up for GitHub

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

Jump to bottom

Cassandra's "unconfigured columnfamily" bug #250

Closed
subnetmarco opened this issue May 20, 2015 · 3 comments · Fixed by #365
Closed

Cassandra's "unconfigured columnfamily" bug #250

subnetmarco opened this issue May 20, 2015 · 3 comments · Fixed by #365
Assignees
@thibaultcha
Labels
task/bug

Comments

@subnetmarco
Copy link
Member

Sometimes when starting Cassandra the following error appears:

[INFO] Connecting to the database...
[ERR] Cassandra error: Cassandra returned error (Invalid): "unconfigured columnfamily schema_migrations"

Running DROP KEYSPACE kong; and restarting Kong fixes the problem.
@subnetmarco subnetmarco added this to the 0.3.1 milestone May 20, 2015
@subnetmarco
Copy link
Member Author

@heblug experienced this problem the first time running Kong, using kongdb.org. I confirm this also happened locally with a local Cassandra.

@thibaultcha
Copy link
Member

That happens if the keyspace is created but missing the schemas_migrations table, which is absolutely required. Basically if this table was deleted or if the migration failed to create the table, but the keyspace is created. To fix this... I'm not sure of what behaviour we should have.

  • Detect that this table is missing, thus assuming the keyspace is corrupted, drop it, and re-run the migrations. Dangerous if the user had data but is somehow missing the migrations table (maybe he deleted it himself or by error?).
  • Detect that this table is missing, and alert the user that he should re-run the migrations, but alert him about the data he'll potentially lose if the keyspace was previously used successfully.

@subnetmarco
Copy link
Member Author

+1 for second option

@thibaultcha thibaultcha removed this from the 0.3.1 milestone Jun 8, 2015
@thibaultcha thibaultcha mentioned this issue Jun 26, 2015
Merged
thibaultcha added a commit that referenced this issue Jun 26, 2015
@thibaultcha
fix(migrations) handle missing schema_migrations
61d9a20 
Handle occasional error where the schema_migrations columnfamily would
be missing thus preventing the migrations to work properly.

We now print a better error for the unaware user and suggest that the
"kong migrations reset" command should be run to fix this.

Fix #250
ctranxuan pushed a commit to streamdataio/kong that referenced this issue Aug 25, 2015
@thibaultcha
fix(migrations) handle missing schema_migrations
c94f8a7 
Handle occasional error where the schema_migrations columnfamily would
be missing thus preventing the migrations to work properly.

We now print a better error for the unaware user and suggest that the
"kong migrations reset" command should be run to fix this.

Fix Kong#250


Former-commit-id: 4e62f5f36fd20dc029a92f2f54e88a372879ad06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thibaultcha thibaultcha

Labels
task/bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[fix/migrations] handle missing schema_migrations Kong/kong
2 participants
@subnetmarco @thibaultcha