[Cassandra 2.1.5]
I'm trying to explore my options for increasing read throughput with token
scans (SELECT * FROM x WHERE token(y) L AND token(y) L). So far I've
started by reading an entire virtual token range from a single node.
Currently on a single query I can read about 57,286.03 rows/s
Fabien, thanks for the reply. We do have Thrift enabled. From what I can
tell, the Could not retrieve endpoint ranges: crops up under various
circumstances.
From further reading on sstableloader, it occurred to me that it might be a
safer bet to use the JMX StorageService bulkLoad command,
I checked the system.log for the Cassandra node that I did the jconsole JMX
session against and which had the data to load. Lot of log output
indicating that it's busy loading the files. Lot of stacktraces indicating
a broken pipe. I have no reason to believe there are connectivity issues
between
Hi Matthew,
It looks fine to me. I have built a similar service that allows a user to
submit a query from a browser and returns the result in JSON format.
Another alternative is to leave a Spark shell or one of the notebooks (Spark
Notebook, Zeppelin, etc.) session open and run queries from
Hi,
For the record I've succesfully used
https://github.com/BrianGallew/cassandra_range_repair to make smooth repairing.
Could maybe also be of interest don't know...
Cheers,
Jens
–
Skickat från Mailbox
On Fri, Jun 19, 2015 at 8:36 PM, null sean_r_dur...@homedepot.com wrote:
It
Hi Ben,
thank for your reply. That was I was afraid of actually as it means
there's no easy solution to implement I guess.
I think some guys in my team are in contact with DS people, so I may
have a look there.
Jonathan
On 06/18/2015 07:26 PM, Ben Bromhead wrote:
OpsCenter is a little bit
Hi,
I already got this error on a 2.1 clusters because thrift was disabled. So
you should check that thrift is enabled and accessible from the
sstableloader process.
Hope this help
Fabien
Le 19 juin 2015 05:44, Mitch Gitman mgit...@gmail.com a écrit :
I'm using sstableloader to bulk-load a
Perfect thank you.
So making a weekly nodetool repair -pr” on all nodes one after the other will
repair my cluster. That is great.
If it does a compaction, does it mean that it would also clean up my tombstone
from my LeveledCompactionStrategy tables at the same time?
Thanks for your help.
Yes compactions will remove tombstones
On Thu, Jun 18, 2015 at 11:46 PM, Jean Tremblay
jean.tremb...@zen-innovations.com wrote:
Perfect thank you.
So making a weekly nodetool repair -pr” on all nodes one after the other
will repair my cluster. That is great.
If it does a compaction,
Hi all,
I have been struggling with Cassandra’s lack of adhoc query support (I know
this is an anti-pattern of Cassandra, but sometimes management come over
and ask me to run stuff and it’s impossible to explain that it will take me
a while when it would take about 10 seconds in MySQL) so I
Hi,
I understand that we must repair the DB on a regular basis.
Now I also see that making a repair is using lots of resources in the cluster
so I need to do this during the weekend because I really would like to have
high performance at least during the week days.
In the documentation I see
Hi,
One valuable (IMHO) entry point is : « Guide to Cassandra Thread Pools »
http://blackbird.io/guide-to-cassandra-thread-pools
Take a look.
Regards,
Dominique
De : pushdlim...@gmail.com [mailto:pushdlim...@gmail.com] De la part de Saurabh
Chandolia
Envoyé : vendredi 19 juin 2015 11:42
À :
Well, it does sound like you just need proxies for cluster-configs,
TestCluster, etc... Your site is called opscenter and then you proxy a
directory called opscenter. But the 2 have nothing to do with each other.
Your site can be called opscenter and then you need a proxy for
TestCluster,
Hi
Is their any way to schedule a job in cassandra to delete the recrods which
are older than a specific time period.
Excluding the option of TTL.
Regards
Anil
Sent from Samsung Mobile
Hi Spencer,
I certainly know how to configure a proxy or how to rewrite URLs if I
need to and we are currently not looking for a contractor, but thanks
for your message! :)
Jonathan
On 06/18/2015 11:29 AM, Spencer Brown wrote:
First, your firewall should really be your frontend There
I have a C* 2.1.5 with 24 nodes.A few days ago ,I have remove a node from
this cluster using nodetool decommission.
But tody I find some log like this:
INFO [GossipStage:1] 2015-06-19 17:38:05,616 Gossiper.java:968 -
InetAddress /172.19.105.41 is now DOWN
INFO [GossipStage:1] 2015-06-19
Hi,
I have recently started using Cassandra. As of now, I am only using cfstats
and cfhistograms to monitor individual CF stats. What all cassandra metrics
should I watch for stability and performance? Are there any tools to do the
same? Is there any performance overhead if I start monitoring too
Hi,
This is not necessarily true. Repair will induce compactions only if you
have entropy in your cluster. If not it will just read your data to compare
all the replica of each piece of data (using indeed cpu and disk IO).
If there is some data missing it will repair it. Though, due to merkle
Thanks Rob, this was helpful.
More counters will be added soon, I'll let you know if those have any
problems.
On Mon, Jun 15, 2015 at 4:32 PM, Robert Coli rc...@eventbrite.com wrote:
On Mon, Jun 15, 2015 at 2:52 PM, Dan Kinder dkin...@turnitin.com wrote:
Potentially relevant facts:
-
Thank you for your reply.
On 19 Jun 2015, at 20:36,
sean_r_dur...@homedepot.commailto:sean_r_dur...@homedepot.com
sean_r_dur...@homedepot.commailto:sean_r_dur...@homedepot.com wrote:
It seems to me that running repair on any given node may also induce repairs to
related replica nodes. For
It seems to me that running repair on any given node may also induce repairs to
related replica nodes. For example, if I run repair on node A and node B has
some replicas, data might stream from A to B (assuming A has newer/more data).
Now, that does NOT mean that node B will be fully repaired.
21 matches
Mail list logo
