Michael,
The ask is for letting keep alive be configurable for native transport,
with Socket.setKeepAlive. By default, SO_KEEPALIVE is false (
http://docs.oracle.com/javase/7/docs/api/java/net/StandardSocketOptions.html#SO_KEEPALIVE).
Regards,
Eric Plowe
On Wed, Apr 9, 2014 at 1:25 PM, Michae
socket.nio.NioWorker.run(NioWorker.java:178)
>> >> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
>> >> Source)
>> >> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>> >> Source)
>> >>
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> >> Source)
> >> at java.lang.Thread.run(Unknown Source)
> >>
> >> Initially we thought this was down to a firewall that is between our
> >> development machines and the Cassandra nod
es and the Cassandra nodes but that has now been
>> configured not to 'kill' any connections on port 9042. We also have the
>> Windows firewall on the client side turned off.
>>
>> We still think this is down to our environment as the same application
>> runnin
oes not appear to be
> doing this but up to now we can't track down the cause.
>
>
>
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/binary-protocol-server-side-sockets-tp7593879p7593937.html
> Sent from the
omcat hosted on a Ubuntu 12.04 server does not appear to be
doing this but up to now we can't track down the cause.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/binary-protocol-server-side-sockets-tp7593879p7593937.html
Sent from the
I am having the exact same issue. I see the connections pile up and pile
up, but they never seem to come down. Any insight into this would be
amazing.
Eric Plowe
On Wed, Apr 9, 2014 at 4:17 PM, graham sanderson wrote:
> Thanks Michael,
>
> Yup keepalive is not the default. It is possible they
Thanks Michael,
Yup keepalive is not the default. It is possible they are going away after
nf_conntrack_tcp_timeout_established; will have to do more digging (it is hard
to tell how old a connection is - there are no visible timers (thru netstat) on
an ESTABLISHED connection))…
This is actuall
On 04/09/2014 12:41 PM, graham sanderson wrote:
Michael, it is not that the connections are being dropped, it is that
the connections are not being dropped.
Thanks for the clarification.
These server side sockets are ESTABLISHED, even though the client
connection on the other side of the netw
Michael, it is not that the connections are being dropped, it is that the
connections are not being dropped.
These server side sockets are ESTABLISHED, even though the client connection on
the other side of the network device is long gone. This may well be an issue
with the network device (it i
On 04/09/2014 11:39 AM, graham sanderson wrote:
Thanks, but I would think that just sets keep alive from the client end;
I’m talking about the server end… this is one of those issues where
there is something (e.g. switch, firewall, VPN in between the client and
the server) and we get left with or
Thanks, but I would think that just sets keep alive from the client end; I’m
talking about the server end… this is one of those issues where there is
something (e.g. switch, firewall, VPN in between the client and the server) and
we get left with orphaned established connections to the server wh
Hello Graham
You can use the following code with the official Java driver:
SocketOptions socketOptions = new SocketOptions();
socketOptions.setKeepAlive(true);
Cluster.builder().addContactPoints(contactPointsList)
.withPort(cql3Port)
.withCompr
Is there a way to configure KEEPALIVE on the server end sockets of the binary
protocol.
rpc_keepalive only affects thrift.
This is on 2.0.5
Thanks,
Graham
smime.p7s
Description: S/MIME cryptographic signature
14 matches
Mail list logo
