Hey Aaron,
I went ahead and changed the model around to reduce the number of CF's from
around 60 or so to 7, but I'm still running into OOM messages and eventual node
crashes after I've pushed in about 30GB of data per node. And it seems that,
under load, once one node goes down, the other see
got it. Thanks for response.
On Thu, Aug 15, 2013 at 4:26 PM, Tyler Hobbs wrote:
> Snapshots just hardlink the existing SSTable files. They don't "freeze"
> the TTL or anything like that, so data can expire while snapshotted and it
> will be converted to a tombstone when it's first compacted
Snapshots just hardlink the existing SSTable files. They don't "freeze"
the TTL or anything like that, so data can expire while snapshotted and it
will be converted to a tombstone when it's first compacted after you reload
it. There's not an easy way to prevent this from happening.
On Thu, Aug
On Thu, Aug 15, 2013 at 11:02 AM, rash aroskar wrote:
> what do you mean by not adding as a seed? if I add new node to existing
> cluster, the new node should not be added as a seed in cassandra.yaml for
> other nodes in the ring?
> when should it be added as a seed then? once the cluster is balan
Hi,
If I add some data in cassandra cluster with TTL lets say 2 days, took
snapshot of it before it expires. If I use the snapshot to load the data in
different/same cluster, will the data from the snapshot will carry the TTL
of 2 days (from the time when the snapshot was created)? if not can I
spe
On Thu, Aug 15, 2013 at 6:58 AM, Janne Jalkanen wrote:
>
> Also, if you are using leveled compaction, remember that each SSTable will
> take a couple of MB of heap space. You can tune this by choosing a good
> sstable_size_in_mb value for those CFs which are on LCS and contain lots of
> data. De
what do you mean by not adding as a seed? if I add new node to existing
cluster, the new node should not be added as a seed in cassandra.yaml for
other nodes in the ring?
when should it be added as a seed then? once the cluster is balanced? or
after manually running rebuild command?
On Wed, Aug
The column_validation_classes arg is just for defining individual column
types. Glad you got it figured out, though.
On Thu, Aug 15, 2013 at 11:23 AM, Pinak Pani <
nishant.has.a.quest...@gmail.com> wrote:
> Thanks for quick reply. Apparantly, I was trying this to get working
>
> cf_kwargs = {'d
Thanks for quick reply. Apparantly, I was trying this to get working
cf_kwargs = {'default_validation_class':COUNTER_COLUMN_TYPE}
sys.create_column_family('my_ks', 'vote_count',
column_validation_classes=cf_kwargs) #1
But this works:
sys.create_column_family('my_ks', 'vote_count', **cf_kwargs)
The only thing that makes a CF a counter CF is that the default validation
class is CounterColumnType, which you can set through
SystemManager.create_column_family().
On Thu, Aug 15, 2013 at 10:38 AM, Pinak Pani <
nishant.has.a.quest...@gmail.com> wrote:
> I do not find a way to create a counter
I do not find a way to create a counter column family in Pycassa.
This[1] does not help.
Appreciate if someone can help me.
Thanks
1.
http://pycassa.github.io/pycassa/api/pycassa/system_manager.html#pycassa.system_manager.SystemManager.create_column_family
Also, if you are using leveled compaction, remember that each SSTable will take
a couple of MB of heap space. You can tune this by choosing a good
sstable_size_in_mb value for those CFs which are on LCS and contain lots of
data. Default is 5 MB, which is for many cases inadequate, so most peo
12 matches
Mail list logo
