[
https://issues.apache.org/jira/browse/CASSANDRA-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054630#comment-13054630
]
Jim Ancona commented on CASSANDRA-2773:
---------------------------------------
I disagree. This is a bug which allows a client to make a cluster unresponsive
by performing a seemingly innocuous series of operations. If that happens, the
cluster is un-restartable without loss of data. I wouldn't call a release where
this can occur "stable". So if the goal for 0.7 is stability...
WRT "fixing your code to not generate problematic mutations," this may be
difficult to do. I have so far identified code that does deletes followed by
updates in the same mutation, but I haven't yet found any updates followed by
deletes. Are we sure that only the update-followed-by-delete scenario is
problematic?
In any case, even after reviewing all our code for the relevant scenarios, I
would not feel comfortable deploying an 0.7 release with this vulnerability to
production. The risk of a catastrophic failure is too great.
> "Index manager cannot support deleting and inserting into a row in the same
> mutation"
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-2773
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2773
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Boris Yen
> Assignee: Jonathan Ellis
> Priority: Critical
> Fix For: 0.8.2
>
> Attachments: 2773-v2.txt, 2773.txt, cassandra.log
>
>
> I use hector 0.8.0-1 and cassandra 0.8.
> 1. create mutator by using hector api,
> 2. Insert a few columns into the mutator for key "key1", cf "standard".
> 3. add a deletion to the mutator to delete the record of "key1", cf
> "standard".
> 4. repeat 2 and 3
> 5. execute the mutator.
> the result: the connection seems to be held by the sever forever, it never
> returns. when I tried to restart the cassandra I saw unsupportedexception :
> "Index manager cannot support deleting and inserting into a row in the same
> mutation". and the cassandra is dead forever, unless I delete the commitlog.
> I would expect to get an exception when I execute the mutator, not after I
> restart the cassandra.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
