[ 
https://issues.apache.org/jira/browse/SOLR-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673817#comment-13673817
 ] 

Mark Miller commented on SOLR-4733:
-----------------------------------

{quote}
wrt transaction isolation & commit, one client can always make another client's 
changes visible, and that's usually never been a big deal. Throw rollbacks into 
the equation and those clients had better be working together since one client 
undoing another clients updates (at the last arbitrary commit point) seems much 
more problematic.
{quote}

Eh ... it's not the end of the world if you commit on someone else, but when 
you consider the idea of commit is generally that your docs dont go in unless 
you do it, I really see it as the same issue as rollback. You simply have to 
understand Lucene/Solr has one global transaction in both cases.

bq. wrt cloud mode,

Yeah, I kind of caught the idea that you may only have been clearing the 
updatelog for rollback and not cloud - which is why I created 2 new issues.

I still think the auto hard commit that the updatelog wants makes supporting 
rollback even in the single node case a large problem though.

I'm halfway back to wanting to boot it for all modes ;)
                
> Rollback does not work correctly with tlog and optimistic concurrency updates
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-4733
>                 URL: https://issues.apache.org/jira/browse/SOLR-4733
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.3, 4.2.1
>         Environment: Ubuntu 12.04.2 LTS
>            Reporter: Mark S
>              Labels: solrj
>         Attachments: SOLR-4733.patch
>
>
> When using the updateLog, attempting to rollback atomic updates still causes 
> post-rollback atomic updates to still report a conflict with the version 
> assigned to the update posted prior to the rollback

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to