Yes, you can have all your normal data centers with DSE configured for
real-time data access and then have a data center that shares the same data
but has DSE Search (Solr indexing) enabled. Your Cassandra data will get
replicated to the Search data center and then indexed there and only there.
We just migrated from a 30 node cluster to a 45 node cluster. (so 15 new
nodes)
By default we have auto_boostrap = false
so we just push our config to the cluster, the cassandra daemons restart,
and they're not cluster members and are the only nodes in the cluster.
Anyway. While I was about
I hadn't considered it because I didn't think it could be configured just
for a single data center; can it?
On Oct 17, 2015 8:50 AM, "Jack Krupansky" wrote:
> Did you consider DSE Search in a DC?
>
> -- Jack Krupansky
>
> On Sat, Oct 17, 2015 at 11:30 AM, Mark Lewis
My advice is to not even consider anything else or make any other changes
to your architecture until you get onto a modern and maintained filesystem.
VERY VERY VERY few people are deploying anything on ReiserFS so you're
going to be the first group encountering any problems.
On Thu, Oct 15, 2015
I've got an existing C* cluster spread across three data centers, and I'm
wrestling with how to add some support for ad-hoc user reporting against
(ideally) near real-time data.
The type of reports I want to support basically boil down to allowing the
user to select a single highly-denormalized
Hi,
I've read all I could find on how cassandra works, I'm still wondering why the
following query takes more than 5s to return on a simple (and modest) 3 nodes
cassandra 2.1.9 cluster:
SELECT sequence_nr, used
FROM messages
WHERE persistence_id = 'session-SW' AND partition_nr = 0;
The
Did you consider DSE Search in a DC?
-- Jack Krupansky
On Sat, Oct 17, 2015 at 11:30 AM, Mark Lewis wrote:
> I've got an existing C* cluster spread across three data centers, and I'm
> wrestling with how to add some support for ad-hoc user reporting against
> (ideally)