Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Deploy Client Config retries infinitely after failure

Solved Go to solution

Deploy Client Config retries infinitely after failure

Explorer

I have a custom CSD with a gateway service role that runs a control script command at deploy client config.

 

when the control script fails (script returns non-zero), the UI reports failure but the command seems to be retried infinitely (did a ps auxf on any host that has the gateway role). 

Furthermore, i cannot investigate the logs in the ccdeploy directory since the directory is constantly wiped. 

 

Are these retries intended or can i signal no retry with a specific exit code?

 

thanks

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Deploy Client Config retries infinitely after failure

Hi,

CM will continually re-try client config deployment. This is helpful in particular if the host is temporarily not available and comes online later. It makes it easier for the administrator to reason about the state of client configs, so you don't have to worry about re-executing the command on a few random hosts that weren't operational at the time of deploy. So the retries are intended.

Ideally, the deploy scripts should be so simple that they can't really fail. If you're just debugging your changes, then you can stop the CM agent (service cloudera-scm-agent stop) on that host to stop the wiping / retry logic and make it easier to debug.

Thanks,
Darren
1 REPLY 1

Re: Deploy Client Config retries infinitely after failure

Hi,

CM will continually re-try client config deployment. This is helpful in particular if the host is temporarily not available and comes online later. It makes it easier for the administrator to reason about the state of client configs, so you don't have to worry about re-executing the command on a few random hosts that weren't operational at the time of deploy. So the retries are intended.

Ideally, the deploy scripts should be so simple that they can't really fail. If you're just debugging your changes, then you can stop the CM agent (service cloudera-scm-agent stop) on that host to stop the wiping / retry logic and make it easier to debug.

Thanks,
Darren
Don't have an account?
Coming from Hortonworks? Activate your account here