impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Knupp (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IMPALA-5105) Improve error message in the event catalogd crashes
Date Tue, 21 Mar 2017 00:44:41 GMT

     [ https://issues.apache.org/jira/browse/IMPALA-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Knupp updated IMPALA-5105:
--------------------------------
    Description: 
IMPALA-4704 documents a case whereby impalad opens up ports 21000 and 21050 before the catalog
update has been received, and this can lead to queries failing with the message:

{noformat}
AnalysisException: This Impala daemon is not ready to accept user requests. Status: Waiting
for catalog update from the StateStore.
{noformat}

Also, we have seen cases where queries fail when the catalogd crashes for some reason or another,
and the exact same error is produced:

{noformat}
[impalad-2.abc.xyz.com:21000] > show tables;
Query: show tables
ERROR: AnalysisException: This Impala daemon is not ready to accept user requests. Status:
Waiting for catalog update from the StateStore.
{noformat}

One error is a recoverable timing issue, the other is crashed processed. It would be nice
if these two conditions were differentiated by unique error messages.

  was:
IMPALA-4704 documents a case whereby impalad opens up ports 21000 and 21050 before the catalog
update has been received, and this can lead to queries failing with the message:

{noformat}
AnalysisException: This Impala daemon is not ready to accept user requests. Status: Waiting
for catalog update from the StateStore.
{noformat}

Also, we have seen cases queries fail when the catalogd crashes for some reason or another,
and the exact same error is produced:

{noformat}
[impalad-2.abc.xyz.com:21000] > show tables;
Query: show tables
ERROR: AnalysisException: This Impala daemon is not ready to accept user requests. Status:
Waiting for catalog update from the StateStore.
{noformat}

One error is a recoverable timing issue, the other is crashed processed. It would be nice
if these two conditions were differentiated by unique error messages.


> Improve error message in the event catalogd crashes
> ---------------------------------------------------
>
>                 Key: IMPALA-5105
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5105
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>            Reporter: David Knupp
>
> IMPALA-4704 documents a case whereby impalad opens up ports 21000 and 21050 before the
catalog update has been received, and this can lead to queries failing with the message:
> {noformat}
> AnalysisException: This Impala daemon is not ready to accept user requests. Status: Waiting
for catalog update from the StateStore.
> {noformat}
> Also, we have seen cases where queries fail when the catalogd crashes for some reason
or another, and the exact same error is produced:
> {noformat}
> [impalad-2.abc.xyz.com:21000] > show tables;
> Query: show tables
> ERROR: AnalysisException: This Impala daemon is not ready to accept user requests. Status:
Waiting for catalog update from the StateStore.
> {noformat}
> One error is a recoverable timing issue, the other is crashed processed. It would be
nice if these two conditions were differentiated by unique error messages.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message