[
https://issues.apache.org/jira/browse/TEPHRA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129328#comment-16129328
]
Andreas Neumann commented on TEPHRA-240:
----------------------------------------
Currently, we do not keep the client id after the transaction commits. The
change set that is kept for conflict detection is not labeled with the client
id. Adding that is easy but may increase the memory footprint. Therefore, there
should be an configuration option whether this should be kept or not.
Also, because the client id is only in memory but not persisted to the
transaction snapshot, this info will not be available after a restart.
> TransactionConflictException should contain the conflicting key and client id
> -----------------------------------------------------------------------------
>
> Key: TEPHRA-240
> URL: https://issues.apache.org/jira/browse/TEPHRA-240
> Project: Tephra
> Issue Type: Bug
> Reporter: Andreas Neumann
> Assignee: Poorna Chandra
>
> Often transaction conflicts are hard to explain. Having the conflicting key,
> or even the name of the client that performed the concurrent update would
> greatly help debug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
