Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 94AFF200C5A for ; Tue, 18 Apr 2017 11:28:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 93651160BAF; Tue, 18 Apr 2017 09:28:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DA00F160B90 for ; Tue, 18 Apr 2017 11:28:46 +0200 (CEST) Received: (qmail 20883 invoked by uid 500); 18 Apr 2017 09:28:45 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 20860 invoked by uid 99); 18 Apr 2017 09:28:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Apr 2017 09:28:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6A96D18969B for ; Tue, 18 Apr 2017 09:28:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id EcFtvXWWHof6 for ; Tue, 18 Apr 2017 09:28:43 +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 DA1CC5F405 for ; Tue, 18 Apr 2017 09:28:42 +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 3AD5AE0874 for ; Tue, 18 Apr 2017 09:28:42 +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 9D4FB21B49 for ; Tue, 18 Apr 2017 09:28:41 +0000 (UTC) Date: Tue, 18 Apr 2017 09:28:41 +0000 (UTC) From: "Albert Lee (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 18 Apr 2017 09:28:47 -0000 [ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated HBASE-17906: ------------------------------- Attachment: hbase-thrift-17906-ForRecurr.zip hbase-thrift-17906-ForRecurr.zip is made a little change of hbase-examples/src/main/python/thrift2 for recurring the problem. Use the 'DemoClient.py' which in this zip and write data through thrift2 server. When the python run more than 'hbase.thrift.connection.max-idletime', all connection to server will be interrupted, then thrift2 server did not work for a while and throw "hbase.ttypes.TIOError: TIOError(_message='Failed 1 action: IOException: 1 time, servers with issues: null location" to DemoClient.py. The problem is because when get table from HTablePools in ThriftHBaseServiceHandler.java, it never refresh the connection which in connectionCache. Until 'hbase.thrift.connection.max-idletime' come, connectionCache begin to clean connections which not refreshed. Then the problem raise. Problems appeared in the version 0.98. I will test this problem whether exists in branch 1+ or master. And sorry about the issue title. It is not a deadlock, it just because connection does refresh when getTable. > When a huge amount of data writing to hbase through thrift2, there will be a deadlock error. > -------------------------------------------------------------------------------------------- > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client > Affects Versions: 0.98.21, 0.98.22, 0.98.23, 0.98.24, 0.98.25 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 > Reporter: Albert Lee > Labels: patch > Fix For: 0.98.21, 0.98.22, 0.98.23, 0.98.24, 0.98.25 > > Attachments: HBASE-17906.branch-0.98.001.patch, HBASE-17906.branch-0.98.002.patch, HBASE-17906.master.001.patch, HBASE-17906.master.002.patch, hbase-thrift-17906-ForRecurr.zip > > > When a huge amount of data writing to hbase through thrift2, there will be a deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)