Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 12-17-2018 11:45 AM
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 ?
Created 12-17-2018 03:39 PM
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>
Created 12-17-2018 03:39 PM
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>
Created 12-17-2018 04:10 PM
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 ?