Great post, Jonathan! Thank you very much.
~Eric
On Wed, Aug 8, 2018 at 2:34 PM Jonathan Haddad wrote:
> Hey folks,
>
> We've noticed a lot over the years that people create tables usually
> leaving the default compression parameters, and have spent a lot of time
> helping teams figure out the
Jon,
Great article. Thank you. (I have nothing to do with this issue, but I
appreciate nuggets of information I glean from the list)
Regards,
Eric
On Tue, Apr 17, 2018 at 10:57 PM Jonathan Haddad wrote:
> To add to what Nate suggested, we have an entire blog post on scaling time
> series data
hen other questions followed as a result. If you
want to contribute to the community, please start by being respectful to
all members of the community.
Regards,
Eric Plowe
On Mon, Feb 26, 2018 at 12:35 PM Kenneth Brotman
wrote:
> I got caught in the middle of this stuff. I feel for every
Cassandra, hard to use? I disagree completely. With that said, there are
definitely deficiencies in certain parts of the documentation, but nothing
that is a show stopper. We’ve been using Cassandra since the sub 1.0 days
and have had nothing but great things to say about it.
With that said, its a
The driver had load balancing policies built in. Behind a load balancer
you'd lose the benefit things like the TokenAwarePolicy.
On Mon, Jun 19, 2017 at 3:49 PM Jonathan Haddad wrote:
> The driver grabs all the cluster information from the nodes you provide
> the driver and connects automatically
astax.com/en/cassandra/2.1/cassandra/architecture/architectureSnitchDynamic_c.html
Regards,
Eric Plowe
On Wed, Mar 22, 2017 at 12:21 PM Shannon Carey wrote:
I understand all that, but it doesn't explain why the latency increases.
The requests are not going to a remote DC. I know this becaus
ONE means at least one replica node to ack the write, but doesn't require
that the coordinator route the request to a node in the local data center.
LOCAL_ONE was introduced to handle the case of when you have multiple data
centers and cross data center traffic is not desirable.
In multiple datac
cluster is
down.
On Monday, February 1, 2016, Jeff Jirsa wrote:
> Yes, but getting at why you think EBS is going down is the real point. New
> GM in 2011. Very different product. 35:40 in the video
>
>
> --
> Jeff Jirsa
>
>
> On Jan 31, 2016, at 9:57 PM, Eric Plowe > w
ussion by Dennis Opacki). 2016 EBS isn't the
> same as 2011 EBS.
>
> --
> Jeff Jirsa
>
>
> On Jan 31, 2016, at 8:27 PM, Eric Plowe > wrote:
>
> Thank you all for the suggestions. I'm torn between GP2 vs Ephemeral. GP2
> after testing is a viable contender for
Fri, Jan 29, 2016 at 7:32 PM, Jeff Jirsa >> > wrote:
>>>
>>>> If you have to ask that question, I strongly recommend m4 or c4
>>>> instances with GP2 EBS. When you don’t care about replacing a node because
>>>> of an instance failure, go with i2+ep
RAID 0 regardless of instance type*
On Friday, January 29, 2016, Eric Plowe wrote:
> Bryan,
>
> Correct, I should have clarified that. I'm evaluating instance types based
> on one SSD or two in RAID 0. I thinking its going to be two in RAID 0,
> but as I've ha
ferent instance types based on one disk vs two?
>
> On Fri, Jan 29, 2016 at 4:33 PM, Eric Plowe > wrote:
>
>> My company is planning on rolling out a C* cluster in EC2. We are
>> thinking about going with ephemeral SSDs. The question is this: Should we
>> put two in RA
My company is planning on rolling out a C* cluster in EC2. We are thinking
about going with ephemeral SSDs. The question is this: Should we put two in
RAID 0 or just go with one? We currently run a cluster in our data center
with 2 250gig Samsung 850 EVO's in RAID 0 and we are happy with the
perfor
Lijun,
That is correct. If you have an investment in Astyanax , you'll need to
stay in the 2.0 series. You'll either need to wait until Astyanax is
updated to support 2.1 (if that is going to happen) or migrate to the
datastax java driver.
~Eric
On Wed, Nov 18, 2015 at 12:04 AM, Lijun Huang wro
Ah. My bad for not checking the jira first.
Thanks!
On Friday, October 2, 2015, Robert Coli wrote:
> On Thu, Oct 1, 2015 at 1:07 PM, Eric Plowe > wrote:
>
>> I am using C* 2.1.9 and GossipingPropertyFileSnitch. I noticed that when
>> I run nodetool info I am seeing the da
getting:
Data Center: UNKNOWN_DC
Rack : UNKNOWN_RACK
nodetool status and opscenter still report correctly.
Is this just a bug with nodetool?
Regards,
Eric Plowe
I'am here! Beaded guy, in a blue gingham shirt. I'll be at the reception.
On Tue, Sep 22, 2015 at 2:59 PM, Jonathan Haddad wrote:
> Yo. It's me. Haddad, aka rustyrazorblade. 6'1", hair probably in a bun
> and a beard. Helping with training today, giving a talk on pyspark & on
> the python
I noticed in the system.log of one of my nodes
INFO [HANDSHAKE-mia1-cas-001.bongojuice.com/172.16.245.1] 2015-09-10
16:00:37,748 OutboundTcpConnection.java:485 - Handshaking version with
mia1-cas-001.bongojuice.com/172.16.245.1
The machine I am on is mia1-cas-001.
If it's nothing, never mind, j
re definitive :)
>
> On Wed, Sep 9, 2015 at 12:11 PM, Eric Plowe > wrote:
>
>> Yeah, that's what I did. Just wanted to verify it that will indeed turn
>> it off.
>>
>> On Wednesday, September 9, 2015, Laing, Michael <
>> michael.la...
gt;
> On Wed, Sep 9, 2015 at 10:11 AM, Eric Plowe > wrote:
>
>> Would this work:
>>
>> ALTER TABLE session_state WITH speculative_retry = '0ms';
>> ALTER TABLE session_state WITH speculative_retry = '0PERCENTILE';
>>
>> I can't set
Would this work:
ALTER TABLE session_state WITH speculative_retry = '0ms';
ALTER TABLE session_state WITH speculative_retry = '0PERCENTILE';
I can't set it to 0, but was wondering if these would have the same effect?
~Eric
On Wed, Sep 9, 2015 at 8:19 AM, Eric Plowe wr
id cross-dc reads.
>
> On Wed, Sep 9, 2015 at 7:55 AM, Eric Plowe > wrote:
>
>> read_repair_chance: 0
>> dclocal_read_repair_chance: 0.1
>>
>>
>> On Wednesday, September 9, 2015, Laing, Michael <
>> michael.la...@nytimes.com
>> > wrote:
>
read_repair_chance: 0
dclocal_read_repair_chance: 0.1
On Wednesday, September 9, 2015, Laing, Michael
wrote:
> What are your read repair settings?
>
> On Tue, Sep 8, 2015 at 9:28 PM, Eric Plowe > wrote:
>
>> To further expand. We have two data centers, Miami and Dal
writing and reading to the Miami cluster with LOCAL_QUORUM.
Regards,
Eric
On Tuesday, September 8, 2015, Eric Plowe wrote:
> Rob,
>
> All writes/reads are happening from DC1. DC2 is a backup. The web app does
> not handle live requests from DC2.
>
> Regards,
>
> Eric Plowe
&
Rob,
All writes/reads are happening from DC1. DC2 is a backup. The web app does
not handle live requests from DC2.
Regards,
Eric Plowe
On Tuesday, September 8, 2015, Robert Coli wrote:
> On Tue, Sep 8, 2015 at 4:40 PM, Eric Plowe > wrote:
>
>> I'm using Cassandra as a s
ver v2.1.6.
Writes and reads are at LOCAL_QUORUM.
The cluster and web servers have their time synced and we've ruled out
clock drift issues.
The issue doesn't happen all the time, maybe two to three times a day.
Any insight as to what to look at next? Thanks!
~Eric Plowe
I think reading the relevant documentation might have helped.
http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html
On Fri, Aug 7, 2015 at 9:04 AM, horschi wrote:
> Hi Cyril,
>
> thanks for backing me up. I'm under siege from all sides here ;-)
>
>
> That
Are you sure that both DC's can communicate with each other over the
necessary ports?
On Thu, Nov 13, 2014 at 3:46 PM, Adil wrote:
> yeh we started nodes one at timemy doubt is if we should configure
> alse cassandra-topology.properties or not? we leave it with default vlaues
>
> 2014-11-13
I am a big fan of perl-ssh-tools (https://github.com/tobert/perl-ssh-tools)
to let me manage my nodes and SVN to store configs.
~Eric Plowe
On Thu, Oct 23, 2014 at 3:07 PM, Michael Shuler
wrote:
> On 10/23/2014 04:18 AM, Alain RODRIGUEZ wrote:
>
>> I was wondering about how do you
> On Mon, Sep 15, 2014 at 4:57 PM, Eric Plowe > wrote:
>
>> Based on this stackoverflow question, vnodes effect the number of mappers
>> Hadoop needs to spawn. Which in then affect performance.
>>
>> With the spark connector for cassandra would the same si
As hadoop* again sorry..
On Monday, September 15, 2014, Eric Plowe wrote:
> Sorry. Trigger finger on the send.
>
> Would vnodes affect performance for spark in a similar fashion for spark.
>
> On Monday, September 15, 2014, Eric Plowe > wrote:
>
>> Hello.
>&g
Sorry. Trigger finger on the send.
Would vnodes affect performance for spark in a similar fashion for spark.
On Monday, September 15, 2014, Eric Plowe wrote:
> Hello.
>
>
> http://stackoverflow.com/questions/19969329/why-not-enable-virtual-node-in-an-hadoop-node/19974621#19974621
Hello.
http://stackoverflow.com/questions/19969329/why-not-enable-virtual-node-in-an-hadoop-node/19974621#19974621
Based on this stackoverflow question, vnodes effect the number of mappers
Hadoop needs to spawn. Which in then affect performance.
With the spark connector for cassandra would the s
Michael,
The ask is for letting keep alive be configurable for native transport,
with Socket.setKeepAlive. By default, SO_KEEPALIVE is false (
http://docs.oracle.com/javase/7/docs/api/java/net/StandardSocketOptions.html#SO_KEEPALIVE).
Regards,
Eric Plowe
On Wed, Apr 9, 2014 at 1:25 PM
27, 2014 at 10:57 AM, Eric Plowe wrote:
>>
>>> i have a cluster that is running 1.2.6. I'd like to upgrade that cluster
>>> to 2.0.7
>>>
>>> Any suggestions/tips that would make the upgrade process smooth?
>>>
>>
>> As indic
i have a cluster that is running 1.2.6. I'd like to upgrade that cluster to
2.0.7
Any suggestions/tips that would make the upgrade process smooth?
,
> so will be available in future versions. See
> https://issues.apache.org/jira/browse/CASSANDRA-4511
>
> If your main concern is performance then you should find another way to
> model the data: each collection is read entirely into memory to access a
> single item.
>
>
>
Collection types cannot be used for filtering (as part of the where
statement).
They cannot be used as a primary key or part of a primary key.
Secondary indexes are not supported as well.
On Mon, May 19, 2014 at 12:50 PM, Raj Janakarajan
wrote:
> Hello all,
>
> I am using Cassandra version 2.0.7
Also I don't think you can null out columns that are part of the primary
key after they've been set.
On Monday, April 21, 2014, Andreas Wagner <
andreas.josef.wag...@googlemail.com> wrote:
> Hi cassandra users, hi Sebastian,
>
> I'd be interested in this ... is there any update/solution?
>
> Than
Setting the columns to null is essentially deleting them from my
understanding. A delete operation works on the entire row.
On Monday, April 21, 2014, Andreas Wagner <
andreas.josef.wag...@googlemail.com> wrote:
> Hi cassandra users, hi Sebastian,
>
> I'd be interested in this ... is there any up
a.yaml and restart cassandra
then run the same test I outlined above using thrift the connection will
stay, like the native transport connections, until cassandra, or the box,
is restarted.
It seems the lack of keep alive support for native transport is the culprit.
Regards,
Eric Plowe
On F
I am having the exact same issue. I see the connections pile up and pile
up, but they never seem to come down. Any insight into this would be
amazing.
Eric Plowe
On Wed, Apr 9, 2014 at 4:17 PM, graham sanderson wrote:
> Thanks Michael,
>
> Yup keepalive is not the default. It is
You should be able to achieve what you're looking for with a trigger vs. a
modification to the core of Cassandra.
http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-0-prototype-triggers-support
On Mon, Mar 10, 2014 at 10:06 AM, DE VITO Dominique <
dominique.dev...@thalesgroup.com> wrote
Disregard... heh. Was reading the latency as SECONDS. Sorry, it's been one
of those weeks.
On Wed, Mar 5, 2014 at 1:44 AM, Eric Plowe wrote:
> Background info:
>
> 6 node cluster.
> 24 gigs of ram per machine
> 8 gigs of ram dedicated to c*
> 4 4 core cpu's
> 2 2
de "WHERE uid
= ''" for the queries.
If there is any more info I can provide, please let me know. At this point
in time, I am a bit stumped.
Regards,
Eric Plowe
45 matches
Mail list logo
