created https://issues.apache.org/jira/browse/CASSANDRA-794 for this
On Fri, Feb 12, 2010 at 2:38 PM, ruslan usifov ruslan.usi...@gmail.com wrote:
Also i have problem with StreamInitiateVerbHandler, the problem in
PendingFile.getTargetFile, namely difference in slashes on win and unix, so
i
are you mixing windows and unix machines in the same cluster?
On Fri, Feb 12, 2010 at 2:38 PM, ruslan usifov ruslan.usi...@gmail.com wrote:
Also i have problem with StreamInitiateVerbHandler, the problem in
PendingFile.getTargetFile, namely difference in slashes on win and unix, so
i change
Ruslan,
I think this indicates that SO_SNDBUF is too small on windows.
Windows is the source, freebsd is the destination, correct?)
I've created https://issues.apache.org/jira/browse/CASSANDRA-795 to
track this. Can you apply the patch attached to it to see if it
addresses the problem?
Thanks.
Yes, for test case
2010/2/15 Jonathan Ellis jbel...@gmail.com
are you mixing windows and unix machines in the same cluster?
On Fri, Feb 12, 2010 at 2:38 PM, ruslan usifov ruslan.usi...@gmail.com
wrote:
Also i have problem with StreamInitiateVerbHandler, the problem in
Hi,
I just installed cassandra using the Debian package on two
servers, _db1a_, and _db1b_.
When I run the command _nodeprobe -host db1a
ring_, the command only works on the server db1a.
iptables is set to
allow everything.
I did also add the
-Djava.rmi.server.hostname=192.168.1.13 to
On Mon, Feb 15, 2010 at 1:13 PM, Shahan Khan cont...@shahan.me wrote:
db1b:~# nodeprobe -host db1a ring
Error connecting to remote JMX agent!
java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested
exception is:
This seems to indicate that db1a resolves as 127.0.0.1 on
I tried Brandon's suggestion, but am still getting the same error on the
remote server.
Any other suggestions? Is it possible that its a bug?
Thanks,
Shahan
db1a = 192.168.1.13
db1b = 192.168.1.14
=
db1a:~# nodeprobe -host 192.168.1.14 ring
Error
connecting to
It seems that read latency is sensitive to number of threads (or thrift
clients): after reducing number of threads to 15 and read latency decreased
to ~20ms.
The other problem is: if I keep mixed write and read (e.g, 8 write threads
plus 7 read threads) against the 2-nodes cluster continuously,
