You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we can run virgil by bin/virgil -host and
the listening port of my cassandra node is 9170 instead of 9160...
but I can't set the port in virgil...so I can't run virgil to listen my cassandra cluster...
The text was updated successfully, but these errors were encountered:
I'll check to make sure the port is being passed through. We may have lost that parameter in the conversion to dropwizard.
-brian
On Aug 17, 2012, at 2:34 AM, sainthxd wrote:
we can run virgil by bin/virgil -host and
the listening port of my cassandra node is 9170 instead of 9160...
but I can't set the port in virgil...so I can't run virgil to listen my cassandra cluster...
—
Reply to this email directly or view it on GitHub.
Looks like it is now pulled from a system parameter in VirgilConfiguration.java:
public static int getPort() {
return Integer.parseInt(System.getProperty(VirgilConfiguration.CASSANDRA_PORT_PROPERTY));
}
That is certainly less than ideal. I know we had issues moving it to a command line parameter though because of dropwizard. I'll see if dropwizard has fixed the issue. If not, we can move it into the yaml file.
we can run virgil by bin/virgil -host and
the listening port of my cassandra node is 9170 instead of 9160...
but I can't set the port in virgil...so I can't run virgil to listen my cassandra cluster...
The text was updated successfully, but these errors were encountered: