Skip to content

Check for old configs#1

Merged
rzezeski merged 3 commits into
masterfrom
rz-check-old-config
May 30, 2012
Merged

Check for old configs#1
rzezeski merged 3 commits into
masterfrom
rz-check-old-config

Conversation

@rzezeski

Copy link
Copy Markdown
Contributor

Since users will more than likely not immediately update their app
configs before restarting Riak after an upgrade then Riak API needs to
check for the old configs. If the old config is found then that value
will be used and a warning will be logged.

This relies on basho/riak_core#182

Since users will more than likely not immediately update their app
configs before restarting Riak after an upgrade then Riak API needs to
check for the old configs.  If the old config is found then that value
will be used and a warning will be logged.
@seancribbs

Copy link
Copy Markdown

@rzezeski @kellymclaughlin The other alternative is to simply not start the PB listener when it is not configured, which is what riak_kv used to do. This means the supervisor will need to check whether it is enabled as well as the listener itself.

@rzezeski

Copy link
Copy Markdown
Contributor Author

Yea, that makes sense as some users may not want the PB interface enabled.

@seancribbs

Copy link
Copy Markdown

👍 to merge if you find my modifications sufficient

@rzezeski

Copy link
Copy Markdown
Contributor Author

This application is started before lager and therefore the log msgs don't show up but #2 is going to address that.

@rzezeski
rzezeski merged commit 5215a62 into master May 30, 2012
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

Successfully merging this pull request may close these issues.

2 participants