[
https://issues.apache.org/jira/browse/SOLR-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673804#comment-13673804
]
Yonik Seeley commented on SOLR-4733:
------------------------------------
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.
wrt cloud mode, there's probably a lot of edge cases we haven't considered when
rollbacks come into play... peer sync stuff, recovery using whole index
replication and then getting a rollback in the middle of buffering updates,
etc.
> 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]
