[
https://issues.apache.org/jira/browse/TEPHRA-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012794#comment-16012794
]
ASF GitHub Bot commented on TEPHRA-228:
---------------------------------------
GitHub user gokulavasan opened a pull request:
https://github.com/apache/incubator-tephra/pull/42
TEPHRA-228 Adding the ability to pass-in a clientId during the start …
…of a transaction which is logged when the transaction gets invalidated
during time out.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gokulavasan/incubator-tephra
feature/tephra-228
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tephra/pull/42.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #42
----
commit 46760aa42b790d2f030f588cce0648b2dd94369a
Author: Gokul Gunasekaran <[email protected]>
Date: 2017-05-16T01:06:10Z
TEPHRA-228 Adding the ability to pass-in a clientId during the start of a
transaction which is logged when the transaction gets invalidated during time
out.
----
> Introduce client ID that can be used to track requests per client
> -----------------------------------------------------------------
>
> Key: TEPHRA-228
> URL: https://issues.apache.org/jira/browse/TEPHRA-228
> Project: Tephra
> Issue Type: Improvement
> Components: api, core
> Reporter: Poorna Chandra
> Assignee: Poorna Chandra
>
> Today transaction manager does not have details of what transaction belongs
> to which client. For instance when a there are a lot of invalid transactions
> generated by a client, it is not easy to say which client generated the
> invalid transactions. Transaction manager just logs a message saying the
> transaction ID was invalidated. This makes debugging very difficult since
> there is no easy way to map the transaction ID to a program.
> Transaction APIs should allow clients to pass in client IDs for every start
> transaction call. Transaction manager can store this client ID as part of the
> transaction metadata. And when transaction manager logs messages with
> transaction ID, it can include the client ID in the message.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
