[jira] [Updated] (CASSANDRA-13180) Better handling of missing entries in system_schema.columns during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-13180:
Resolution: Fixed
Fix Version/s: (was: 3.0.x)
(was: 3.x)
3.11
3.0.11
Status: Resolved (was: Ready to Commit)
Thank you, committed as {{a70b0d4d37851891ec1c8af96063985a5122edda}} to
{{cassandra-3.0}} and merged up to {{cassandra-3.11}} and {{trunk}}.
> Better handling of missing entries in system_schema.columns during startup
> --
>
> Key: CASSANDRA-13180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13180
> Project: Cassandra
> Issue Type: Improvement
> Components: Distributed Metadata
>Reporter: Tyler Hobbs
>Assignee: Tyler Hobbs
> Fix For: 3.0.11, 3.11
>
>
> Like the error in CASSANDRA-12213 and CASSANDRA-12165, it's possible for
> {{system_schema.keyspaces}} and {{tables}} to contain entries for a table
> while {{system_schema.columns}} has none. This produces an error during
> startup, and there's no way for a user to recover from this without restoring
> from backups.
> Although this has been seen in the wild on one occasion, the cause is still
> not entirely known. (It may be due to a concurrent DROP TABLE and ALTER
> TABLE where a table property is altered.) Until we know the root cause, it
> makes sense to give users a way to recover from that situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13180) Better handling of missing entries in system_schema.columns during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-13180:
--
Status: Ready to Commit (was: Patch Available)
> Better handling of missing entries in system_schema.columns during startup
> --
>
> Key: CASSANDRA-13180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13180
> Project: Cassandra
> Issue Type: Improvement
> Components: Distributed Metadata
>Reporter: Tyler Hobbs
>Assignee: Tyler Hobbs
> Fix For: 3.0.x, 3.x
>
>
> Like the error in CASSANDRA-12213 and CASSANDRA-12165, it's possible for
> {{system_schema.keyspaces}} and {{tables}} to contain entries for a table
> while {{system_schema.columns}} has none. This produces an error during
> startup, and there's no way for a user to recover from this without restoring
> from backups.
> Although this has been seen in the wild on one occasion, the cause is still
> not entirely known. (It may be due to a concurrent DROP TABLE and ALTER
> TABLE where a table property is altered.) Until we know the root cause, it
> makes sense to give users a way to recover from that situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13180) Better handling of missing entries in system_schema.columns during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua McKenzie updated CASSANDRA-13180:
Reviewer: Aleksey Yeschenko
> Better handling of missing entries in system_schema.columns during startup
> --
>
> Key: CASSANDRA-13180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13180
> Project: Cassandra
> Issue Type: Improvement
> Components: Distributed Metadata
>Reporter: Tyler Hobbs
>Assignee: Tyler Hobbs
> Fix For: 3.0.x, 3.x
>
>
> Like the error in CASSANDRA-12213 and CASSANDRA-12165, it's possible for
> {{system_schema.keyspaces}} and {{tables}} to contain entries for a table
> while {{system_schema.columns}} has none. This produces an error during
> startup, and there's no way for a user to recover from this without restoring
> from backups.
> Although this has been seen in the wild on one occasion, the cause is still
> not entirely known. (It may be due to a concurrent DROP TABLE and ALTER
> TABLE where a table property is altered.) Until we know the root cause, it
> makes sense to give users a way to recover from that situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CASSANDRA-13180) Better handling of missing entries in system_schema.columns during startup
[
https://issues.apache.org/jira/browse/CASSANDRA-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-13180:
Status: Patch Available (was: Open)
Patch and pending test runs:
||branch||testall||dtest||
|[CASSANDRA-13180-3.0|https://github.com/thobbs/cassandra/tree/CASSANDRA-13180-3.0]|[testall|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-13180-3.0-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-13180-3.0-dtest]|
|[CASSANDRA-13180-3.11|https://github.com/thobbs/cassandra/tree/CASSANDRA-13180-3.11]|[testall|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-13180-3.11-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-13180-3.11-dtest]|
|[CASSANDRA-13180-trunk|https://github.com/thobbs/cassandra/tree/CASSANDRA-13180-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-13180-trunk-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-13180-trunk-dtest]|
There were minor conflicts in the merges to 3.11 and trunk.
> Better handling of missing entries in system_schema.columns during startup
> --
>
> Key: CASSANDRA-13180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13180
> Project: Cassandra
> Issue Type: Improvement
> Components: Distributed Metadata
>Reporter: Tyler Hobbs
>Assignee: Tyler Hobbs
> Fix For: 3.0.x, 3.x
>
>
> Like the error in CASSANDRA-12213 and CASSANDRA-12165, it's possible for
> {{system_schema.keyspaces}} and {{tables}} to contain entries for a table
> while {{system_schema.columns}} has none. This produces an error during
> startup, and there's no way for a user to recover from this without restoring
> from backups.
> Although this has been seen in the wild on one occasion, the cause is still
> not entirely known. (It may be due to a concurrent DROP TABLE and ALTER
> TABLE where a table property is altered.) Until we know the root cause, it
> makes sense to give users a way to recover from that situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
