Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine if FluoExec should read config from Zookeeper #898

Open
mikewalch opened this issue Aug 4, 2017 · 1 comment
Open

Determine if FluoExec should read config from Zookeeper #898

mikewalch opened this issue Aug 4, 2017 · 1 comment

Comments

@mikewalch
Copy link
Member

mikewalch commented Aug 4, 2017

Prior to #883, FluoExec read all configuration in fluo.properties and provided user with FluoConfiguration with everything set. After #883, all configuration is still provided but it is read from Zookeeper. This keeps expected behaviour but requires the Fluo application to be initialized and Zookeeper to be running. This ticket is figure out the best behaviour. If the read from Zookeeper is removed, commands that use FluoExec like OptimizeTable in Fluo Recipes will need to be modified.

@keith-turner
Copy link
Contributor

One possible way to handle this issue is to only use the fluo-conn.props if ZK not initialized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants