About zbz

javicacheiro · ‎12-10-2018

One easy option in old CDH versions is just to change the shebang at the beginning of the script to: #!/usr/bin/env python2 Actually this will be more precise than the default, because the script is actually a python 2 script and ... python 3 is coming ... so it is good to be specific about the given version of the interpreter the script needs. We could be even more explicit and require python2.7.

zbz · ‎10-22-2018

Thank you so munch！ I change the group of '/tmp/logs' to hadoop , and restart the JobHistoryServer role, everything being OK. So happy !

bgooley · ‎10-08-2018

@JoaoBarreto, It is possible to do so, but it is not something we document or test exactly. The closest steps would be only doing the Cloudera Manager steps here: https://www.cloudera.com/documentation/enterprise/5-15-x/topics/install_singleuser_reqts.html#concept_ivr_lng_2v Since the agent runs as "root" by default, you shouldn't need to do any of the agent-specific steps there. Also, the Management Service "System User" and "System Group" are "cloudera-scm" by default. You may need to do a little trial and error to get everything working, but I don't think it would be too bad.

Online	Offline
Last Visited	‎07-09-2019 03:07 AM

Member Since	‎10-07-2018 10:55 PM
Last Visited	‎07-09-2019 03:07 AM
Posts	16

Cloudera Community

Re: topology.py not Python 3 compatible

Re: Yarn Aggregate Log Retention Setting

Re: Changing installation username from "cloudera-...