From dev-return-2112-apmail-tephra-dev-archive=tephra.apache.org@tephra.incubator.apache.org Thu Apr 26 09:23:05 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 8BC1E174F3 for ; Thu, 26 Apr 2018 09:23:05 +0000 (UTC) Received: (qmail 81624 invoked by uid 500); 26 Apr 2018 09:23:05 -0000 Delivered-To: apmail-tephra-dev-archive@tephra.apache.org Received: (qmail 81582 invoked by uid 500); 26 Apr 2018 09:23:05 -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 81571 invoked by uid 99); 26 Apr 2018 09:23:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Apr 2018 09:23:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D2BB01A26B6 for ; Thu, 26 Apr 2018 09:23:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id d6Xw80VwzviB for ; Thu, 26 Apr 2018 09:23:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 06AE85F1B9 for ; Thu, 26 Apr 2018 09:23: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 869A0E0D74 for ; Thu, 26 Apr 2018 09:23: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 42DD82108C for ; Thu, 26 Apr 2018 09:23:00 +0000 (UTC) Date: Thu, 26 Apr 2018 09:23:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TEPHRA-270) Avoid transaction state cache refresh on co-procesor startup 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-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16453739#comment-16453739 ] ASF GitHub Bot commented on TEPHRA-270: --------------------------------------- Github user anew commented on a diff in the pull request: https://github.com/apache/incubator-tephra/pull/72#discussion_r184323707 --- Diff: tephra-core/src/main/java/org/apache/tephra/coprocessor/TransactionStateCache.java --- @@ -78,6 +78,7 @@ protected void startUp() throws Exception { protected void shutDown() throws Exception { if (refreshService != null) { refreshService.interrupt(); + refreshService.join(1000); --- End diff -- this means, if the refreshService does not finish within a second, shutdown() will throw exception? And the remainder of the shutdown sequence is not performed? Is that intentional? > Avoid transaction state cache refresh on co-procesor startup > ------------------------------------------------------------ > > Key: TEPHRA-270 > URL: https://issues.apache.org/jira/browse/TEPHRA-270 > Project: Tephra > Issue Type: Improvement > Components: core > Reporter: Poorna Chandra > Assignee: Poorna Chandra > Priority: Major > Fix For: 0.14.0-incubating > > > Transaction state cache, on startup, refreshes the transaction snapshot from HDFS. The transaction state cache startup is called during HBase co-processor startup. The refresh of the transaction snapshot can block, thus blocking the co-processor startup. > The subsequent transaction snapshot refreshes happen in the background. Also - there is no guarantee that a snapshot will be present during the refresh on startup. Hence it is okay not to refresh the snapshot during snapshot, but do it in background. -- This message was sent by Atlassian JIRA (v7.6.3#76005)