cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew F. Dennis (JIRA)" <j...@apache.org>
Subject [jira] Created: (CASSANDRA-2044) CLI should loop on describe_schema until agreement of fatel exit with stacktrace/message if no agreement after X seconds
Date Mon, 24 Jan 2011 20:36:45 GMT
CLI should loop on describe_schema until agreement of fatel exit with stacktrace/message if
no agreement after X seconds
------------------------------------------------------------------------------------------------------------------------

                 Key: CASSANDRA-2044
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2044
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 0.7.0
            Reporter: Matthew F. Dennis
            Assignee: Pavel Yaskevich
             Fix For: 0.7.1


see CASSANDRA-2026 for brief background.

It's easy to enter statements into the CLI before the schema has settled, often causing problems
where it is no longer possible to get the nodes in agreement about the schema without removing
the system directory.

The alleviate the most common problems with this, the CLI should issue the modification statement
and loop on describe_schema until all nodes agree or until X seconds has passed.  If the timeout
has been exceeded, the CLI should exit with an error and inform the user that the schema has
not settled and further migrations are ill-advised until it does.

number_of_nodes/2+1 seconds seems like a decent wait time for schema migrations to start with.

Bonus points for making the value configurable.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message