my 2 cents:
try major compaction on the column family with TTL's - for sure will be
faster than full rebuild.
also try not cassandra related things, such check and remove old log files,
backups etc.
On Wed, Oct 1, 2014 at 9:34 AM, Sumod Pawgi wrote:
> In the past in such scenarios it has helpe
In the past in such scenarios it has helped us to check the partition where
cassandra is installed and allocate more space for the partition. Maybe it is a
disk space issue but it is good to check if it is related to the space
allocation for the partition issue. My 2 cents.
Sent from my iPhone
This is a shot into the dark but you could check whether you have too many
snapshots laying around that you actually don't need. You can get rid of
those with a quick "nodetool clearsnapshot".
On Wed, Oct 1, 2014 at 5:49 AM, cem wrote:
> Hi All,
>
> I have a 7 node cluster. One node ran out of d
Hello Matthias
According to your description, an event-sourcing design would be a good
fit for your scenario.
In Cassandra, instead of "updating" existing data, why don't you just
store new values (it can be delta only, not a problem) with a monotonic
increasing date ?
This way, in your analy
Hi All,
I have a 7 node cluster. One node ran out of disk space and others are
around 80% disk utilization.
The data has 10 days TTL but I think compaction wasn't fast enough to clean
up the expired data. gc_grace value is set default. I have a replication
factor of 3. Do you think that it may he
Also be aware of https://issues.apache.org/jira/browse/CASSANDRA-7734 if you
are using C* 2.0.6+ (2.0.6 introduced a change that can sometimes causes
initial schema propagation not to happen, introducing potentially long delays
until some other code path repairs it later)
On Sep 30, 2014, at 1:
I think Sylvain may not have had his coffee yet. You can't use IF's in
SELECT statements, but you can in INSERT/UPDATE/DELETE:
UPDATE foo SET a = 0 WHERE k = 0 IF b != 0;
On Tue, Sep 30, 2014 at 2:36 AM, Sylvain Lebresne
wrote:
>
>
>> Is != supported as part of the where clause in Cassandra?
>
Only recently! Moving off list (c* users bcc'd).
On 30 September 2014 19:20, Andrew Cobley wrote:
> HI Ben,
>
> yeah, that was it, recovered from the Cassandra summit ?
>
>
> Andy
>
> On 30 Sep 2014, at 08:19, Ben Bromhead wrote:
>
> check your cqlshrc file (sometimes in ~/.cassandra) ?
>
Hi all,
i'm unsure if cassandra is appropriate for my use case:
Maintain a query model.
Collect data from several sources (asynchronously) and merge it into
aggregates (rows) in one cassandra table.
The data is mostly updated, except from initial load or adding new data
ranges.
Some source deliv
HI Ben,
yeah, that was it, recovered from the Cassandra summit ?
Andy
On 30 Sep 2014, at 08:19, Ben Bromhead
mailto:b...@instaclustr.com>> wrote:
check your cqlshrc file (sometimes in ~/.cassandra) ?
I've been caught out before when playing with a RC of 2.1
On 30 September 2014 01:25, Andre
I too have saved images in blobs (in development environment admittedly) .
Sample code can be seen here:
https://github.com/acobley/instagrim/blob/master/src/main/java/uk/ac/dundee/computing/aec/instagrim/models/PicModel.java
Note this code uses the org.imgscalr.Scalr to resize and process ima
MySQL Cluster (don't use FKs yet) or Redis (in-memory databases) sound more
appropriate
for data that churns a lot.
Thanks, James Briggs.
--
Cassandra/MySQL DBA. Available in San Jose area or remote.
cass_top: https://github.com/jamesbriggs/cassandra-top
On Tue, Sep 30, 2014 at 2:25 AM, Robert Coli wrote:
> On Mon, Sep 22, 2014 at 3:50 AM, Carlos Scheidecker
> wrote:
>
>> I can successfully read a file to a ByteBuffer and then write to a
>> Cassandra blob column. However, when I retrieve the value of the column,
>> the size of the ByteBuffer ret
>
> Is != supported as part of the where clause in Cassandra?
>
It's not.
Or is it the grammar for some other purpose?
>
It's supported in 'IF' conditions. You can do something like:
SELECT * FROM foo WHERE k = 0 IF v != 3;
--
Sylvain
check your cqlshrc file (sometimes in ~/.cassandra) ?
I've been caught out before when playing with a RC of 2.1
On 30 September 2014 01:25, Andrew Cobley wrote:
> Without the apache cassandra running I ran jps -l on this machine ,the
> only result was
>
> 338 sun.tool.jps.Jps
>
> The Mac did
I'm guessing your talking about multi-homing because you want to have
multiple tenants (different apps/ teams etc) to make better use of
resources ?
As Jared mentioned running multiple Cassandra processes on the same
hardware that participate in the same cluster doesn't make much sense from
a fail
16 matches
Mail list logo
