-
Notifications
You must be signed in to change notification settings - Fork 41
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
More helpful information when Sql4DClient fails to start #69
Comments
Hi @milimetric , try adding option -i 50 .I will fix this issue soon. BTW if you want to try out more here are some posts Thanks |
Awesome, thanks Kalyan, that allows me to connect. It looks like I'm On Thu, Mar 26, 2015 at 9:44 PM, srikalyan chandrashekar <
|
Hi the current version works with druid 0.6.154 , i have tagged with v3.5.6 , please clone and use that for druid 0.6.154. However for druid 0.7.0 we are working towards making it available ASAP. Here is the bug |
@milimetric Just released version 4.0.0 to maven which is compatible with druid 0.7.0 (or) just clone from master here and build. |
I have a standard Druid cluster set up with the pre-packaged configs, except I changed all the 8xxx ports to 9xxx. I have run mvn clean install successfully on Sql4D, and it has generated a Sql4DClient-3.5.6.jar. However, when I try to run the client with the configuration as instructed, it just prints the usage message and quits:
I may have some problem in my setup, though I see all my nodes running and logging meaningful stuff and I can query them, etc. But if I'm doing something wrong, it would be nice if the message from running the command told me what the exception was in parsing my args / trying to start.
Thanks btw, this seems like an awesome project.
The text was updated successfully, but these errors were encountered: