I have a few config files that I changed on my EMR cluster such as the zeppelin-env.sh, zeppelin-site.xml or tmux.conf. In each file I do minor changes such as add a few export lines. I', happy with those confs and now I want them all to be there on start up. I can save those conf files on my S3 and aws cp them with a bootstrap action but this feels like an overkill for a few line changes.
我在EMR集群上更改了一些配置文件，例如zeppelin-env.sh，zeppelin-site.xml或tmux.conf。在每个文件中，我做了一些小的更改，例如添加一些导出行。我对那些混乱感到高兴，现在我希望他们都能在那里开始。我可以将这些conf文件保存在我的S3上并使用引导操作来解决这些问题，但这对于几行更改感觉有些过分。
What is the best practice to change conf files on cluster creation?
在群集创建时更改conf文件的最佳做法是什么？
1 个解决方案
#1
1
Apparently zeppelin-site.xml is unneeded as everything can be overridden using the zeppelin-env.sh, which in turn can be configured with the configurations API. For application that I install using a BA, I will aws s3 cp per Henry's advice.
显然，zeppelin-site.xml是不需要的，因为可以使用zeppelin-env.sh覆盖所有内容，而zeppelin-env.sh又可以使用配置API进行配置。对于我使用BA安装的应用程序，根据Henry的建议，我将获得s3 cp。
#1
1
Apparently zeppelin-site.xml is unneeded as everything can be overridden using the zeppelin-env.sh, which in turn can be configured with the configurations API. For application that I install using a BA, I will aws s3 cp per Henry's advice.
显然，zeppelin-site.xml是不需要的，因为可以使用zeppelin-env.sh覆盖所有内容，而zeppelin-env.sh又可以使用配置API进行配置。对于我使用BA安装的应用程序，根据Henry的建议，我将获得s3 cp。