Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

ambari + log.retention.hours

avatar

hi all

log.retention.hours in kafka config is in hours

when I set it to small value as 0.5h , and then restart the kafka service

kafka service failed , seems because ambari not support this small value

so , is it possible any way to by-pass this limitation ? and set the log.retention.hours for example to 30m ?

Michael-Bronson
1 ACCEPTED SOLUTION

avatar

Hi @Michael Bronson,

Can you update the exact log exception in the operation log which blocked the start of Kafka service via ambari?

If the value cannot be set via UI , please see setting via command line helps

/var/lib/ambari-server/resources/scripts/configs.py -l <AMBARI_HOSTNAME> -t 8080 -u <USER_NAME> -p <PASSWORD> -a <GET/SET/DELETE>  -n <CLUSTER_NAME> -c <CONFIG_TYPE> -k <KEY> -v <VALUE> 

View solution in original post

2 REPLIES 2

avatar

Hi @Michael Bronson,

Can you update the exact log exception in the operation log which blocked the start of Kafka service via ambari?

If the value cannot be set via UI , please see setting via command line helps

/var/lib/ambari-server/resources/scripts/configs.py -l <AMBARI_HOSTNAME> -t 8080 -u <USER_NAME> -p <PASSWORD> -a <GET/SET/DELETE>  -n <CLUSTER_NAME> -c <CONFIG_TYPE> -k <KEY> -v <VALUE> 

avatar

but if from ambari we cant set it to 30m , then why API should work? from my understanding the value should set in XML , so what is the diffrences here ?

Michael-Bronson