You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "bharath v (JIRA)" <ji...@apache.org> on 2018/09/19 19:34:00 UTC

[jira] [Commented] (IMPALA-7498) impalad should wait for catalogd during start up

    [ https://issues.apache.org/jira/browse/IMPALA-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621102#comment-16621102 ] 

bharath v commented on IMPALA-7498:
-----------------------------------

Todd, I looked at the code and I don't think it will retry 3 times and then exit. It may be true in the earlier versions of V2 feature but I'm not able to track down the 3-time retry loop. Please correct me if I'm wrong.

It waits indefinitely for the initial update but the issue happens to be with the log-spew. I've sent out of a patch here http://gerrit.cloudera.org:8080/11472 to fix it.

> impalad should wait for catalogd during start up
> ------------------------------------------------
>
>                 Key: IMPALA-7498
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7498
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Todd Lipcon
>            Assignee: bharath v
>            Priority: Major
>
> If you start all daemons simultaneously, impalad with --use_local_catalog enabled will retry three times in a tight loop trying to fetch the DB names, and then exit. Instead it should loop for some amount of time waiting for the catalog to be ready in the same way that the existing implementation does.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org