Do you mean Priam nitan?
> On 16 Jun 2017, at 16:48, Nitan Kainth wrote:
>
> you can try atlas from netflix, it is open source.
>
>> On Jun 16, 2017, at 8:52 AM, Surbhi Gupta wrote:
>>
>> If u are using dse then u can use opscenter
>>
>> On Fri, Jun 16, 2017 at 6:01 AM Ram Bhatia wrote:
>
Agree, I meant as Jonathan said to use C* for primary key and as a primary
storage and ES as an indexed version of what you have in cassandra.
2017-06-12 19:19 GMT+02:00 DuyHai Doan :
> Sorry, I misread some reply I had the impression that people recommend ES
> as primary datastore
>
> On Mon, Ju
Cassandra.
> In that case I have to create distributed tables such as:-
> 1) video_by_title, video_by_actor, video_by_year etc..
> 2) After creating Tables , will have to configure solr core on all tables.
>
> Is it like this ?
>
>
>
>
>
>> On Mon, Jun
Why not elasticsearch for this use case? It will make your life much simpler
> On 12 Jun 2017, at 04:40, @Nandan@ wrote:
>
> Hi,
>
> Currently, I am working on data modeling for Video Company in which we have
> different types of users as well as different user functionality.
> But currentl
You could put the tenant as a column that is part of the clustering key. That
avoids large partitions.
On 12 Jun 2017, at 07:14, Erick Ramirez wrote:
>> Given my use case is cassandra the best suited one or is there any other
>> database which suits my requirement better?
>
> Probably not th
If you're on AWS you can use Netflix Priam
> On 17 May 2017, at 18:40, Abhishek Gupta wrote:
>
> Hi Zaidi,
>
> We use Chef for the configuration management of our 14 node cluster.
>
> You can have a look at Chef or maybe some other config management tools too
> like Ansible and Puppet.
>
>
>> X repair processes (that will each trigger a Markel tree building on each
>> node). But I would assume that Cassandra prevents this by making sure that
>> there is only one repair process running per node.
>>
>>
>>
>>> On Fri, Apr 21, 2017 at 2:43 AM
If I have a table like this:
PRIMARY KEY ((userid),deviceid)
And I query
SELECT * FROM devices where userid= ? and deviceid = ?
Will cassandra read the entire partition for the userid? So if I lots of
tombstones for userid, will they get scanned?
I guess this depends on how the bloomfilter is w
It will create more overhead on your cluster. Consider using something like
reaper to manage.
> On 21 Apr 2017, at 00:57, eugene miretsky wrote:
>
> In Cassandra 3.0 the default nodetool repair behaviour is incremental and
> parallel.
> Is there a downside to triggering repair from multiple
You changed to 6 nodes because you were running out of disk? But you still
replicate 100% to all so you don't gain anything
> On 10 Apr 2017, at 13:48, Cogumelos Maravilha
> wrote:
>
> No.
>
> nodetool status, nodetool describecluster also nodetool ring shows a correct
> cluster.
>
> Not
It's not that easy as I recall this email thread
https://groups.google.com/forum/m/#!topic/nosql-databases/ZLdgwCT_PNU
/Oskar
> On 30 Sep 2016, at 18:40, Carlos Alonso wrote:
>
> Cassandra is a Wide Column Store http://db-engines.com/en/system/Cassandra
>
> Carlos Alonso | Software Engineer
How about this tool?
https://github.com/instaclustr/cassandra-sstable-tools
> On 13 Mar 2017, at 17:56, Artur R wrote:
>
> Hello!
>
> I can't find where C* stores information about partitions size (if stores it
> at all).
> So, the questions;
>
> 1. How to obtain the size (in rows or in byt
Throttle your compaction so low that it practically stops and then try so save
the nodes to simulate not keeping up with compaction
Sent from my iPhone
> On 1 Mar 2017, at 14:35, Stefan Podkowinski wrote:
>
> I've just created a page for this topic that we can use to collect some
> content:
>
Are you running multi dc?
Skickat från min iPad
> 27 feb. 2017 kl. 16:08 skrev Thakrar, Jayesh :
>
> Suppose I have an application, where there are no deletes, only 5-10% of rows
> being occasionally updated (and that too only once) and a lot of reads.
>
> Furthermore, I have replication = 3
We currently have some cases where we store base64 as a text field instead
of a blob (running version 2.0.17).
I would like to move these to blob but wondering what benefits and
optimizations there are? The possible ones I can think of is (but there's
probably more):
* blob is stored as off heap B
(LOCAL_ONE I think). Should I try repairing all nodes to make
> sure all data is consistent?
>
> -JE
>
>
>> On Tue, Feb 14, 2017 at 1:32 PM, Oskar Kjellin
>> wrote:
>> What consistency levels are you using for reads/writes?
>>
>> Sent from my iPho
What consistency levels are you using for reads/writes?
Sent from my iPhone
> On 14 Feb 2017, at 22:27, Josh England wrote:
>
> I'm running Cassandra 3.9 on CentOS 6.7 in a 6-node cluster. I've got a
> situation where the same query sometimes returns 2 records (correct), and
> sometimes only
There is no harm in running it tho. If it's not needed it will simply
terminate. Better to be safe
Sent from my iPhone
> On 9 Jan 2017, at 08:13, Amit Singh F wrote:
>
> Hi ,
>
> Generally Upgradesstables are only recommended when you plan to move with
> Major version like from 2.0 to 2.1
(key3 in the second example)?
>
>> On Tue, Dec 27, 2016 at 10:06 AM, Oskar Kjellin
>> wrote:
>> The second one will be the most efficient.
>> How much depends on how unique key1 is.
>>
>> In the first case everything for the same key1 will be on the same
The second one will be the most efficient.
How much depends on how unique key1 is.
In the first case everything for the same key1 will be on the same partition.
If it's not unique at all that will be very bad.
In the second case the combo of key1 and key2 will decide what partition.
If you
The actual video is not stored in Cassandra. You need to use a proper origin
like s3.
Although you can probably store it in Cassandra, it's not a good idea.
Sent from my iPhone
> On 14 nov. 2016, at 18:02, raghavendra vutti
> wrote:
>
> Hi,
>
> Just wanted to know How does hulu or netfli
Could you not send both labels in one request? Race conditions should still be
handled as Vladimir suggests. But in this specific case the client could send
both as 1 request thus simplifying the solution.
/Oskar
> On 12 nov. 2016, at 12:05, Vladimir Yudovin wrote:
>
> Hi Ali,
>
> >What can
Hi,
You could manually trigger it with nodetool compact.
/Oskar
> On 8 nov. 2016, at 21:47, Lahiru Gamathige wrote:
>
> Hi Users,
>
> I am thinking of migrating our timeseries tables to use TWCS. I am using JMX
> to set the new compaction and one node at a time and I am not sure how to
>
gt; pod for $25 per month in the same DC.
>
> We provide Cassandra cluster on all provider in many worldwide locations.
>
> Best regards, Vladimir Yudovin,
>
> *Winguzone <https://winguzone.com?from=list> - Hosted Cloud
> CassandraLaunch your cluster in minutes.*
>
&
my iPhone
> On 4 nov. 2016, at 10:10, Oskar Kjellin wrote:
>
> So I've run Cassandra on both Aws and azure. I would strongly suggest that if
> you have the option, run as far away from azure as you can.
>
> Here's a list of issues I have running Cassandra on azure:
So I've run Cassandra on both Aws and azure. I would strongly suggest that if
you have the option, run as far away from azure as you can.
Here's a list of issues I have running Cassandra on azure:
1. No native snitch
2. No concept of availability zones. This makes it impossible for Cassandra to
Hi,
Ran into the same issue when going to 3.5. Completely killed our cluster. Only
way was to restore a backup.
/Oskar
> On 2 aug. 2016, at 07:54, Julien Anguenot wrote:
>
> Hey Jesse,
>
> You might wanna check and comment against that issue:
>
> https://issues.apache.org/jira/browse/CAS
Hi,
If I were you I would stick on 3.0.x. I haven't experienced 3.x to be
production ready. We went to prod with 3.5 and I wish we hadn't.
/Oskar
> On 23 juni 2016, at 10:56, Bienek, Marcin wrote:
>
> Hi,
>
> We are short before going in prod with our cassandra cluster. Now I wonder if
>
.
>
> AFAIK, there is no evidence that UDTs are responsible of this bad behavior.
>
>> On Tue, Jun 21, 2016 at 11:45 AM, Oskar Kjellin
>> wrote:
>> Yea I saw that one. We're not using UDT in the affected tables tho.
>>
>> Did you resolve it?
>
this bad behavior.
>
>> On Tue, Jun 21, 2016 at 11:45 AM, Oskar Kjellin
>> wrote:
>> Yea I saw that one. We're not using UDT in the affected tables tho.
>>
>> Did you resolve it?
>>
>> Sent from my iPhone
>>
>>> On 21 juni 2016, at 1
o 3.0.x.
>
> See comments on the Jira issue I opened at the time over there:
> https://issues.apache.org/jira/browse/CASSANDRA-11887
>
>
>> On Tue, Jun 21, 2016 at 10:47 AM, Oskar Kjellin
>> wrote:
>> Hi,
>>
>> We've done this upgrade in both
Hi,
We've done this upgrade in both dev and stage before and we did not see
similar issues.
After upgrading production today we have a lot issues tho.
The main issue is that the Datastax client quite often does not get the
data (even though it's the same query). I see similar flakyness by simply
32 matches
Mail list logo
