On 8 Sep 2014, at 12:34 pm, Oleg Dulin wrote:
> Another idea I had was taking the ec2-snitch configuration and converting it
> into a Property file snitch. But I still don't understand how to perform this
> move since I need my newly created VPC instances to have public IPs --
> something I wo
In this case, it seems more likely CHANGES.txt will be correct, since it is
maintained *at time of commit*, whereas JIRA fix versions can be forgotten
to be maintained.
On Tue, Sep 9, 2014 at 7:07 AM, Robert Coli wrote:
> On Mon, Sep 8, 2014 at 2:56 PM, Peter Haggerty > wrote:
>
>> When the CHA
On Mon, Sep 8, 2014 at 2:56 PM, Peter Haggerty
wrote:
> When the CHANGES file shows an issue as being in a particular release
> but the JIRA for the issue shows a different version in "Fix Versions"
> which one is right?
>
CHANGES.txt management is kinda a mess. JIRA is likely to be more correct
On Mon, Sep 8, 2014 at 2:01 PM, Tim Heckman wrote:
> We're still using the 1.2.x branch of Cassandra, and will be for some
> time due to the thrift deprecation. Has it only been removed from the
> 2.x line?
>
Other than the fact that 2.0.x is not production ready yet, there's no
reason not to go
When the CHANGES file shows an issue as being in a particular release
but the JIRA for the issue shows a different version in "Fix Versions"
which one is right?
All four of these are listed in 2.0.10 in the CHANGES file:
https://github.com/apache/cassandra/blob/cassandra-2.0/CHANGES.txt
https://i
Thrift is still present in the 2.0 branch as well as 2.1. Where did
you see that it's deprecated?
Let me elaborate my earlier advice. Shuffle was removed because it
doesn't work for anything beyond a trivial dataset. It is definitely
"more risky" than adding a new vnode enabled DC, as it does n
On Mon, Sep 8, 2014 at 1:45 PM, Jonathan Haddad wrote:
> I believe shuffle has been removed recently. I do not recommend using
> it for any reason.
We're still using the 1.2.x branch of Cassandra, and will be for some
time due to the thrift deprecation. Has it only been removed from the
2.x line
I believe shuffle has been removed recently. I do not recommend using
it for any reason.
If you really want to go vnodes, your only sane option is to add a new
DC that uses vnodes and switch to it.
The downside in the 2.0.x branch to using vnodes is that repairs take
N times as long, where N is
On Mon, Sep 8, 2014 at 1:21 PM, Tim Heckman wrote:
> We're still at the exploratory stage on systems that are not
> production-facing but contain production-like data. Based on our
> placement strategy we have some concerns that the new datacenter
> approach may be riskier or more difficult. We'r
On Mon, Sep 8, 2014 at 11:19 AM, Robert Coli wrote:
> On Mon, Sep 8, 2014 at 11:08 AM, Tim Heckman wrote:
>>
>> I'm looking to convert our recently upgraded Cassandra cluster from a
>> single token per node to using vnodes. We've determined that based on
>> our data consistency and usage patterns
I get that, but if you read my opening post, I have an existing cluster
in EC2 classic that I have no idea how to move to VPC cleanly.
On 2014-09-08 19:52:28 +, Bram Avontuur said:
I have setup Cassandra into VPC with the EC2Snitch and it works without
issues. I didn't need to do anything
I have setup Cassandra into VPC with the EC2Snitch and it works without
issues. I didn't need to do anything special to the configuration. I have
created instances in 2 availability zones, and it automatically
picks it up as 2 different data racks. Just make sure your nodes can see
each other in th
Dear Colleagues:
I need to move Cassandra from EC2 classic into VPC.
What I was thinking is that I can create a new data center within VPC
and rebuild it from my existing one (switching to vnodes while I am at
it). However, I don't understand how the ec2-snitch will deal with this.
Another i
On Mon, Sep 8, 2014 at 11:08 AM, Tim Heckman wrote:
> I'm looking to convert our recently upgraded Cassandra cluster from a
> single token per node to using vnodes. We've determined that based on
> our data consistency and usage patterns that shuffling will be the
> best way to convert our live c
Hello,
I'm looking to convert our recently upgraded Cassandra cluster from a
single token per node to using vnodes. We've determined that based on
our data consistency and usage patterns that shuffling will be the
best way to convert our live cluster.
However, when following the instructions for
On Fri, Sep 5, 2014 at 3:20 PM, Rahul Neelakantan wrote:
> The reason I asked about he hints is because I see hints being replayed
> but the large compacted hints stable still sticks around, perhaps it is a
> bug with that version .
>
I've seen this behavior with HH in older versions, so probabl
Hi,
I am running Cassandra 2.0.5 on my PC (with just one node and the default
cassandra.yaml).
I have inserted one million rows into a column family (each row has a int key,
two small set columns.)
In cqlsh, when I did a select count
cqlsh:testks> select count(*) from ips_table limit
It's up for vote right now, so should be a just few days unless something
unexpected happens.
On Mon, Sep 8, 2014 at 4:46 PM, Eugene Voytitsky wrote:
> Hi all,
>
> is there preliminary date when Cassandra 2.1 be finally released (not
> beta/rc)?
>
> --
> Best regards,
> Eugene Voytitsky
>
Hi all,
is there preliminary date when Cassandra 2.1 be finally released (not
beta/rc)?
--
Best regards,
Eugene Voytitsky
19 matches
Mail list logo
