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

Rituparna Agrawal commented on IMPALA-7532:
-------------------------------------------

Here is the message in impalad.FATAL

Log file created at: 2018/09/26 11:38:57
Running on machine: adb-test9-4.vpc.cloudera.com
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
F0926 11:38:57.980722 42971 impala-server.cc:389] LocalCatalogException: Unable 
to load database names
CAUSED BY: TException: org.apache.impala.common.InternalException: Couldn't 
open transport for adb-test9-2.vpc.cloudera.com:26000 (connect() failed: 
Connection refused)

CAUSED BY: InternalException: Couldn't open transport for 
adb-test9-2.vpc.cloudera.com:26000 (connect() failed: Connection refused)

. Impalad exiting.


> Add retry/back-off to fetch-from-catalog RPCs
> ---------------------------------------------
>
>                 Key: IMPALA-7532
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7532
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Todd Lipcon
>            Assignee: Tianyi Wang
>            Priority: Major
>
> Currently if there is an error connecting to the catalog server, the 'fetch 
> from catalog' implementation will retry with no apparent backoff. We should 
> retry for some period of time with backoff in between the attempts, so that 
> impala can ride over short interruptions of the catalog service.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to