Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
Impala 2.5.0, Impala 2.6.0, Impala 2.7.0, Impala 2.8.0, Impala 2.9.0, Impala 2.10.0
Description
Currently ImpalaD's open the frontend connections and this results in query failures. The preferred behaviour would be that the ports remain closed till the catalog is received and for any reason is the SS connectivity is not established after reasonable attempts and timeouts, then the impalad to simply shut down.
impalad.INFO:I1216 17:39:40.437333 10463 jni-util.cc:166] com.cloudera.impala.common.AnalysisException: This Impala daemon is not ready to accept user requests. Status: Waiting for catalog update from the StateStore. impalad.INFO:I1216 17:39:40.438743 10463 status.cc:112] AnalysisException: This Impala daemon is not ready to accept user requests. Status: Waiting for catalog update from the StateStore. impalad.INFO:I1216 17:39:40.918184 10464 jni-util.cc:166] com.cloudera.impala.common.AnalysisException: This Impala daemon is not ready to accept user requests. Status: Waiting for catalog update from the StateStore. impalad.INFO:I1216 17:39:40.918994 10464 status.cc:112] AnalysisException: This Impala daemon is not ready to accept user requests. Status: Waiting for catalog update from the StateStore. impalad.INFO:I1216 17:39:44.129482 10465 jni-util.cc:166] com.cloudera.impala.common.AnalysisException: This Impala daemon is not ready to accept user requests. Status: Waiting for catalog update from the StateStore.
This will help especially when we have multiple impala'd behind a LB and connections can be directed to daemons with the catalog when some servers/impala services are been restarted for any reason.