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

Scylla cluster starts before server properties are read #8

Open
VladyslavKurmaz opened this issue Jun 28, 2017 · 0 comments
Open

Scylla cluster starts before server properties are read #8

VladyslavKurmaz opened this issue Jun 28, 2017 · 0 comments
Labels

Comments

@VladyslavKurmaz
Copy link
Collaborator

Issue

Server doesn't use Scylla server DNS name from the config.properties.
Whatever Scylla DNS is defined, server will use localhost

server_1    | com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: localhost/127.0.0.1:9042 (com.datastax.driver.core.exceptions.TransportException: [localhost/127.0.0.1:9042] Cannot connect), localhost/0:0:0:0:0:0:0:1:9042 (com.datastax.driver.core.exceptions.TransportException: [localhost/0:0:0:0:0:0:0:1:9042] Cannot connect))
server_1    |   at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:232)

Environment

  • Ubuntu 16.04
# java -version
openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.16.04.2-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)

Root cause

Scylla cluster starts before server reads properties from config.properties file.

Workaround

Hardcode Scylla server DNS name
server/src/main/java/ua/papka24/server/db/scylla/ScyllaCluster.java
ln 82

this.scyllaPath = "scylla";//scyllaPath;
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant