was a conference for Cassandra, hosted by DataStax.
Throughout Jonathan's keynote, he was addressing Apache Cassandra, not
DataStax Enterprise.
Hope that helps clear the muddy waters!
[image: DataStaxLogo copy3.png] <http://www.datastax.com/>
PHIL BAYLISS
Solutions Engineer | 512.95
Running Cassandra 2.2.1 on 3 nodes (on EC2, from Datastax AMI, then
upgraded). Inserting time-series data; All entries with TTL to expire
3 hours after the "actual_time" of the observation. Entries arrive
with varied delay, and often in duplicate. Data is expiring (no longer
visible from CQL),
Jeff Jirsa wrote:
> 2.2.1 has a pretty significant bug in compaction:
> https://issues.apache.org/jira/browse/CASSANDRA-10270
>
> That prevents it from compacting files after 60 minutes. It may or
> may not be the cause of the problem you're seeing, but it seems like
> it may be possibly related,
that the new counter implementations are
safer although I'm not sure what that means in practice. Will the
counters be 99.99% accurate? How often will they be over or under counted?
Thanks, Mike.
--
Thanks,
Phil Yang
as
our_table-147a2090ed4211e480153bc81e542ebd/
instead of as
our_table/
Why would that happen? We're also seeing lagging compactions and high
cpu usage.
Thanks, Don
--
Thanks,
Phil Yang
find that there are a
lot of patches in 2.1.5. Is it ready for upgrade?
I personally would not run either version in production at this time,
but if forced, would prefer 2.1.5 over 2.1.2.
=Rob
--
Cheers,
Brian
http://www.integrallis.com
--
Thanks,
Phil Yang
--
Thanks,
Phil Yang
, Phil Yang ud1...@gmail.com wrote:
you can use nodetool rebuild in this node.
2015-03-25 9:20 GMT+08:00 Flavien Charlon flavien.char...@gmail.com:
Hi,
What is the process to re-bootstrap a node after hard drive failure
(Cassandra 2.1.3)?
This is the same node as previously, but the data
like to re-bootstrap it from the data stored on the other nodes
of the cluster (I have RF=3).
I am not using vnodes.
Thanks
Flavien
--
Thanks,
Phil Yang
column or modifying any table properties?
Thanks
Ajay
--
Thanks,
Phil Yang
indexes.
See CASSANDRA-8798
~mck
--
-
Nate McCall
Austin, TX
@zznate
Co-Founder Sr. Technical Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com
--
Thanks,
Phil Yang
release more frequently? Or we may make a rule to decide if we
need release a new version? For example: If the latest version was
released two weeks ago, or after the latest version we have already
resolved 20 issues, we should release a new minor version.
--
Thanks,
Phil Yang
tickets.
=Rob
On Mon, Dec 29, 2014 at 1:40 PM, Robert Coli rc...@eventbrite.com wrote:
On Wed, Dec 24, 2014 at 9:41 AM, Phil Burress philtburr...@gmail.com
wrote:
Just upgraded our cluster from 2.1.1 to 2.1.2 and our nodes keep dying.
The kernel is killing the process due to out of memory
：18600360358
地址：北京市大兴区 朝林广场25层
邮编：100101
=
网购上京东，省钱又放心！
www.jd.com
*发件人:* Phil Burress [mailto:philtburr...@gmail.com]
*发送时间:* 2014年12月31日 2:53
*收件人:* user@cassandra.apache.org
*主题:* Re: Downgrade from 2.1.2 to 2.1.1
Thanks Rob.
On Tue
Thanks Rob.
On Tue, Dec 30, 2014 at 1:38 PM, Robert Coli rc...@eventbrite.com wrote:
On Tue, Dec 30, 2014 at 9:42 AM, Phil Burress philtburr...@gmail.com
wrote:
We are having a lot of problems with release 2.1.2. It was suggested here
we should downgrade to 2.1.1 if possible
--
Thanks,
Phil Yang
sorry for typo.. timestamp which Cassandra uses is independent on the
timezone.
Usually, it is recommended to use NTP to reduce the difference of
timestamps in each nodes
2014-12-27 21:20 GMT+08:00 Phil Yang ud1...@gmail.com:
In java,
http://docs.oracle.com/javase/7/docs/api/java/lang
but nothing has worked thus far. We did not have this issue until
we upgraded. Anyone else run into this or have suggestions?
Thanks!
Phil
I've added these as answers to a question I posted on Stack Overflow:
http://stackoverflow.com/questions/26460932/how-to-deploy-changes-to-a-cassandra-cql-schema/27013426
Thank you
Phil
On 05.12.2014 15:23, Brian Sam-Bodden wrote:
There is also https://github.com/hsgubert/cassandra_migrations
-datasets
https://issues.apache.org/jira/browse/CASSANDRA-6654
Thank you
Phil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The session will be written once at create time, and never modified
after that. Will that affect things?
Thank you
- -Phil
On 01.12.2014 15:58, Jonathan Haddad wrote:
I don't think DateTiered will help here, since there's no
clustering key
need a hand getting going with it.
Cheers,
Phil
Is there any mention of this limitation anywhere in the Cassandra
documentation? I don't see it mentioned in the 'Anti-patterns in Cassandra'
section of the DataStax 2.0 documentation or anywhere else.
When starting out with Cassandra as a store for a multi-tenant application
it seems very
but perhaps that's the price we have to pay to scale.
And I still think this needs to be made more prominent in the documentation.
Thanks
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Reasonable-range-for-the-max-number-of-tables
Ken Hancock wrote
You didn't post any timings, only when it started failing so it's unclear
whether performance is dropping off or scaling in some sort of linear or
non-linear fashion. Second the recommendation to do some traces which
should be much more telling.
I'm afraid I've not yet had
://github.com/hancockks/cassandra_range_repair
On Mon, Jun 30, 2014 at 10:20 PM, Phil Burress philburress...@gmail.com
wrote:
@Paulo, this is very cool! Thanks very much for the link!
On Mon, Jun 30, 2014 at 9:37 PM, Paulo Ricardo Motta Gomes
paulo.mo...@chaordicsystems.com wrote:
If you
to be an option in the version we have. We are running 2.0.7 with vnodes.
Any insight into what might be causing these OOMs and/or what version this
-snapshot option is available in?
Thanks!
Phil
We are running repair -pr. We've tried subrange manually and that seems to
work ok. I guess we'll go with that going forward. Thanks for all the info!
On Mon, Jun 30, 2014 at 6:52 PM, Jaydeep Chovatia
chovatia.jayd...@gmail.com wrote:
Are you running full repair or on subset? If you are
One last question. Any tips on scripting a subrange repair?
On Mon, Jun 30, 2014 at 7:12 PM, Phil Burress philburress...@gmail.com
wrote:
We are running repair -pr. We've tried subrange manually and that seems to
work ok. I guess we'll go with that going forward. Thanks for all the info
:26 PM, Phil Burress philburress...@gmail.com
wrote:
One last question. Any tips on scripting a subrange repair?
On Mon, Jun 30, 2014 at 7:12 PM, Phil Burress philburress...@gmail.com
wrote:
We are running repair -pr. We've tried subrange manually and that seems
to work ok. I guess we'll go
the original 2 that worked
previously have not changed.
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RPC-timeout-paging-secondary-index-query-results-tp7595078p7595126.html
Sent from the cassandra-u...@incubator.apache.org mailing list
The problem appears to be directly related to number of entries in the index.
I started with an empty table and added 50,000 entries at a time with the
same indexed value. I was able to page through the results of a query that
used the secondary index with 250,000 records in the table using a
work.
Thanks
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RPC-timeout-paging-secondary-index-query-results-tp7595078.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
must be doing
something wrong for it to appear to be this broken.
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RPC-timeout-paging-secondary-index-query-results-tp7595078p7595092.html
Sent from the cassandra-u...@incubator.apache.org
everything pushes you
toward using vnodes. It's not until you start reading in forums such as
this, blog posts, and JIRA issues that it becomes clear that they do come
with caveats.
I'll look forward to the 'always-specify-initial_token best practice' post.
Thanks,
Phil
--
View this message
Definitely no TTL and records are only written once with no deletions.
Phil
DuyHai Doan wrote
Are you sure there is no TTL set on your data? It might explain the shrink
in sstable size after compaction.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146
that there is no
automatic method for this but is it possible to do this manually and if so
what are the steps required? Do we need to add new nodes with the number of
vnodes we require and then decommission the existing ones or is it possible
to do it just with our existing 3 nodes?
Thanks
Phil
--
View
file.
For a small cluster, e.g. 9 nodes with RF=3 would you actually recommend
using vnodes at all and if so how many?
Phil
Robert Coli-3 wrote
On Thu, May 22, 2014 at 4:31 AM, Phil Luckhurst
phil.luckhurst@
wrote:
We have a 3 node 2.0.7 cluster with RF=3. At the moment
Hi Andreas,
So does that mean it can compact the 'hottest' partitions into a new sstable
but the old sstables may not immediately be removed so the same data could
be in more that one sstable? That would certainly explain the difference we
see when we manually run nodetool compact.
Thanks
Phil
I'm wondering if the lack of response to this means it was a dumb question
however I've searched the documentation again but I still can't find an
answer :-(
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Can-SSTables-overlap
.
Using this we simply multiplied by the number of identifiers, in this case
700, to get the 7GB estimate.
And as noted above this estimate is correct once the data is compacted to
one sstable but is wrong when there are multiple sstables.
Phil
Andreas Finke wrote
Hi Phil,
there is no dump
reduced it to a single sstable
that does match our 7GB estimate.
I'd like to understand what accounts for the other 4GB when it was stored as
multiple sstables? Is it because the individual sstables overlap?
Thanks
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org
) with
cassandra 2.0.7. Any suggestions on how to debug these errors?
Is there a recommendation to move to Placement Groups for Cassandra?
Thanks!
Phil
Hobbs ty...@datastax.com wrote:
On Fri, Apr 25, 2014 at 10:43 AM, Phil Burress
philburress...@gmail.comwrote:
Thanks. I made a change to a single node and it took almost an hour to
rejoin the cluster (go from DN to UP in nodetool status). The cluster is
pretty much idle right now and has
If I wanted to make a configuration change to a single node in a cluster,
what is the recommended approach for doing that? Is it ok to just stop that
instance, make the change and then restart it?
Just a follow-up on this for any interested parties. Ultimately we've
determined that the bootstrap/join process is broken in Cassandra. We ended
up creating an entirely new cluster and migrating the data.
On Mon, Apr 21, 2014 at 10:32 AM, Phil Burress philburress...@gmail.comwrote:
The new
Cassandra 2.0.6
On Fri, Apr 25, 2014 at 10:31 AM, James Rothering jrother...@codojo.mewrote:
What version of C* is this?
On Fri, Apr 25, 2014 at 6:55 AM, Phil Burress philburress...@gmail.comwrote:
Just a follow-up on this for any interested parties. Ultimately we've
determined
:
Yes.
Some changes you can manually have take affect without a restart (ie
compactionthroughput, things settable from jmx). There is also config
changes you cant really make like switching the snitch and such without a
big todo.
---
Chris
On Apr 25, 2014, at 8:53 AM, Phil Burress
The new node has managed to stay up without dying for about 24 hours now...
but it still is in JOINING state. A new concern has popped up. Disk usage
is at 500GB on the new node. The three original nodes have about 40GB each.
Any ideas why this is happening?
On Sat, Apr 19, 2014 at 9:19 PM, Phil
On Fri, Apr 18, 2014 at 1:43 PM, Phil Burress philburress...@gmail.comwrote:
First, I just stopped 2 of the nodes and left one running. But this
morning, I stopped that third node, cleared out the data, restarted and let
it rejoin again. It appears streaming is done (according to netstats
PM, Robert Coli rc...@eventbrite.com wrote:
On Wed, Apr 16, 2014 at 1:56 PM, Phil Burress philburress...@gmail.comwrote:
I've shut down two of the nodes and am bootstrapping one right now. Is
there any way to tell when it will finish bootstrapping?
nodetool netstats will show the progress
(according to compactionstats). Just sit and wait I guess?
On Fri, Apr 18, 2014 at 2:23 PM, Steven A Robenalt srobe...@stanford.eduwrote:
Looking back through this email chain, it looks like Phil said he wasn't
using vnodes.
For the record, we are using vnodes since we brought up our first cluster
to finish?
Running Cassandra version 2.0.6. on Ubuntu 12.04.
Thanks very much!
Phil
Thanks very much for the response. I'm not using vnodes, does that matter?
On Wed, Apr 16, 2014 at 2:13 PM, Robert Coli rc...@eventbrite.com wrote:
On Wed, Apr 16, 2014 at 11:10 AM, Phil Burress
philburress...@gmail.comwrote:
How long does bootstrapping typically take? I have 3 existing
Also, one more quick question. For the new nodes, do I add all three
existing nodes as seeds? Or just add one?
On Wed, Apr 16, 2014 at 2:16 PM, Phil Burress philburress...@gmail.comwrote:
Thanks very much for the response. I'm not using vnodes, does that matter?
On Wed, Apr 16, 2014 at 2:13
Thanks!
On Wed, Apr 16, 2014 at 2:50 PM, Robert Coli rc...@eventbrite.com wrote:
On Wed, Apr 16, 2014 at 11:16 AM, Phil Burress
philburress...@gmail.comwrote:
Thanks very much for the response. I'm not using vnodes, does that
matter?
Not in your case. In some cases it is safe
I've shut down two of the nodes and am bootstrapping one right now. Is
there any way to tell when it will finish bootstrapping?
On Wed, Apr 16, 2014 at 2:56 PM, Phil Burress philburress...@gmail.comwrote:
Thanks!
On Wed, Apr 16, 2014 at 2:50 PM, Robert Coli rc...@eventbrite.com wrote
We are also seeing this in our development environment. We have a 3 node
Cassandra 2.0.5 cluster running on Ubuntu 12.04 and are connecting from a
Tomcat based application running on Windows using the 2.0.0 Cassandra Java
Driver. We have setKeepAlive(true) when building the cluster in the
it.
--
Thanks
Phil
Chris Lohfink wrote
TCP keep alives (by the setTimeout) are notoriously useless... The
default
2 hours is generally far longer then any timeout in NAT translation tables
(generally ~5 min) and even if you decrease the keep alive to a sane value
a log of networks actually throw away
not seen the gossip failures for the
last 24 hours.
--
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Gossip-intermittently-marks-node-as-DOWN-tp7593189p7593569.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive
The VMs are hosted on the same ESXi server and they are just running
Cassandra. We seem to get this happen even if the nodes appear to be idle;
about 2 to 4 times per hour.
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Gossip
It was created with the default settings so we have 256 per node.
Fabrice Facorat wrote
From what I understand, this can happen when having many nodes and
vnodes by node. How many vnodes did you configure on your nodes ?
2014-03-04 11:37 GMT+01:00 Phil Luckhurst lt;
phil.luckhurst@
gt
Here's the tpstats output from both nodes.
Johnny Miller wrote
What is nodetool tpstats telling you?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Gossip-intermittently-marks-node-as-DOWN-tp7593189p7593206.html
Sent from the
Gossiper.java (line
849) InetAddress /10.150.100.20 is now UP
INFO [HANDSHAKE-/10.150.100.20] 2014-02-28 08:14:09,613
OutboundTcpConnection.java (line 386) Handshaking version with
/10.150.100.20
Has anyone got any suggestions for fixing this?
Thanks
Phil
--
View this message in context
|
{1: 2, 2: 1}
Is this a known issue or something wrong on our system?
Thanks
Phil
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Invalid-compacted-at-timestamp-entries-in-Cassandra-2-0-5-tp7593190.html
Sent from the cassandra-u
Thanks.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Invalid-compacted-at-timestamp-entries-in-Cassandra-2-0-5-tp7593190p7593192.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Sent from my iPhone
My experience is that timestamps have to be sequentially increasing for
writes to work. Soft/silent error if you do not follow this protocol.
Haven't tested against 0.6.4 though.
On Tue, Sep 21, 2010 at 8:29 AM, Lucas Nodine lucasnod...@gmail.com wrote:
Chris, I believe if the timestamp being
My experience for the last question is ... it depends. If you have NO
changes to the store (which I would argue could be abnormal, it's not in a
production environment allowing writes) ... then I you can do a full
range/key scan and get no repeats. Factors that will impact scanning all
keys
Ben, can you elaborate on some infrastructure topology issues that would
break this approach?
On Wed, Sep 1, 2010 at 6:25 PM, Benjamin Black b...@b3k.us wrote:
On Wed, Sep 1, 2010 at 4:16 PM, Andres March ama...@qualcomm.com wrote:
I didn't have anything specific in mind. I understand all the
I'm about to be on a series of long plane flights ... is there way to
download the videos from the summit for offline viewing?
Thanks ... The format and download links did the trick
-phil
On Aug 28, 2010, at 7:38 AM, Jeremy Hanna jeremy.hanna1...@gmail.com wrote:
Looks like below each video (on blip.tv) there's a download link - downloads
to a flash video (.flv) file.
On Aug 28, 2010, at 5:33 AM, Phil Stanhope
will not be
returned in the get_range_slices call.
David ... is this what you are referring to?
Is there anyway to tell get_range_slices to return only keys that have a (any)
column?
-phil
On Jul 1, 2010, at 9:03 AM, David Boxenhorn wrote:
Great! Thanks!
On Thu, Jul 1, 2010 at 3:40 PM
In 0.6.x the iterating approach works ... but you need to flush and compact
(after GCGraceSeconds) in order to NOT see the keys in the CF.
Will the behavior of the truncate method in 0.7 require flush/compact as well?
Or will it be immediate?
-phil
On Jun 18, 2010, at 1:29 PM, Benjamin Black
turned this behavior into a feature (of sorts). When this happens I increment
a formally non-zero portion of the timestamp (the last digit of precision which
was always zero) and use this as a counter to track how many times a key/col
was updated (max 9 for my purposes).
-phil
On Jun 18, 2010, at 5
recover? Do you want consistency at the time of
write? Or eventually?
Cassandra has a bunch of knobs that you can turn ... but that flexibility
requires that you think about your expected usage patterns and operational
policies.
-phil
On Jun 15, 2010, at 4:40 PM, Julie wrote:
Benjamin Black b
76 matches
Mail list logo
