[GitHub] incubator-tephra issue #41: TEPHRA-152 Using ReferenceCounting for Transacti...
Github user poornachandra commented on the issue: https://github.com/apache/incubator-tephra/pull/41 @gokulavasan Now that we have introduced class `ReferenceCountedSupplier`, it would be good to use this class in `PruneUpperBoundWriterSupplier` too. It will reduce code duplication. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (TEPHRA-228) Introduce client ID that can be used to track requests per client
Poorna Chandra created TEPHRA-228: - Summary: 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)
