Hi,
I am trying to taking snapshot of my data but faced following error.
Please help me to resolve this issue.
[root@cassandra1 bin]# ./nodetool -h localhost snapshot 20120711
Exception in thread main java.io.IOError: java.io.IOException: Cannot
run program ln: java.io.IOException: error=12
.
Please help me to resolve this issue.
[root@cassandra1 bin]# ./nodetool -h localhost snapshot 20120711
Exception in thread main java.io.IOError: java.io.IOException:
Cannot run program ln: java.io.IOException: error=12, Cannot allocate
memory
Hi,
I'm trying to tune, memtable size, key cache size and heap size on
Cassandra 1.1.0 but I keep having memory pressure and reduced cache size.
With the following settings:
heap size: 10GB (had the same issue with 8GB so I'm testing with increased
heap size)
memtable_total_space_in_mb: 2GB
Greetings.
Running (CQL 3) queries like:
update users set admin = 1 where corporation_id =
'7a55bc4c-84e7-479c-9ac6-43f7836705b5';
… I see in logs a row like:
StorageProxy.java (line 175) Mutations/ConsistencyLevel are
[RowMutation(keyspace='goh_test',
I see.
The reason I looked at that package was, I need to use the batch feature, and I
could not make it work using thrift with the CF having composite key. It worked
fine with the simple key, but not composite, I was getting an error while
trying to do the update.
Sylvain suggested (in reply
There is no rounding or correction whatsoever. It just happens that if
you don't give a timestamp in CQL, the timestamp is generated server
side using that Java System.currentTimeMillis() that only provide
milliseconds precision. If you provide your own timestamp however we
use it without doing
When I said to use the BATCH statement I mean't using a query that is
a BATCH statement, so something like:
BEGIN BATCH
INSERT ...;
INSERT ...;
...
APPLY BATCH;
If you want to that from java, you will want to look at the jdbc
driver
Thanks Sylvain, I actually tried the prepared batch, works fine. I did the 1000
rows in one batch, 20 columns each, and it was good. Then I tried 1, and it
still works, I am going to measure which way it is faster overall.
-Original Message-
From: Sylvain Lebresne
Coming back on this thread, we are proud to announce we opened a Swiss
BigData UserGroup.
http://www.bigdata-usergroup.ch/
Next meetup is July 16, with topic NoSQL Storage: War Stories and
Best Practices.
Hope to meet you there !
Benoit.
2012/5/17 Sasha Dolgy sdo...@gmail.com:
All,
A year
Hi,
at the moment I'm doing research about keeping linked/connected file list
in Cassandra- e.g. PDF file cut into pages (multiple PDFs) where first page
is connected to second, second to third etc.
This files connection/link is not specified. Main goal is to be able to
get all linked files (the
I would use something other than the page itself as the key. Maybe a
filename, something smaller.
Then you could use a LongType comparator for the columns and use the page
number for the column name, the value being the contents of the files.
On Wed, Jul 11, 2012 at 1:34 PM, Tomek Hankus
why not just hold the pages as different columns in the same row? columns are
automatically sorted such that if the column name was associated with the page
number it would automatically flow the way you wanted. - Original Message
-From: quot;Tomek Hankusquot; ;tom...@gmail.com
Hi:
We are currently using Cassandra 0.8.10 and have run into some strange issues
surrounding
querying for a range of data
I ran a couple of get statements via the Cassandra client and found some
interesting results:
Consider the following Column Family Definition:
ColumnFamily:
Thanks Jonathan that did the trick. I deleted the Statistics.db files
for the offending column family and was able to get Cassandra to
start.
Thank you,
Jason
Using PropertyFileSnitch you can fine tune the topology of the cluster.
What you tell Cassandra about your DC and rack doesn't have to match how
they are in real life. You can create virtual DCs for Cassandra and even treat
each node as a separate rack.
For example, in
out of curiosity, is there a way that Cassandra can communicate that it's
close to the being overloaded ?
On Sun, Jun 17, 2012 at 6:29 PM, aaron morton aa...@thelastpickle.comwrote:
http://wiki.apache.org/cassandra/FAQ#dropped_messages
https://www.google.com/#q=cassandra+dropped+messages
Hello
Currently we are using Cassandra 1.0.6 in our production system but suffer
with the CASSANDRA-3616 (it is already fixed in 1.0.7 version).
We thought to upgrade the Cassandra to 1.1.X versions, to get it's new
features, but having some concerns about the upgrade and expert advices are
As far as I know there isn't any way to use the rack name in the
strategy_options for a keyspace. You
might want to look at the code to dig into that, perhaps.
Aha, I was wondering if I could do that as well ( specify rack options ) :)
Thanks for the pointer, I will dig into the code.
Since replication factor is 2 in first cluster, I
won't lose any data.
Assuming you have been running repair or working at CL QUORUM (which is the
same as CL ALL for RF 2)
Is it advisable and safe to go ahead?
um, so the plan is to turn off 2 nodes in the first cluster, restask them into
the
I don't think it's related to 4337.
There is an explicit close call just before the deletion attempt.
Can you create a ticket on https://issues.apache.org/jira/browse/CASSANDRA with
all of the information you've got here (including the full JVM vendor, version,
build). Can you also check if
error. Please
help me to resolve this issue.
[root@cassandra1 bin]# ./nodetool -h localhost snapshot 20120711
Exception in thread main java.io.IOError: java.io.IOException: Cannot run
program ln: java.io.IOException: error=12, Cannot allocate memory
JMX is really the only way it exposes that kind of information. I
recommend setting up mx4j if you want to check on the server stats
programmatically.
On Wed, Jul 11, 2012 at 8:17 PM, Frank Hsueh frank.hs...@gmail.com wrote:
out of curiosity, is there a way that Cassandra can communicate that
On Wed, Jul 11, 2012 at 8:38 PM, Roshan codeva...@gmail.com wrote:
Currently we are using Cassandra 1.0.6 in our production system but suffer
with the CASSANDRA-3616 (it is already fixed in 1.0.7 version).
We thought to upgrade the Cassandra to 1.1.X versions, to get it's new
features, but
I highly recommend specifying the same rack for all nodes (using
cassandra-topology.properties) unless you really have a good reason not too
(and you probably don't). The way that replicas are chosen when multiple
racks are in play can be fairly confusing and lead to a data imbalance if
you don't
24 matches
Mail list logo
