Increase cloudera CommandPusherThread execution timeout

[#1]

Hi all,

i'm trying to provising a 1 node cluster with no success it often fails with timeout.

checking cloudera manager logs i found this

/var/log/cloudera-scm-server/cloudera-scm-server.log:6924:2022-03-17 18:26:49,352 WARN CommandPusher-1:com.cloudera.server.cmf.CommandPusherThread: Aborting command 1546334130 (HiveCreateSysDb) because timeout value 330 seconds exceeded.
/var/log/cloudera-scm-server/cloudera-scm-server.log:7050:2022-03-17 18:33:38,262 WARN CommandPusher-1:com.cloudera.server.cmf.CommandPusherThread: Aborting command 1546334158 (HiveCreateSysDb) because timeout value 330 seconds exceeded.
/var/log/cloudera-scm-server/cloudera-scm-server.log:7211:2022-03-17 18:49:12,671 WARN CommandPusher-1:com.cloudera.server.cmf.CommandPusherThread: Aborting command 1546334161 (HiveCreateSysDb) because timeout value 330 seconds exceeded.
/var/log/cloudera-scm-server/cloudera-scm-server.log:7918:2022-03-17 21:01:22,709 WARN CommandPusher-1:com.cloudera.server.cmf.CommandPusherThread: Aborting command 1546334167 (HiveCreateSysDb) because timeout value 330 seconds exceeded.

how can i increase this value?

cloudera manager 7.4.4

thanks

regards,

C.

[#2]

Hi @AguniCat ,

Could you please provide the full stdout and stderr outputs?

André

[#3]

hi @araujo ,

thank you for your reply

> Could you please provide the full stdout and stderr outputs?

im not able to post the log here probably because it's too long.. any advice?

regards,

C.

[#4]

the provision randomly breaks in some steps

another example

stdout

Thu Mar 17 23:59:08 -03 2022
JAVA_HOME=/usr/java/jdk1.8.0_232-cloudera
using /usr/java/jdk1.8.0_232-cloudera as JAVA_HOME
using 7 as CDH_VERSION
using /var/run/cloudera-scm-agent/process/1546334223-hdfs-NAMENODE-format as CONF_DIR
using  as SECURE_USER
using  as SECURE_GROUP
CONF_DIR=/var/run/cloudera-scm-agent/process/1546334223-hdfs-NAMENODE-format
CMF_CONF_DIR=
unlimited
Formatting using clusterid: cluster1546333851

stderr

https://pastebin.com/aR7Yj4Nw

regards,c.

[#5]

@AguniCat ,

Please try restarting the agent with the command below and then try again.

systemctl restart cloudera-scm-agent

If it fails again, please share the agent log here (using pastebin): /var/log/cloudera-scm-agent/cloudera-scm-agent.log

Cheers,

André

--
Was your question answered? Please take some time to click on "Accept as Solution" below this post.
If you find a reply useful, say thanks by clicking on the thumbs up button.

[#6]

hi all,

it worked. i guess i was using fairly small sized hosts (1manager+3 workers 8gb ram) - lab reasons.

increasing each to 16gb made it through

thank you all

C.