On 7 September 2012 00:42, aaron morton aa...@thelastpickle.com wrote:
1. When a write request is received, it is written to the base CF and
secondary index to secondary (hidden) CF. If this right, will the secondary
index be written local the node or will it follow RP/OPP to write to nodes.
This problem is not new to 1.1
That's what I understood from your last comment.
Is there a way to fix this error ? What is its impact on my data ?
Alain
2012/9/7 Peter Schuller peter.schul...@infidyne.com
This problem is not new to 1.1.
On Sep 6, 2012 5:51 AM, Radim Kolar h...@filez.com
We have upgraded a 0.8 cluster to 1.0.11. After upgrading the first node
and running upgradesstables, we have run a routine repair operation, This
operation has been running for a long time and does not seem to be
progressing.
Running netstats has shown unexpected values for percentages as shown
After a chat with driftx today, I tried wiping out my MigrationInfo on the
ring and rolling a restart. I then made a single change to the schema so at
least 1 migration would exist. Unfortunately the same error persists:
Previous version mismatch. Also occasionally the node is bootstrapping
You might want to change the name. There is a node.js driver for
cassandra with the same name. I am not sure which one of your got to
the name first.
On Thu, Sep 6, 2012 at 8:00 PM, aaron morton aa...@thelastpickle.com wrote:
Thanks Tomek,
Feel free to add it to
Hi All,
I have a question about node-tool drain on a single Cassandra 1.0.11 node:
If I use node-tool drain, it does stop accepting writes and flushes the
tables. However, is it normal that the commit log files are not deleted and
that it gets replayed?
Because if I do the following:
1) Write
Could you give me a URL to this stuff ?
2012/9/7 Edward Capriolo edlinuxg...@gmail.com
You might want to change the name. There is a node.js driver for
cassandra with the same name. I am not sure which one of your got to
the name first.
On Thu, Sep 6, 2012 at 8:00 PM, aaron morton
I attempted to manually load the Schema sstables onto the new node and
bootstrap it. Unfortunately when doing so, the new node believed it was
already bootstrapped, and just joined the ring with zero data.
To fix (read: hack) that, I removed the following logic from
StorageService.java:523:
So we wrote 1,000,000 rows into cassandra and ran a simple S-SQL(Scalable SQL)
query of
PARTITIONS n(:partition) SELECT n FROM TABLE as n WHERE n.numShares = :low and
n.pricePerShare = :price
It ran in 60ms
So basically playOrm is going to support millions of rows per partition. This
is
It's also some kind of OS (link: http://www.helenos.org/ ), not a really
unique name. However the software looks nice!
Best regards,
Robin Verlangen
*Software engineer*
*
*
W http://www.robinverlangen.nl
E ro...@us2.nl
Disclaimer: The information contained in this message and attachments is
Try to get Cassandra running the TPH-C benchmarks and beat oracle :)
On Fri, Sep 7, 2012 at 10:01 AM, Hiller, Dean dean.hil...@nrel.gov wrote:
So we wrote 1,000,000 rows into cassandra and ran a simple S-SQL(Scalable
SQL) query of
PARTITIONS n(:partition) SELECT n FROM TABLE as n WHERE
Now that would be cool. Right now though, to many other features need
to be added like a GUI on top of the ad-hoc query tool is the next top
priority so one can do any S-SQL statement and ad-hoc query the heck out
of a noSQL store.
We may even be able to optimize our queries to be even
This is the node.js driver with a similar name:
https://github.com/simplereach/helenus
On Fri, Sep 7, 2012 at 9:07 AM, Robin Verlangen ro...@us2.nl wrote:
It's also some kind of OS (link: http://www.helenos.org/ ), not a really
unique name. However the software looks nice!
Best regards,
Hi, I have successfully upgraded 2 nodes ring Cassandra with latest
version. After up-gradation, I found following exceptions. Please help
me to resolve this issue.
[2012-09-07 19:36:44,232] |TimedOutException()
me.prettyprint.hector.api.exceptions.HTimedOutException: TimedOutException()
Is there a way to fix this error ? What is its impact on my data ?
The fact that the message shows means that Cassandra has attempted to
repair the problem so there isn't much to do. However the fact that
you do get the messages in the first means that there is a bug
somewhere that generate
+1 What kinds of problems?
Cassandra uses identifier internally for each CF. If you concurrently
create CFs, you might end up with either two different CFs having the
same identifier or the same CF having two different identifiers (on
two different nodes). That in turn might likely trigger a
That obviously shouldn't happen and I don't remember any open ticket
related to that. You might want to open a ticket on jira
(https://issues.apache.org/jira/browse/CASSANDRA).
--
Sylvain
On Fri, Sep 7, 2012 at 10:50 AM, B R software.research.w...@gmail.com wrote:
We have upgraded a 0.8 cluster
I have a very reliable repro case on our cluster involving nodetool repair.
I posted a summary in a comment on the issue. Let me know if more details
are needed.
Charles
On Fri, Sep 7, 2012 at 8:35 AM, Sylvain Lebresne sylv...@datastax.comwrote:
Is there a way to fix this error ? What is its
On Fri, Sep 7, 2012 at 6:38 AM, Rene Kochen rene.koc...@schange.com wrote:
If I use node-tool drain, it does stop accepting writes and flushes the
tables. However, is it normal that the commit log files are not deleted and
that it gets replayed?
It's not expected by design, but it does seem to
Hello experts.
Should I limit the number of rows per Composite Primary Key's leading column?
I think it falls into the same wide row good practice for number of
columns per row for CQL 2.0, e.g. 10M or less.
Any comments will be appreciated.
--
Thanks,
Charlie (@mujiang) 木匠
===
Data
20 matches
Mail list logo
