sought.
So if your switches are configured to drop conns in an impolite way as
a defense against flooding, and maybe the default is 3 hours or 4hrs
15 minutes, then you can run into my behavior.
Thanks all for your attention and advice.
AJ
On Sat, Jun 19, 2010 at 8:16 PM, AJ Slater wrote:
>
ting my last mail to this list, succeeded.
So, its timing out, but al the while sending heartbeats and
GossipDIgestSyns and Acks back and forth and maybe not really querying
its peers when it should, or timing out trying to do so. When it
finally realizes theres an error, it resets something? And t
SynMessage to /10.33.3.10 ...
TRACE 19:42:04,229 Performing status check ...
AJ
On Sat, Jun 19, 2010 at 7:02 PM, Jonathan Ellis wrote:
> This is definitely not a Cassandra bug, something external is causing
> those connection failures.
>
> On Sat, Jun 19, 2010 at 3:12 PM, AJ Slate
tcpdump shows bidirectional communication with ACKs during a known
problem period. I did not have TRACE logging going during the period I
have tcpdump logs, but I assume that an 'INFO error connecting to' is
probably caused by ConnectExceptions
For instance...
lpc03:~$ telnet fs02 7000
...conne
org.apache.cassandra.net.OutboundTcpConnection.run(OutboundTcpConnect
ion.java:85)
On Sat, Jun 19, 2010 at 2:19 PM, AJ Slater wrote:
> I shall do just that. I did a bunch of tests this morning and the
> situation appears to be this:
>
> I have three nodes A, B and C, with RF=2. I understand now why this
&g
torage project is... uh... well... it could be better.
AJ
On Fri, Jun 18, 2010 at 8:16 PM, Jonathan Ellis wrote:
> set log level to TRACE and see if the OutboundTcpConnection is going
> bad. that would explain the message never arriving.
>
> On Fri, Jun 18, 2010 at 10:39 AM, AJ S
t
would be dropping heartbeats and I'd see that.
AJ
On Thu, Jun 17, 2010 at 2:26 PM, AJ Slater wrote:
> These are physical machines.
>
> storage-conf.xml.fs03 is here:
>
> http://pastebin.com/weL41NB1
>
> Diffs from that for the other two storage-confs are inline he
ur
> cassandra.in.sh and storage-conf.xml someplace?
>
> On Thu, Jun 17, 2010 at 10:31 AM, AJ Slater wrote:
>> Total data size in the entire cluster is about twenty 12k images. With
>> no other load on the system. I just ask for one column and I get these
>> timeouts. Perf
the symptoms you describe is that you
> are swapping.
>
> On Thu, Jun 17, 2010 at 10:12 AM, AJ Slater wrote:
>> I'm seing 10s timeouts on reads few times a day. Its hard to reproduce
>> consistently but seems to happen most often after its been a long time
>> between r
Jun 17, 2010 at 1:47 PM, aaron morton wrote:
> Do you have Row Caching enabled ? You can check in the JMX console to see if
> you're hitting the cache.
>
> Try turning on DEBUG level logging and look at the log on a machine you
> connect to do the read.
>
>
> Aaro
resolves itself and response times are down to
single digit milliseconds for a column get.
On Thu, Jun 17, 2010 at 10:24 AM, AJ Slater wrote:
> Cassandra 0.6.2 from the apache debian source.
> Ubunutu Jaunty. Sun Java6 jvm.
>
> All nodes in separate racks at 365 main.
>
> On Thu, Jun
Cassandra 0.6.2 from the apache debian source.
Ubunutu Jaunty. Sun Java6 jvm.
All nodes in separate racks at 365 main.
On Thu, Jun 17, 2010 at 10:12 AM, AJ Slater wrote:
> I'm seing 10s timeouts on reads few times a day. Its hard to reproduce
> consistently but seems to happen most
I'm seing 10s timeouts on reads few times a day. Its hard to reproduce
consistently but seems to happen most often after its been a long time
between reads. After presenting itself for a couple minutes the
problem then goes away.
I've got a three node cluster with replication factor 2, reading at
Its proper competitors are stuff like redis and memcached.
On Fri, Jun 4, 2010 at 8:19 AM, Jones, Nick wrote:
> I saw a tweet about claiming far better performance to Cassandra. After
> following up, I found out it requires the entire DB to reside in memory
> across the nodes.
>
>
>
> *Nick Jon
14 matches
Mail list logo
