For those playing along at home Edwards ticket was marked as a dup of
Problem with creating keyspace after drop
https://issues.apache.org/jira/browse/CASSANDRA-4219
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 30/08/2012, at 4:43 AM, Edw
> in terms of our high-rate write load cassandra1.0.11 is about 3 (three!!)
> times slower than cassandra-0.7.8
We've not had any reports of a performance drop off. All tests so far have show
improvements in both read and write performance.
> I agree, such digests save some network IO, but they
> *from 12 to 20 seconds (!!!) to find 5000 rows*.
More is not always better.
Cassandra must materialise the full 5000 rows and send them all over the wire
to be materialised on the other side. Try asking for a few hundred at a time
and see how it goes.
Cheers
-
Aaron Morto
describe_schema_versions on the thrift API
(SystemManager.describe_schema_versions() on pycassa) is what you are after.
Call it before hand to know what's what, and then call until all nodes converge
on the new schema.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
h
when we setup our new Cassandra Cluster recently, we looked at the problem
of what to do
when a node dies and needs to be replaced.
we could either let it be dead and have ops team spin up a new node and
manually assign a token to it;
we could also use Priam.
but our company uses Puppet to manage
This line always returns "0" because the key ByteBuffer has already been
read from.
startToken
=
partitioner.getTokenFactory().toString(partitioner.getToken(Iterables.getLast(rows).key));
I was able to get it to work by using .mark() and .reset() on the buffer.
I'll log a bug, but confused as to
--
Juan
Antonio Gomez Moriano
DEVELOPER
TEAM LEADER
nice, thanks guys!
On Tue, Aug 28, 2012 at 11:58 PM, Senthilvel Rangaswamy <
senthil...@gmail.com> wrote:
> We use Jolokia. Its pretty awesome.
>
>
> On Tue, Aug 28, 2012 at 11:44 PM, Peter Schuller <
> peter.schul...@infidyne.com> wrote:
>
>> I can recommend Jolokia highly for providing an HTTP/
Je suis absent(e) du bureau jusqu'au 19/09/2012
Remarque : ceci est une réponse automatique à votre message "Re: Node
forgets about most of its column families" envoyé le 29/08/2012 18:43:52.
C'est la seule notification que vous recevrez pendant l'absence de cette
personne.
Well I tried to drop the keyspace, but it's still there. No errors in logs and
Cassandra-cli showed the schema agreement after the command. I took a snapshot
of the system keyspace first. Nothing is crashing in the clients yet either,
still able to read/write to that keyspace.
[default@EBond
Hey all,
I'm having an issue using ColumnFamilyInputFormat in an hadoop job. The
mappers spin out of control and just keep reading records over and over,
never getting to the end. I have CF with wide rows (although none is past
about 5 at the columns at the moment), I've tried setting wide rows
You looking for the author of Spring Data Cassandra?
https://github.com/boneill42/spring-data-cassandra
If so, I guess that is me. =)
-brian
---
Brian O'Neill
Lead Architect, Software Development
Apache Cassandra MVP
Health Market Science
The Science of Better Results
2700 Horizon Drive Kin
is author of Spring - Cassandra here? I am interested in getting this
merged into upstream spring. They have cassandra support on their todo
list.
To elaborate, we don't know yet how to expose DCT in CQL3. If you can
give more background on what you're using DCT for, that would help.
(If we're lucky, it's also possible that you don't actually need DCT
-- Collections in 1.2 is done entirely with classic CT under the
hood.)
On Mon, Aug 27, 2
thanks!
On Wed, Aug 29, 2012 at 10:19 AM, Omid Aladini wrote:
> The change is introduced in 1.1.1 [1] which takes replication factor
> into account [2]. That's why 18.75% * 16 = 300% (which you have
> replication factor of 3).
>
> [1] https://issues.apache.org/jira/browse/CASSANDRA-3412
> [2]
> h
The change is introduced in 1.1.1 [1] which takes replication factor
into account [2]. That's why 18.75% * 16 = 300% (which you have
replication factor of 3).
[1] https://issues.apache.org/jira/browse/CASSANDRA-3412
[2]
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/
in terms of our high-rate write load cassandra1.0.11 is about 3 (three!!)
times slower than cassandra-0.7.8
after some investigation carried out I noticed files with "sha1" extension
(which are missing for Cassandra-0.7.8)
in maybeWriteDigest() function I see no option fot switching sha1 digests
o
Hi Aaron,
Thanks for the reply. I've recorded what we know at
https://issues.apache.org/jira/browse/CASSANDRA-4583.
This includes log snippets from two of the nodes from around the time. I
don't know what is relevant so they've got everything that was in the
system log at the time of the failur
On Wed, Aug 29, 2012 at 7:33 AM, Tiwari, Dushyant
wrote:
>
>
>
>
>
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions
> or views contained herein are not intended to be, and do not constitute,
> advice within the meaning of Section 975 o
The playOrm test suite drops the keyspace and recreates it for tests to wipe
out the in-memory or cassandra db. Today, we successfully ran our test suite
on a 6 node cluster. The one issue I had though was I needed to sleep after
keyspace creation and column family creation. BEFORE that I res
Sent from my iPhone
--
NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or
views contained herein are not intended to be, and do not constitute, advice
within the meaning of Section 975 of the Dodd-Frank Wall Stree
Thanks Peter.
This is 1.1.X ?
Any thoughts on how recent the last schema change was ?
Had the schema started in a pre 1.1X cluster? If so had their been a migration
change after 1.1 upgrade?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
> But the following nodetool repair crashes. It has to be stopped and then
> re-started.
How did it crash ?
> Are there any suggestions for logging or similar so that we can get a clue
> next time this happens.
Can you make the logs from #5 available?
If you feel you can describe the situation
> But does cassandra provide statistics at the granularity of rows.
No.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 29/08/2012, at 12:05 PM, Shankaranarayanan P N wrote:
> Hello,
>
> I have seen that cassandra gives CFstats that prov
Staggering the repairs also gives the DynamicSnitch a chance to route around
nodes which maybe running slow.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 29/08/2012, at 11:19 AM, Omid Aladini wrote:
>>> Secondly, what's the need for sl
It would be handy to work out what the corruption is. Could you snapshot the
system keyspace and store it somewhere, just incase we can look at it later ?
> Is there a way I can confirm this
Errors in the client and/or the server log is the the traditional way.
> go about cleaning up/restoring
> - if during the streaming session, the sstable that was about to stream out
> but was being compacted, would we see error in the log?
No.
Remember we never modify files on disk. And the "truth" contained in one file
generated by compaction is the same as the"truth" contained in the files befor
29 matches
Mail list logo
