[
https://issues.apache.org/jira/browse/TEPHRA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Poorna Chandra updated TEPHRA-266:
----------------------------------
Environment:
was:
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.
Description:
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.
> Identify log messages when multiple instances of Tephra to 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
> 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
(v6.4.14#64029)
