[ 
https://issues.apache.org/jira/browse/CASSANDRA-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Yaskevich updated CASSANDRA-2044:
---------------------------------------

    Attachment: CASSANDRA-2044.patch

I have added option "--schema-mwt" to set wait time for schema migration in 
seconds from command line, if it was not set system will use node_count/2 + 1 
secs or 5 secs if couldn't connect to JMX.

CLI checks node agreement on every keyspace create/drop and if nodes were not 
able to agree in given wait time system will print error message "The schema 
has not settled in %d seconds and further migrations are ill-advised until it 
does." and exit with -1 code.

> CLI should loop on describe_schema until agreement or 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
>
>         Attachments: CASSANDRA-2044.patch
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> 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.

Reply via email to