docker: binary transport protocol hosts #767
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… with the datastax driver (which uses a binary protocol)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when using the docker image to run Blueflood, it's impossible to have Blueflood connect to Cassandra when using the datastax driver. Reason for this is that only the CASSANDRA_HOSTS environment variable is set, which is used when using the astyanax driver, but the CASSANDRA_BINXPORT_HOSTS environment variable is not, which is used when using the datastax driver. Therefore Blueflood uses the default defined in CoreConfig.java, which is connecting to "localhost:9042".
This PR solves this by setting the CASSANDRA_BINXPORT_HOSTS environment variable in the docker-entrypoint.sh script.