From dev-return-2108-apmail-tephra-dev-archive=tephra.apache.org@tephra.incubator.apache.org Thu Apr 26 02:03:03 2018 Return-Path: X-Original-To: apmail-tephra-dev-archive@minotaur.apache.org Delivered-To: apmail-tephra-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2843118609 for ; Thu, 26 Apr 2018 02:03:03 +0000 (UTC) Received: (qmail 58045 invoked by uid 500); 26 Apr 2018 02:03:03 -0000 Delivered-To: apmail-tephra-dev-archive@tephra.apache.org Received: (qmail 57996 invoked by uid 500); 26 Apr 2018 02:03:03 -0000 Mailing-List: contact dev-help@tephra.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tephra.incubator.apache.org Delivered-To: mailing list dev@tephra.incubator.apache.org Received: (qmail 57985 invoked by uid 99); 26 Apr 2018 02:03:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Apr 2018 02:03:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 61035C965D for ; Thu, 26 Apr 2018 02:03:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id t9vRpq0n5nae for ; Thu, 26 Apr 2018 02:03:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 39D115F189 for ; Thu, 26 Apr 2018 02:03:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5FFD9E0047 for ; Thu, 26 Apr 2018 02:03:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1480F241D2 for ; Thu, 26 Apr 2018 02:03:00 +0000 (UTC) Date: Thu, 26 Apr 2018 02:03:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TEPHRA-266) Identify log messages when multiple instances of Tephra run on a single HBase cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)