Hmm, I wish that were the case, since once those messages start appearing ..
they never stop .. resulting in timeouts on all client requests until I stop
the server.
When I restart the server and try querying for anything via the index the
messages then resumed.
Right now the problem has gone awa
If you're not seeing the NullPointerException at this point, things
are probably good. These messages are expected when logging at DEBUG.
Gary.
On Tue, Oct 12, 2010 at 02:35, J T wrote:
> I rinsed & repeated after updating to the latest trunk version and checking
> if the 1571 patch was include
I rinsed & repeated after updating to the latest trunk version and checking
if the 1571 patch was included (which it appeared to be) and the start of
the repeating error sequence was:
DEBUG [pool-1-thread-21] 2010-10-12 08:30:31,143 ClientState.java (line 81)
logged in: #
DEBUG [pool-1-thread-21]
Hi,
Looks like I was premature in my response.
I had cause today to wipe my datastore and restart cassandra and reload the
.yaml containing the schema definition.
After doing a restart of my app which essentially inserted into a CF with a
2ndary idx and then queried that CF I was left with log f
Hi,
On a first pass, that patch seems to have solved the problem.
I'll be testing that functionality repeatedly in the next day or so I'll let
you know how it fairs.
Thanks
Jason
On Wed, Oct 6, 2010 at 4:06 PM, Stu Hood wrote:
> Hey JT,
>
> I believe this issue should be fixed by CASSANDRA-15
Hey JT,
I believe this issue should be fixed by CASSANDRA-1571... if you're able to
test that patch, it would be very helpful.
Thanks,
Stu
-Original Message-
From: "J T"
Sent: Tuesday, October 5, 2010 9:50pm
To: cassandra-u...@incubator.apache.org
Subject: Null Pointer Exception / Seco
