You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Alexander Behm (JIRA)" <ji...@apache.org> on 2018/03/16 20:30:00 UTC
[jira] [Resolved] (IMPALA-6683) Restarting the Catalog without
restarting Impalad and SS can block topic updates
[ https://issues.apache.org/jira/browse/IMPALA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Behm resolved IMPALA-6683.
------------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.12.0
commit 0532ff97c80aad08e800fede78348653e57a872f
Author: Tianyi Wang <tw...@cloudera.com>
Date: Thu Mar 15 18:25:54 2018 -0700
IMPALA-6683: Fix infinite loop after restarting the catalog
Currently the catalog service ID topic item includes the ID string.
It causes the coexistence of multiple catalog service ID topic items
after the catalogd restarts. Impalad therefore keeps detecting the
change of catalog service ID and requests a full catalog update. This
patch uses "CATALOG_SERVICE_ID" as the topic item name instead.
With the patch impalad prints only one line of catalog change log after
the catalog restarts.
Change-Id: I1ee6c6477458e0f4dd31b12daa9ed5f146d84e7b
Reviewed-on: http://gerrit.cloudera.org:8080/9684
Reviewed-by: Alex Behm <al...@cloudera.com>
Reviewed-by: Dimitris Tsirogiannis <dt...@cloudera.com>
Tested-by: Impala Public Jenkins
> Restarting the Catalog without restarting Impalad and SS can block topic updates
> --------------------------------------------------------------------------------
>
> Key: IMPALA-6683
> URL: https://issues.apache.org/jira/browse/IMPALA-6683
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.12.0
> Reporter: Mostafa Mokhtar
> Assignee: Tianyi Wang
> Priority: Blocker
> Fix For: Impala 2.12.0
>
>
> After restarting the Catalog without restarting the other services topic updates are getting stuck
> From SS
> {code}
> I0315 17:20:44.305951 120990 statestore.cc:242] Preparing initial catalog-update topic update for impalad@va1031.foo:22000. Size = 50.18 MB
> I0315 17:20:44.305981 120974 statestore.cc:242] Preparing initial catalog-update topic update for impalad@vd1120.foo:22000. Size = 50.18 MB
> I0315 17:20:44.305982 120975 statestore.cc:242] Preparing initial catalog-update topic update for impalad@vc1518.foo:22000. Size = 50.18 MB
> I0315 17:20:44.343500 121001 statestore.cc:652] Received request for different delta base of topic: catalog-update from: impalad@vd1107.foo:22000 subscriber from_version: 0
> I0315 17:20:44.355831 120963 statestore.cc:242] Preparing initial catalog-update topic update for impalad@ve1134.foo:22000. Size = 50.18 MB
> I0315 17:20:44.355840 120983 statestore.cc:242] Preparing initial catalog-update topic update for impalad@vd1329.foo:22000. Size = 50.18 MB
> {code}
> From Impalad
> {code}
> E0315 17:20:36.468525 7355 impala-server.cc:1381] There was an error processing the impalad catalog update. Requesting a full topic update to recover: CatalogException: Detected catalog service ID change. Aborting updateCatalog()
> E0315 17:20:40.778920 7355 impala-server.cc:1381] There was an error processing the impalad catalog update. Requesting a full topic update to recover: CatalogException: Detected catalog service ID change. Aborting updateCatalog()
> I0315 17:20:42.951370 11846 StmtMetadataLoader.java:193] Waiting for table metadata. Waited for 170 catalog updates and 340149ms. Tables remaining: [metadata_benchmarks.80_partitions_250k_files]
> I0315 17:21:04.954602 11846 StmtMetadataLoader.java:214] Re-sending prioritized load request. Waited for 180 catalog updates and 362152ms.
> I0315 17:21:04.955175 11846 FeSupport.java:274] Requesting prioritized load of table(s): metadata_benchmarks.80_partitions_250k_files
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)