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 640BD200B6F for ; Wed, 24 Aug 2016 16:41:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 62AD8160AB1; Wed, 24 Aug 2016 14:41:17 +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 A8BDC160A91 for ; Wed, 24 Aug 2016 16:41:16 +0200 (CEST) Received: (qmail 31289 invoked by uid 500); 24 Aug 2016 14:41:15 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Delivered-To: moderator for dev@hive.apache.org Received: (qmail 97975 invoked by uid 99); 24 Aug 2016 11:52:40 -0000 X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.43 X-Spam-Level: * X-Spam-Status: No, score=1.43 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=qLWg8TK59yTAffN4qt+MI8UlZUc3gyS3KzzvRTWZc6w=; b=ZLrtLVqfelXrdH+RxeqtXno/XKsX+70uAfm/+VxmxBH2AFmOB/LAvJj4OX0V5FMhNP gAE6qdXuXP4zfmIBX8PL2p3zV0WXG1Xcgi8Zx03+ggiVRcNGRNtCuJSj1kXLAdacUEGs 52huPmwa3uA+GGLfyhFkwkuRLj7kKc87RVX68gfseiufKDSrqBhrR92zKXw15ZkeXb4P aVJKHF8Ywhl7O6607yJ3A/ex5IGormu8tG9y8yKzMJ8jZVHiR4X3sep06h/l/Lq6Iko5 vKutrh1YklCjhW0gVOu8nyPcqWv6WFVV4Q4furCYv+NfpY2D2T/Adbpar9+F1/HRPkXC juGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=qLWg8TK59yTAffN4qt+MI8UlZUc3gyS3KzzvRTWZc6w=; b=Z5t0VdzcX/szIRppuX6xDF+joxMDisaxYz4QS2GwocFiUzMOqZ2L2lahhDpQERYzog Ihf4SCfxPxSXGjdcl/At+5wHzSB7ssdOG88HS1hwlGMFID3+6WmQkkAsy1ozBUEQW9/H HOOAS1Xts82zMNgZWe6hm04QJC1zEhx7SJQRrX2l/a4CxyFjD/WNUa8ovpT7c50oYlSl f80O5gtH6Xz0aTLWdCDH3KW7dHfyqMszP0hAEWuU2NXm0PGc29lLoOdzcuOmlzX/MDLL 7PX1iI5gOEjLPXRLxobpWlAXC4tM+3yJ1XCF+EKsLGy62FpaVWYrunnQjJpX3JaqR05G vB1g== X-Gm-Message-State: AEkooutuSWeoK04ejKGoN3//LZpCpRwfzQDXg3VGs7CQtpowdFUQmajYvoEdppcYUej11jxgzqkyhsS9CYfkCQ== X-Received: by 10.194.38.166 with SMTP id h6mr2353584wjk.101.1472039551216; Wed, 24 Aug 2016 04:52:31 -0700 (PDT) MIME-Version: 1.0 From: eric wong Date: Wed, 24 Aug 2016 19:52:30 +0800 Message-ID: Subject: Too many hive client cause mysql meta store hang infinitely To: user@hive.apache.org, dev@hive.apache.org Content-Type: multipart/alternative; boundary=047d7b6706e18bb7b8053acfea75 archived-at: Wed, 24 Aug 2016 14:41:17 -0000 --047d7b6706e18bb7b8053acfea75 Content-Type: text/plain; charset=UTF-8 Hi, we encounter this problem in our proc hadoop cluster: Sometimes hive mysql metastore hang because deadlock, so result in all hive client hang infinitely. we check in this problem, found most mysql request hang on " SHOW FULL COLUMNS FROM `DELETEME1472008582981` FROM `hive` LIKE '%' " More interesting is mysql request span to multiple nodes will request table with same name, like below: | 5409551 | hive | 10.93.xx.54:23327 | hive | Query | 1476 | Waiting for table metadata lock | SHOW FULL COLUMNS FROM `DELETEME1472008582981` FROM `hive` LIKE '%' | | 5409557 | hive | 10.93.xx.20:3862 | hive | Query | 1473 | Waiting for table metadata lock | SHOW FULL COLUMNS FROM `DELETEME1472008582981` FROM `hive` LIKE '%' | | 5409567 | hive | 10.93.xx.51:48055 | hive | Query | 1469 | Waiting for table metadata lock | SHOW FULL COLUMNS FROM `DELETEME1472008582981` FROM `hive` LIKE '%' | | 5409576 | hive | 10.93.xx.32:18886 | hive | Sleep | 1464 | | NULL | | 5409577 | hive | 10.93.xx.32:18887 | hive | Query | 1463 | Waiting for table metadata lock | SHOW FULL COLUMNS FROM `DELETEME1472008582981` FROM `hive` LIKE '%' | | 5409587 | hive | 10.93.25.32:19582 | hive | Query | 1457 | Waiting for table metadata lock | SHOW FULL COLUMNS FROM `DELETEME1472008582981` FROM `hive` LIKE '%' obviously it is not identical with the datanucleus code in : RDBMSStoreManager.java , which one hive session will create probeTable with current milliseconds("DELETEME+"). List above shows that five hive session among multiple node however request for ProbeTable with same name! And we check our configuration in hive-site.xml, autoCreateSchema(false) and fixedDataStore(true) has been set for long time. Code shows when this two properties is set, no "DELETEMExxx" table will be created and queried. so we want to figure out why our hive client will request for such "DELETEMExxx" table, so result in deadlock in mysql metastore database. Any suggestion will be welcome. Thanks! env: hive version: 1.2.1 metastore database: MySQL Local/Embedded Metastore Server Hive user: 100+ Best wishes! -- Wang Haihua --047d7b6706e18bb7b8053acfea75--