What is your partition type? Is it org.apache.cassandra.dht.Murmur3Partitioner?
In your repair command i do see there are two different KeySpaces "MY_KEYSPACE"
and "SN_KEYSPACE", are these two separate key spaces or typo?
-jaydeep
On Tuesday, 27 May 2014 10:26 PM, Matthew Allen
wrote:
Hi,
Am a bit confused regarding data ownership in a multi-dc environment.
I have the following setup in a test cluster with a keyspace with
(placement_strategy = 'NetworkTopologyStrategy' and strategy_options =
{'DC_NSW':2,'DC_VIC':2};)
Datacenter: DC_NSW
==
Replicas: 2
Address R
>
> In case the above doesn't work, another thing to be aware of is that JMX
> uses 2 different ports. The initial connection to 7199 causes a second port
> to be opened, which is normally assigned randomly to an available and
> otherwise unused port above 1024. If your server has a
> firewall/ACL/
Why wouldnt you use datastax enterprise in-memory option vs oracle coherence?
> On May 27, 2014, at 10:33 PM, Samir Faci wrote:
>
> http://www.datastax.com/docs/1.0/references/sstable2json might be what
> you're looking for. It's in the bin folder of your cassandra installation.
>
> Thou
http://www.datastax.com/docs/1.0/references/sstable2json might be what
you're looking for. It's in the bin folder of your cassandra installation.
Though I really doubt you'd want to just drop what is in Oracle into
cassandra. SQL to NoSQL is rarely ever a 1 to 1 mapping.
On Tue, May 27, 2014
Thanks guys!
Yea I am going to do this on a test environment that simulates our
production environment. I was just looking for any potential gotchas, etc.
On Tue, May 27, 2014 at 6:42 PM, Robert Coli wrote:
> On Tue, May 27, 2014 at 1:24 PM, Robert Coli wrote:
>
>> On Tue, May 27, 2014 at 1
On Tue, May 27, 2014 at 1:24 PM, Robert Coli wrote:
> On Tue, May 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 indicated in NOTES.
I'd review the CHANGES.txt to see what has changed and the NEWS.txt to see
what you need to do before upgrading (config changes, data storage changes,
etc).
Generally:
- Determine what version you are upgrading to, and why
- Snapshot the data across all nodes
- Upgrade the nodes one at a time (ro
Charlie,
I would be willing to help you out with your issues tomorrow afternoon, feel
free to give me a call after 4m ET. There are lots of people who store *and*
update data with cassandra (at scale).
--
Colin Clark | Solutions Architect
DataStax | www.datastax.com
m | +1-320-221-9531
e
On Sun, May 25, 2014 at 12:01 PM, Charlie Mason wrote:
> I have a table which has one column per user. It revives at lot of updates
> to these columns through out the life time. They are always updates on a
> few specific columns Firstly is Cassandra storing a Tombstone for each of
> these old col
On Tue, May 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 indicated in NOTES.txt, upgrades to 2.0.x must pass through at least
(iirc?) 1.2.9.
Great! Thanks for the feedback gents.
Have a nice week.
From: Nate McCall
Sent: Tuesday, May 27, 2014 12:39 PM
To: Cassandra Users
I missed that - thanks Holger!
On Tue, May 27, 2014 at 10:14 AM, Holger Hoffstätte
wrote:
On Tue, 27 May 2014 09:26:41 -0500, Nate McC
I've written a bit about upgrading from 1.1 to 1.2, non-vnodes:
http://monkeys.chaordic.com.br/operation/zero-downtime-cassandra-upgrade/
Some tips may be valid for a more recent upgrade, but I'm sure the
community has more specific tips regarding the upgrade from 1.2 to 2.0.
On Tue, May 27, 2014
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?
I missed that - thanks Holger!
On Tue, May 27, 2014 at 10:14 AM, Holger Hoffstätte <
holger.hoffstae...@googlemail.com> wrote:
> On Tue, 27 May 2014 09:26:41 -0500, Nate McCall wrote:
>
> >> In the new setup /tmp was mounted as noexec. So it looks like JNA was
> >> putting the native library her
Hi Tim,
In case the above doesn't work, another thing to be aware of is that JMX
uses 2 different ports. The initial connection to 7199 causes a second port
to be opened, which is normally assigned randomly to an available and
otherwise unused port above 1024. If your server has a
firewall/ACL/Sec
Hi,
Could someone please help on how to import data from Apache Cassandra to
Oracle Coherence.
As per my understanding it could be done by sstable to JSON-->JSON upload
to oracle coherence, however is there any code/tool/script to upload JSON
to Oracle Coherence.
Thanks,
Joy
On Tue, 27 May 2014 09:26:41 -0500, Nate McCall wrote:
>> In the new setup /tmp was mounted as noexec. So it looks like JNA was
>> putting the native library here and then it was unable to execute it.
>>
>>
> If you wanted to keep /tmp noexec (not a bad idea depending on
> environment) you could a
>
>
> In the new setup /tmp was mounted as noexec. So it looks like JNA was
> putting the native library here and then it was unable to execute it.
>
If you wanted to keep /tmp noexec (not a bad idea depending on environment)
you could also append the following to cassandra-env.sh:
JVM_OPTS="$JVM
19 matches
Mail list logo
