We are also extending our backwards compatibility policy to cover all 3.x
releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for
instance, including cross-version repair.
What will be the EOL policy for releases after 3.0? Given your example, will
3.1 still see bugfixes at
Hi Jonathan
Does documentation fit into the new monthly releases and definition of done
as well, or is that part of another process? I didn't see any mention of it
in the docs, though I may have missed it.
On Thu, 11 Jun 2015 at 9:10 pm Stefan Podkowinski
stefan.podkowin...@1und1.de wrote:
We
3.1 is EOL as soon as 3.3 (the next bug fix release) comes out.
On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski
stefan.podkowin...@1und1.de wrote:
We are also extending our backwards compatibility policy to cover all
3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7,
I've upgraded a node from 2.0.10 to 2.1.6. Before taking down the node,
I've run nodetool upgradesstables and nodetool scrub.
When starting up the node with 2.1.6, I'm getting a MarshalException
(stacktrace included below). For some reason, it seems that C* is trying to
convert a text value from
hey there,
I'm trying to compile a script which include the line #include
cassandra.h . the compilation is never completed and I have the error
file/directory cassandra.h not found. Any idea how to fix this knowing that
I have the Datastax Cassandra cpp-driver installed??
In advance, thank you
Hi,
3.x beta release date ?
2015-06-11 16:21 GMT+02:00 Jonathan Ellis jbel...@gmail.com:
3.1 is EOL as soon as 3.3 (the next bug fix release) comes out.
On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski
stefan.podkowin...@1und1.de wrote:
We are also extending our backwards
As soon as 8099 is done.
On Thu, Jun 11, 2015 at 11:53 AM, Pierre Devops pierredev...@gmail.com
wrote:
Hi,
3.x beta release date ?
2015-06-11 16:21 GMT+02:00 Jonathan Ellis jbel...@gmail.com:
3.1 is EOL as soon as 3.3 (the next bug fix release) comes out.
On Thu, Jun 11, 2015 at 4:10
Please send this question to the DataStax C++ mailing list
https://groups.google.com/a/lists.datastax.com/forum/#!forum/cpp-driver-user
On Thu, Jun 11, 2015 at 8:57 AM, ICHIBA Sara ichi.s...@gmail.com wrote:
hey there,
I'm trying to compile a script which include the line #include
We’re running Cassandra 2.0.9 and just migrated from 2-3 replicas.
We changes our consistency level to 2 during this period while we’re
running a repair.
but we can’t figure out what command to run to repair our data
We *think* we have to run “nodetool repair -pr” on each node.. is that
right?
Looks awesome, do you have any examples/benchmarks of using these indexes
for various cluster sizes e.g. 20 nodes, 60 nodes, 100s+?
On 10 June 2015 at 09:08, Andres de la Peña adelap...@stratio.com wrote:
Hi all,
With the release of Cassandra 2.1.6, Stratio is glad to present its open
source
On Thu, Jun 11, 2015 at 3:59 PM, Kevin Burton bur...@spinn3r.com wrote:
but we can’t figure out what command to run to repair our data
We *think* we have to run “nodetool repair -pr” on each node.. is that
right? or do we have to run nodetool -h hostname repair ?
The simple heuristic is
Considering that 2.1.6 was just released and it is the first “stable” release
ready for production in the 2.1 series, won’t it be too soon to EOL 2.1.x when
3.0 comes out in September?
Mohammed
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Thursday, June 11, 2015 10:14 AM
To: user
By that logic, 2.1.0 should have been somewhat as stable as 2.0.10 (the last
release of 2.0.x branch before 2.1.0). However, we found out that it took
almost 9 months for 2.1.x series to become stable and suitable for production.
Going by past history, I am worried that it may take the same
We've started using the docs-impacting label
https://issues.apache.org/jira/issues/?jql=labels%20%3D%20docs-impacting%20AND%20project%20%3D%20CASSANDRA
to make it easier for the technical writers to keep up, but otherwise we're
not planning any major changes.
On Thu, Jun 11, 2015 at 4:50 AM,
Hi,
I am running a cassandra cluster with 4 dcs. Out of 4 dcs, I have 3 DCs
returning right data but 1 dc where I had 1 node down, the data didn't return
correct records.
So, e.g. DC1 - 386 records (single-token based DC)DC2 - 386 records (vnode
based DC)DC3 - 386 records (vnode based DC)DC4 -
It looks (I’m guessing with entirely not enough info) that you only have two
nodes in DC4, and are probably writing at QUORUM reading at LOCAL_ONE. But
please specify your configuration
On Jun 11, 2015, at 7:01 PM, K F kf200...@yahoo.com wrote:
Hi,
I am running a cassandra cluster with 4
I think the point is that 2.2 will replace 2.1.x + (i.e. the done/safe bits of
3.0 are included in 2.2).. so 2.2.x and 2.1.x are somewhat synonymous.
On Jun 11, 2015, at 8:14 PM, Mohammed Guller moham...@glassbeam.com wrote:
Considering that 2.1.6 was just released and it is the first
So, here is the configuration
DC 1 - 32 single tokenDC 2 - 32 nodes configured as vnodesDC 3 - 32 nodes
configured as vnodesDC 4 - 32 nodes configured as vnodes
Write CL just 2 days backs was one and it was changed to LOCAL_QUORUMRead CL
has always been ONE
I am running on 2.0.9 version of
Can you open a JIRA ticket with details and the schema for that table here?
https://issues.apache.org/jira/browse/CASSANDRA
On Thu, Jun 11, 2015 at 9:23 AM, Tom van den Berge t...@drillster.com
wrote:
I've upgraded a node from 2.0.10 to 2.1.6. Before taking down the node,
I've run nodetool
Sure!
I just opened https://issues.apache.org/jira/browse/CASSANDRA-9582
On Thu, Jun 11, 2015 at 5:27 PM, Tyler Hobbs ty...@datastax.com wrote:
Can you open a JIRA ticket with details and the schema for that table
here? https://issues.apache.org/jira/browse/CASSANDRA
On Thu, Jun 11, 2015
20 matches
Mail list logo
