[ https://issues.apache.org/jira/browse/TEPHRA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16453358#comment-16453358 ] ASF GitHub Bot commented on TEPHRA-266: --------------------------------------- GitHub user poornachandra opened a pull request: https://github.com/apache/incubator-tephra/pull/74 TEPHRA-266 Identify log messages when multiple instances of Tephra run on a single HBase cluster JIRA - https://issues.apache.org/jira/browse/TEPHRA-266 You can merge this pull request into a Git repository by running: $ git pull https://github.com/poornachandra/incubator-tephra feature/tx-state-cache-log Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-tephra/pull/74.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 #74 ---- commit df16b5be2146c4ae92d23d2c62a2cf3b32a0ced5 Author: poorna Date: 2018-04-26T01:58:52Z TEPHRA-266 Identify log messages when multiple instances of Tephra run on a single HBase cluster ---- > Identify log messages when multiple instances of Tephra run on a single HBase cluster > ------------------------------------------------------------------------------------- > > Key: TEPHRA-266 > URL: https://issues.apache.org/jira/browse/TEPHRA-266 > Project: Tephra > Issue Type: Improvement > Environment: > Reporter: Poorna Chandra > Assignee: Poorna Chandra > Priority: Major > Fix For: 0.14.0-incubating > > > When multiple instances of Tehpra are run in a single HBase cluster, the log messages from the co-processors of all instances (which are identical except for the timestamp) go into a single region server log file. It becomes very difficult to figure out issues of an instance due to this. > it would be good if instance id is logged along with the co-processor log messages so that we can identity which messages belong to which instance of Tephra. -- This message was sent by Atlassian JIRA (v7.6.3#76005)