Hi,
I have filed a fix as CASSANDRA-8038, which would be a good news for those
who has suffered from overwhelming GC or OOM by tombstones.
Appreciate your feedbacks!
Thanks,
Takenori
Anti-pattern. Dynamically altering the schema won't scale and is bad ju ju.
--
Colin Clark
+1-320-221-9531
> On Oct 6, 2014, at 10:56 PM, Todd Fast wrote:
>
> There is a team at my work building a entity-attribute-value (EAV) store
> using Cassandra. There is a column family, called Entity
Furthermore, dynamically altering the schema will prevent adding new node
to the cluster. I've faced a similar issue recently. While the new node is
joining the cluster, data are streamed from old to new node. If the
application alter the schema on the fly (DROP TABLE, DROP COLUMN ) the
data st
Hi guys, sorry about digging this up, but, is this bug also affecting 1.2.x
versions ? I can't see this being backported to 1.2 on the Jira. Was this
bug introduced in 2.0 ?
Anyway, how does nodetool repair -pr behave on a multi DC env, does it make
cross DC repairs or not ? Should we remove the "
Hello Takenori
Read Repair belongs to the Anti-Entropy procedures to ensure that
eventually, data from all replicas do converge. Tombstones are data
(deletion marker) so they need to be exchanged between replicas. By
skipping tombstone you prevent the data convergence with regard to
deletion.
On
Hi everyone,
We were working with Cassandra clusters in 2.0 version and now we want to work
with clusters in 2.1 version. We configure the Cassandra.yaml as we configured
it in the previous version, but at the moment of start the service there is a
fatal error. The log tells us that if you conf
Statically defining columsn using EAV table approach is totally a wrong fit
for Cassandra.
Taking a step back, EAV tables generally don't scale at no matter the
database. I've done this on SqlServer, Oracle and DB2. Many products that
use EAV approach like master data management products suffer fr
The bitmap updates will be daily.
I'll watch the video..
Regards
Eduardo
On Mon, Oct 6, 2014 at 6:04 PM, DuyHai Doan wrote:
> Yes this one, not Ooyala sorry. Very inventive usage of C* indeed. Thanks
> for the links
>
> On Mon, Oct 6, 2014 at 11:01 PM, Peter Sanford
> wrote:
>
>> On Mon,
This related issue might be of interest:
https://issues.apache.org/jira/browse/CASSANDRA-7450
In 1.2 "-pr" option does make cross DC repairs, but you must ensure that
all nodes from all datacenter execute repair, otherwise some ranges will be
missing. This fix enables -pr and -local together, whic
On Tue, Oct 7, 2014 at 1:57 AM, DuyHai Doan wrote:
> Read Repair belongs to the Anti-Entropy procedures to ensure that
> eventually, data from all replicas do converge. Tombstones are data
> (deletion marker) so they need to be exchanged between replicas. By
> skipping tombstone you prevent the
The broadcast_rpc_address should be an IP address that drivers/clients can
connect to. This is what will show up in the system.peers table under
"rpc_address". In most cases it should match the value of
broadcast_address (or listen_address, if broadcast_address isn't set).
On Tue, Oct 7, 2014 at
Also note that with an IN clause, if there is a failure fetching one of the
partitions, the entire request will fail and will need to be retried. If
you use concurrent async queries, you'll only need to retry one small
request.
On Mon, Oct 6, 2014 at 1:14 PM, DuyHai Doan wrote:
> "Definitely be
Hello,
I'm running Cassandra 1.2.16 with supercolumns and Hector.
create column family CFName
with column_type = 'Super'
and comparator = 'UTF8Type'
and subcomparator = 'UTF8Type'
and default_validation_class = 'UTF8Type'
and key_validation_class = 'UTF8Type'
and read_repair_cha
On Tue, Oct 7, 2014 at 1:38 PM, Owen Kim wrote:
> I'm running Cassandra 1.2.16 with supercolumns and Hector.
>
Slightly non-responsive response :
In general supercolumn use is not recommended. It makes it more difficult
to get support when one uses a feature no one else uses.
=Rob
I'm aware. I've had the system up since pre-composite columns and haven't
had the cycles to do a major data and schema migration.
And that's not "slightly" non-responsive.
On Tue, Oct 7, 2014 at 1:49 PM, Robert Coli wrote:
> On Tue, Oct 7, 2014 at 1:38 PM, Owen Kim wrote:
>
>> I'm running Cass
On Tue, Oct 7, 2014 at 2:03 PM, Owen Kim wrote:
> I'm aware. I've had the system up since pre-composite columns and haven't
> had the cycles to do a major data and schema migration.
>
> And that's not "slightly" non-responsive.
>
"There may be unknown bugs in the code you're using, especially be
Sigh, it is a bit grating. I (genuinely) appreciate your acknowledgement of
that. Though, I didn't intend for the question to be "about" supercolumns.
It is possible I'm hitting an odd edge case though I'm having trouble
reproducing the issue in a controlled environment since there seems to be a
t
DuyHi and Rob, Thanks for your feedbacks.
Yeah, that's exactly the point I found. Some may want to run read repair even
on tombstones as before, but others not like Rob and us.
Personally, I take read repaid as a nice to have feature, especially for
tombstones, where a regular repair is anyway
On Tue, Oct 7, 2014 at 3:11 PM, Owen Kim wrote:
> Sigh, it is a bit grating. I (genuinely) appreciate your acknowledgement
> of that. Though, I didn't intend for the question to be "about"
> supercolumns.
>
(Yep, understand tho that if you hadn't been told that advice before, it
would grate a lo
19 matches
Mail list logo
