Naresh, are you deploying cassandra in windows?
If that is the case you may need to change the data and commitlog
directories in cassandra.yaml. Also you should check the log directories.
See the section 2.1 http://wiki.apache.org/cassandra/GettingStarted
On Tue, Aug 13, 2013 at 8:28 AM,
Carlo,
Do you read/write with the consistency levels according to your needs [1]?
Have you tried to see if it happens when using the cassandra-cli to get
that data?
[1] http://wiki.apache.org/cassandra/ArchitectureOverview
On Wed, Jul 24, 2013 at 5:34 PM, cbert...@libero.it
, Richard Low rich...@wentnet.com wrote:
On 19 July 2013 23:31, Alexis Rodríguez arodrig...@inconcertcc.comwrote:
Hi guys,
I've read here [1] that you can make a deletion mutation for the
future. That mechanism operates as a schedule for deletions according to
the stackoverflow post. But, I've
That repo for libcassandra works for cassandra 0.7.x due to changes in the
thrift interface we have faced some problems in the past.
May be you can take a look to my fork of libcassandra https://github.com/axs
-mvd/libcassandra that we are using with cassandra 1.1.11.
Besides that, I recommend
creation and insertion work will still need thrift calls.
On Wed, Jul 3, 2013 at 6:05 PM, Alexis Rodríguez
arodrig...@inconcertcc.com wrote:
That repo for libcassandra works for cassandra 0.7.x due to changes in
the thrift interface we have faced some problems in the past.
May be you can take
Nicolai,
Perhaps you can check the system.log to see if there are any errors on
compaction. Also, I believe C* 1.2.0 it's not a stable version.
On Thu, May 9, 2013 at 2:43 AM, Nicolai Gylling n...@issuu.com wrote:
Hi
I have a 3-node SSD-based cluster, with around 1 TB data, RF:3, C*
Kenjale
On Wed, Apr 17, 2013 at 6:58 PM, Alexis Rodríguez
arodrig...@inconcertcc.com wrote:
Jay,
I believe that compaction occurs on the data directories and not in the
commitlog.
http://wiki.apache.org/cassandra/MemtableSSTable
On Wed, Apr 17, 2013 at 7:58 PM, Jay Svc jaytechg
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 18/04/2013, at 11:58 AM, Alexis Rodríguez
arodrig...@inconcertcc.com wrote:
Jay,
I believe that compaction occurs on the data directories and not in
the commitlog
:D
Jay, check if your disk(s) utilization allows you to change the
configuration the way Edward suggest. iostat -xkcd 1 will show you how much
of your disk(s) are in use.
On Wed, Apr 17, 2013 at 5:26 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
three things:
1) compaction throughput is
(minor or major), long after all its records have been deleted. This causes
disk usage to rise dramatically. The only way to make the SStable files
disappear is to run “nodetool cleanup” (which takes hours to run).
** **
Just a theory so far….
** **
*From:* Alexis Rodríguez
Adeel,
It may be a problem in the remote node, could you check the system.log?
Also you might want to check the rpc_timeout_in_ms in both nodes, maybe an
increase in this parameter helps.
On Fri, Apr 12, 2013 at 9:17 AM, adeel.ak...@panasiangroup.com wrote:
Hi,
I have started repair on
Aaron,
It seems that we are in the same situation as Nury, we are storing a lot of
files of ~5MB in a CF.
This happens in a test cluster, with one node using cassandra 1.1.5, we
have commitlog in a different partition than the data directory. Normally
our tests use nearly 13 GB in data, but when
Hi guys!
We are getting the following message in our logs
ERROR [CompactionExecutor:535] 2012-10-31 12:14:14,254 CounterContext.java
(line 381) invalid counter shard detected;
(ea9feac0-ec3b-11e1--fea7847157bf, 1, 60) and
(ea9feac0-ec3b-11e1--fea7847157bf, 1, -60) differ only in count;
cassandra-people,
I'm trying to measure disk usage by cassandra after inserting some columns
in order to plan disk sizes and configurations for future deploys.
My approach is very straightforward:
clean_data (stop_cassandra rm -rf
/var/lib/cassandra/{dara,commitlog,saved_caches}/*)
14 matches
Mail list logo
