Re: NoHostAvailableException

Hi, as I mentioned about rpc_address: 0.0.0.0 YAML says it is allowed to specify 0.0.0.0 ... but that will break clients that rely on node auto-discovery. Try set rpc_address: external_ip Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes.

Re: NoHostAvailableException

Hi Vladimir, I have attached cassandra.yaml we have in our setup, please check once. - do you have native port 9042 open in firewall ? Yes, 9042 is opened on our firewall, checked with our team - Can you connect to cluster with cqlsh? Yes, Im able to connect cluster using cqlsh. What else could

Re: NoHostAvailableException

Yaml in 2.0.17 says # The address to bind the Thrift RPC service and native transport # server -- clients connect here. # # Leaving this blank has the same effect it does for ListenAddress, # (i.e. it will be based on the configured hostname of the node). # # Note that unlike ListenAddress a

Re: NoHostAvailableException

Sorry it was typo.. It is *broadcast_address and not **broadcast_*rpc*_address.* And also there is no such configuration in cass.yaml with *broadcast_rpc_address *in c*-2.0.17. Very sorry once again. This is configrn I have in cass.yaml *listen_address: [external IP]* *# Address to broadcast to

Re: NoHostAvailableException

Not broadcast_address, but broadcast_rpc_address (you gave this example:rpc_address: 0.0.0.0 , broadcast_rpc_address: 1.2.3.4) Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Mon, 21 Nov 2016 08:14:38 -0500techpyaasa .

Re: NoHostAvailableException

Hi Vladimir, I have not modified anything for broadcasr_address, I left as it was.. *# Leaving this blank will set it to the same value as listen_address* *# broadcast_address: 1.2.3.4* So the comment above says "*Leaving this blank will set it to the same value as listen_address" *, so it shud

Re: NoHostAvailableException

Try to set broadcast_rpc_address on each node to its real external IP address. Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Mon, 21 Nov 2016 05:47:00 -0500techpyaasa . wrote Following exception

Re: NoHostAvailableException coming up on our server

Thanks a lot for suggestion Romain, I have done the setup to see the driver logs, but haven't seen that error again. Also thanks for the MaxRequestPerConnection tip, I will change it to 32K. Regards, Abhinav On Wed, Jul 13, 2016 at 1:02 PM Romain Hardouin wrote: > Put the driver logs in debug m

Re: NoHostAvailableException coming up on our server

Put the driver logs in debug mode to see what's happen.Btw I am surprised by the few requests by connections in your setup: .setConnectionsPerHost(HostDistance.LOCAL, 20, 20) .setMaxRequestsPerConnection(HostDistance.LOCAL, 128) It looks like a protocol v2 settings (Cassandra 2.0

Re: NoHostAvailableException coming up on our server

I am using 3.0.0 version over apache-cassandra-3.3 On Tue, Jul 12, 2016 at 2:37 PM Riccardo Ferrari wrote: > What driver version are you using? > > You can look at the LoggingRetryPolicy to have more meaningful messages in > your logs. > > best, > > On Tue, Jul 12, 2016 at 9:02 PM, Abhinav Solan

Re: NoHostAvailableException coming up on our server

What driver version are you using? You can look at the LoggingRetryPolicy to have more meaningful messages in your logs. best, On Tue, Jul 12, 2016 at 9:02 PM, Abhinav Solan wrote: > Thanks, Johnny > Actually, they were running .. it went through a series of read and writes > .. and recovered

Re: NoHostAvailableException coming up on our server

Thanks, Johnny Actually, they were running .. it went through a series of read and writes .. and recovered after the error. Is there any settings I can specify in preparing the Session at java client driver level, here are my current settings - PoolingOptions poolingOptions = new PoolingOptions()

Re: NoHostAvailableException coming up on our server

Abhinav - your getting that as the driver isn’t finding any hosts up for your query. You probably need to check if all the nodes in your cluster are running. See: http://docs.datastax.com/en/drivers/java/3.0/com/datastax/driver/core/exceptions/NoHostAvailableException.html Johnny > On 12 Jul 2

Re: NoHostAvailableException/TransportException

On Thu, Oct 31, 2013 at 10:01 AM, Les Hartzman wrote: > I did notice on startup the message "JNA not found. Native methods will > be disabled". Not sure if this means anything or not. > While not relevant to the problem you were having, in general one really does want to have JNA available when

Re: NoHostAvailableException/TransportException

Thank you! That was it. Les On Thu, Oct 31, 2013 at 10:06 AM, Sylvain Lebresne wrote: > cqlsh uses thrift, the java driver uses the native protocol. Thirft is on > port 9160 by default, the native protocol is on port 9042 by default. Try > connecting on port 9042 with the driver instead (which

Re: NoHostAvailableException/TransportException

cqlsh uses thrift, the java driver uses the native protocol. Thirft is on port 9160 by default, the native protocol is on port 9042 by default. Try connecting on port 9042 with the driver instead (which is the driver default really). -- Sylvain On Thu, Oct 31, 2013 at 6:01 PM, Les Hartzman wrot