Re: Cassandra Summit CFP update

[Scott Hirleman]

To come over the top on this, speaking can be great for your career and
company. And Patrick will help you find a great topic. And you only have to
deal with him for 15min, which is _mostly_ doable ;p

If you need help getting internal approvals - communications or potentially
even budget -, we have a CFP Concierge that can partner with you to try to
get you over the line.

Since these lists are mostly technical people, a talk can be a great chance
to partner with someone in your organization on the business and/or
engineering exec side to tell the story of something awesome you built
enabled by Cassandra. So leverage it to get some visibility internally for
the awesome work you are doing.

Again, you can easily grab time with Patrick to find a topic that would
make a great talk. He loves doing this stuff. So if you are on the fence,
why not submit? If you aren't sure if you'll get approved, is there a harm
in submitting what would be an awesome talk? Maybe a 30min harm to your
schedule at most?

Patrick 15min CFP consult (seriously, take advantage, he'll get you excited
about your topic):
https://calendly.com/patrick-mcfadin/15-minute-cassandra-summit-cfp-consult

On Tue, Nov 29, 2022 at 12:53 PM Patrick McFadin  wrote:

>
>
>
>
>
>
>
>
>
> *Hi everyone,An update on the current CFP process for Cassandra
> Summit. There are currently 23 talk submissions which are far behind what
> we need. Two days of tracks mean we need 60 approved talks. Ideally, we
> need over 100 submitted to ensure we have a good pool of quality talks. We
> already have quite a few vendor pitches that have nothing to do with
> Cassandra. Think of it as like CFP
> spam. https://events.linuxfoundation.org/cassandra-summit/program/cfp/
> <https://events.linuxfoundation.org/cassandra-summit/program/cfp/>The
> deadline is December 11th. That is 12 days! If you are assuming that will
> get pushed out, don’t. We have a tight schedule before March 13th. Speakers
> must be notified of talk acceptance by the beginning of January to book
> travel in time. The full schedule will be published by mid-January. That
> being said, I have talked to quite a few people that are working on a
> submission. Thank you for being willing to create a talk! How can I help
> you get it completed? Again, here is my Calendly link if you need to talk
> it over:
> https://calendly.com/patrick-mcfadin/15-minute-cassandra-summit-cfp-consult
> <https://calendly.com/patrick-mcfadin/15-minute-cassandra-summit-cfp-consult>This
> is our conference! Let’s make it a festival of the database we love and the
> things we build with it. One more thing. We need sponsors! If your employer
> can, this is a great opportunity to get your brand out in front of people
> building the future. I’ll be back. Go submit a talk. You’ll be happy you
> did! Patrick*
>


-- 
Scott Hirleman
scott.hirle...@gmail.com

Re: R/W timeouts VS number of tables in keyspace

[Scott Hirleman]

I feel like that calls for an anti-pattern -> success blog post Luca 藍

On Tue, Jul 20, 2021 at 9:17 AM Luca Rondanini 
wrote:

> Thanks Sean,
>
> I'm switching to G1 in order to gain some time while refactoring. I should
> be able to go down to 4 tables! Yes, the original design was that poor.
>
> Thanks again
>
> On Tue, Jul 20, 2021 at 6:41 AM Durity, Sean R <
> sean_r_dur...@homedepot.com> wrote:
>
>> Each table in the cluster will have a memtable. This is why you do not
>> want to fracture the memory into 900+ slices. The rule of thumb I have
>> followed is to stay in the low hundreds (maybe 200) tables for the whole
>> cluster. I would be requiring the hard refactoring (or moving tables to
>> different clusters) immediately, since you really need to reduce by at
>> least 700 tables. You are seeing the memory impacts.
>>
>>
>>
>> In addition, in my experience, CMS is much harder to tune. G1GC works
>> well in my use cases without much tuning (or Java-guru level knowledge).
>> However, I don’t think that you will be able to engineer around the 900+
>> tables, no matter which GC you use.
>>
>>
>>
>> Sean Durity – Staff Systems Engineer, Cassandra
>>
>>
>>
>> *From:* Luca Rondanini 
>> *Sent:* Monday, July 19, 2021 11:34 AM
>> *To:* user@cassandra.apache.org
>> *Subject:* [EXTERNAL] R/W timeouts VS number of tables in keyspace
>>
>>
>>
>> Hi all,
>>
>>
>>
>> I have a keyspace with almost 900 tables.
>>
>>
>>
>> Lately I started receiving lots of w/r timeouts (eg
>> com.datastax.driver.core.exceptions.Read/WriteTimeoutException: Cassandra
>> timeout during write query at consistency LOCAL_ONE (1 replica were
>> required but only 0 acknowledged the write).
>>
>>
>>
>> *I'm even experiencing nodes crashing.*
>>
>>
>>
>> In the logs I get many warnings like:
>>
>>
>>
>> WARN  [Service Thread]GCInspector.java:282 - ConcurrentMarkSweep GC
>> in 4025ms.  CMS Old Ge
>> n: 2141569800 -> 2116170568; Par Eden Space: 167772160 -> 0; Par Survivor
>> Space: 20971520 -> 0
>>
>>
>> WARN  [GossipTasks:1].FailureDetector.java:288 - Not marking nodes
>> down due to local pause
>> of 5038005208 > 50
>>
>> I know 900 tables is a design error for C* but before a super painful
>> refactoring I'd like to rule out any configuration problem. Any suggestion?
>>
>>
>>
>> Thanks a lot,
>>
>> Luca
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> The information in this Internet Email is confidential and may be legally
>> privileged. It is intended solely for the addressee. Access to this Email
>> by anyone else is unauthorized. If you are not the intended recipient, any
>> disclosure, copying, distribution or any action taken or omitted to be
>> taken in reliance on it, is prohibited and may be unlawful. When addressed
>> to our clients any opinions or advice contained in this Email are subject
>> to the terms and conditions expressed in any applicable governing The Home
>> Depot terms of business or client engagement letter. The Home Depot
>> disclaims all responsibility and liability for the accuracy and content of
>> this attachment and for any damages or losses arising from any
>> inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other
>> items of a destructive nature, which may be contained in this attachment
>> and shall not be liable for direct, indirect, consequential or special
>> damages in connection with this e-mail message or its attachment.
>>
>

-- 
Scott Hirleman
scott.hirle...@gmail.com

Re: 4.0 best feature/fix?

[Scott Hirleman]

Is there a good place to see the docs around the rate limiters? Interested
in how Cassandra could be used to serve/store data products re data mesh
and guardrails are super crucial re serving data to analytics users without
impacting operational performance. :)

On Fri, May 7, 2021 at 7:00 AM Jeff Jirsa  wrote:

> Cassandra 4.0 should work fine with java 11, including zgc (though zgc in
> jdk11 isn't meant to be production ready).
>
> The things I care most about:
> - Much faster streaming, which you care about if you're not using
> EBS/Disaggregated storage
> - Virtual tables that make observability much more consistent (less JMX,
> more CQL)
> - Incremental repair finally actually works (correctly)
> - There's a bunch of new defensive rate limiters and hot-tunable
> properties in the database that people will enjoy once they need to use them
> - JDK11
>
>
>
>
> On Fri, May 7, 2021 at 6:05 AM Joe Obernberger <
> joseph.obernber...@gmail.com> wrote:
>
>> Hi Sean - I'm using RC1 now in a research environment on bare metal.  The
>> biggest drawback of Cassandra for me is that Cassandra has issues working
>> with modern large servers - a server with >32TBytes of SSD seems to be a
>> non-starter.
>>
>> I tried running Cassandra with java 11, and that doesn't appear to work.
>>
>> -Joe
>> On 5/7/2021 8:47 AM, Durity, Sean R wrote:
>>
>> There is not enough 4.0 chatter here. What feature or fix of the 4.0
>> release is most important for your use case(s)/environment? What is working
>> well so far? What needs more work? Is there anything that needs more
>> explanation?
>>
>>
>>
>> Sean Durity
>>
>> Staff Systems Engineer – Cassandra
>>
>> #cassandra - for the latest news and updates
>>
>>
>>
>>
>>
>> --
>>
>> The information in this Internet Email is confidential and may be legally
>> privileged. It is intended solely for the addressee. Access to this Email
>> by anyone else is unauthorized. If you are not the intended recipient, any
>> disclosure, copying, distribution or any action taken or omitted to be
>> taken in reliance on it, is prohibited and may be unlawful. When addressed
>> to our clients any opinions or advice contained in this Email are subject
>> to the terms and conditions expressed in any applicable governing The Home
>> Depot terms of business or client engagement letter. The Home Depot
>> disclaims all responsibility and liability for the accuracy and content of
>> this attachment and for any damages or losses arising from any
>> inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other
>> items of a destructive nature, which may be contained in this attachment
>> and shall not be liable for direct, indirect, consequential or special
>> damages in connection with this e-mail message or its attachment.
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
>>  Virus-free.
>> www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=emailclient>
>> <#m_-3272604231784000544_m_654382365824200109_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>

-- 
Scott Hirleman
scott.hirle...@gmail.com

Re: Network Bandwidth and Multi-DC replication

[Scott Hirleman]

ons:
>
> 1. Would you considers these factors expected behaviour?
>
>
> 13 seems high. 9 seems more correct unless you’re double counting sending
> and receiving.
>
> 2. Are there ways to reduce the traffic through configuration?
>
>
> Compression, reducing RF, maybe mitigation with longer timeouts to avoid
> double sending hints.
>
>
> A few additional notes on the setup:
>
> * use NetworkTopologyStrategy for replication and
> cassandra-rackdc.properties to configure the GossipingPropertyFileSnitch
> * internode_compression is set to dc
> * inter_dc_tcp_nodelay is set to false
>
> Any help is highly appreciated!
>
> Best Regards
> Jens
>
> Geschäftsführer: Oliver Koch (CEO), Jean-Baptiste Cornefert, Christoph
> Ostermann, Hermann Schweizer, Bianca Swanston
> Amtsgericht Kempten/Allgäu, Registernummer: 10655, Steuernummer
> 127/137/50792, USt.-IdNr. DE272208908
>
>
> Geschäftsführer: Oliver Koch (CEO), Jean-Baptiste Cornefert, Christoph
> Ostermann, Hermann Schweizer, Bianca Swanston
> Amtsgericht Kempten/Allgäu, Registernummer: 10655, Steuernummer
> 127/137/50792, USt.-IdNr. DE272208908
>
>
> Geschäftsführer: Oliver Koch (CEO), Jean-Baptiste Cornefert, Christoph
> Ostermann, Hermann Schweizer, Bianca Swanston
> Amtsgericht Kempten/Allgäu, Registernummer: 10655, Steuernummer
> 127/137/50792, USt.-IdNr. DE272208908
>


-- 
Scott Hirleman
scott.hirle...@gmail.com

Re: Commercial Support Providers?

[SmartCat - Scott Hirleman]

Other one I've run across is Insight In Data <http://insightindata.com/>.
Pretty flexible and cost effective. Can't speak to how knowledgeable they
are but in my small amount of dealings with them, they are easy to work
with.

On Thu, Nov 3, 2016 at 9:13 PM, Ben Slater <ben.sla...@instaclustr.com>
wrote:

> I can confirm that we do offer support contracts for OSS Apache Cassandra
> at Instaclustr (in addition to our managed service) - either drop me an
> email direct (signature below) or contact sa...@instaclustr.com and would
> be happy to discuss details.
>
> Cheers
> Ben
>
> On Fri, 4 Nov 2016 at 14:02 Max C <mc_cassan...@core43.com> wrote:
>
>> Hello -
>>
>> We’re rolling out a small cluster at my work (2 DCs of 3 nodes each —
>> hosted on-premises), and my boss has asked us to look into commercial
>> support offerings.
>>
>> The main thing we’re looking for is a company that we can call day or
>> night if/when things go “kaboom” and I can’t figure out what the problem is
>> (ex: an upgrade fails unexpectedly, weird error messages in the logs,
>> repairs keep failing, etc).  If they offer their own tested, supported,
>> patched, version of Cassandra that would be ideal, and certainly management
>> tools like OpsCenter are a bonus.
>>
>> The obvious choice here is DataStax, and we’re definitely talking to
>> them.  Are there any other providers which offer this sort of service?
>> Maybe Instaclustr?
>>
>> Thanks.
>>
>> - Max
>
>


-- 
*Scott Hirleman*
*Head of US Marketing and Sales*
www.smartcat.io
https://github.com/smartcat-labs <http://www.smartcat.io/>

<https://github.com/smartcat-labs>

Re: Improving cassandra documentation

[SmartCat - Scott Hirleman]

Totally agree, I just saw DataStax + docs so I figured it was about DSE,
not OSS C* *shrug*.

On Thu, Nov 3, 2016 at 2:24 PM, Justin Cameron <jus...@instaclustr.com>
wrote:

> Maybe a little off-tangent, but there is also a set of open source
> documentation now available on the Apache Cassandra website:
> http://cassandra.apache.org/doc/latest/
>
> You can contribute to them directly via git
>
> On Thu, 3 Nov 2016 at 12:11 SmartCat - Scott Hirleman <sc...@smartcat.io>
> wrote:
>
>> http://docs.datastax.com/en/landing_page/doc/landing_page/contact.html
>> Looks like it is still just email d...@datastax.com
>>
>> On Thu, Nov 3, 2016 at 9:34 AM, Oleg Krayushkin <allight...@gmail.com>
>> wrote:
>>
>> Hi, from time to time I find errors in datastax cassandra docs. Is there
>> a right & easy way to report them?
>>
>> Thanks.
>>
>> --
>>
>> Oleg Krayushkin
>>
>>
>>
>>
>> --
>> *Scott Hirleman*
>> *Head of US Marketing and Sales*
>> www.smartcat.io
>> https://github.com/smartcat-labs <http://www.smartcat.io/>
>>
>> <https://github.com/smartcat-labs>
>>
> --
>
> Justin Cameron
>
> Senior Software Engineer | Instaclustr
>
>
>
>
> This email has been sent on behalf of Instaclustr Pty Ltd (Australia) and
> Instaclustr Inc (USA).
>
> This email and any attachments may contain confidential and legally
> privileged information.  If you are not the intended recipient, do not copy
> or disclose its content, but please reply to this email immediately and
> highlight the error to the sender and then immediately delete the message.
>
>


-- 
*Scott Hirleman*
*Head of US Marketing and Sales*
www.smartcat.io
https://github.com/smartcat-labs <http://www.smartcat.io/>

<https://github.com/smartcat-labs>

Re: Improving cassandra documentation

[SmartCat - Scott Hirleman]

http://docs.datastax.com/en/landing_page/doc/landing_page/contact.html
Looks like it is still just email d...@datastax.com

On Thu, Nov 3, 2016 at 9:34 AM, Oleg Krayushkin <allight...@gmail.com>
wrote:

> Hi, from time to time I find errors in datastax cassandra docs. Is there a
> right & easy way to report them?
>
> Thanks.
>
> --
>
> Oleg Krayushkin
>



-- 
*Scott Hirleman*
*Head of US Marketing and Sales*
www.smartcat.io
https://github.com/smartcat-labs <http://www.smartcat.io/>

<https://github.com/smartcat-labs>

Re: Unsubscribe

[SmartCat - Scott Hirleman]

That doesn't work. You need to send an email to user-unsubscribe@cassandra.
apache.org

On Sat, Oct 29, 2016 at 1:53 AM, dhanesh malviya <dnesh...@gmail.com> wrote:

>
>
> --
> Regards,
> Dhanesh Malviya..
>



-- 
*Scott Hirleman*
*Head of US Marketing and Sales*
www.smartcat.io
https://github.com/smartcat-labs <http://www.smartcat.io/>

<https://github.com/smartcat-labs>

Re: unsubscribe

[SmartCat - Scott Hirleman]

That doesn't work. You need to send an email to
user-unsubscr...@cassandra.apache.org

On Thu, Oct 27, 2016 at 11:22 AM, Anseh Danesharasteh <
anseh.dan...@gmail.com> wrote:

> unsubscribe
>



-- 
*Scott Hirleman*
*Head of US Marketing and Sales*
www.smartcat.io
https://github.com/smartcat-labs <http://www.smartcat.io/>

<https://github.com/smartcat-labs>

Re: Upgrading from Cassandra 2.1.12 to 3.0.9

[SmartCat - Scott Hirleman]

I think the TLP team are recommending the approach I would as well, which
is to spin up a new cluster and copy your data into it for testing
purposes. If your app isn't in production yet, playing around with 3.7 is
great, really helps the community as Jon said; the word "upgrading" will
set off many alarm bells because the connotation is you have a stable
application built and are looking to put it on pretty bleeding edge tech
that hasn't been well tested yet, which is usually a road to tears.

On Fri, Sep 23, 2016 at 10:28 AM, Jonathan Haddad <j...@jonhaddad.com> wrote:

> I strongly recommend not upgrading to 3.7.  Here's my thoughts on Tick
> Tock releases, copy / pasted from a previous email I wrote on this ML:
>
> 3.7 falls under the Tick Tock release cycle, which is almost completely
> untested in production by experienced operators.  In the cases where it has
> been tested, there have been numerous bugs found which I (and I think most
> people on this list) consider to be show stoppers.  Additionally, the Tick
> Tock release cycle puts the operator in the uncomfortable position of
> having to decide between upgrading to a new version with new features
> (probably new bugs) or back porting bug fixes from future versions
> themselves.There will never be a 3.7.1 release which fixes bugs in 3.7
> without adding new features.
>
> https://github.com/apache/cassandra/blob/trunk/NEWS.txt
>
> For new projects I recommend starting with the recently released 3.0.9.
>
> Assuming the project changes it's policy on releases (all signs point to
> yes), then by the time 4.0 rolls out a lot of the features which have been
> released in the 3.x series will have matured a bit, so it's very possible
> 4.0 will stabilize faster than the usual 6 months it takes for a major
> release.
>
> All that said, there's nothing wrong with doing compatibility & smoke tests
> against the latest 3.x release as well as 3.0 and reporting bugs back to
> the Apache Cassandra JIRA, I'm sure it would be greatly appreciated.
>
> https://issues.apache.org/jira/secure/Dashboard.jspa
>
> Jon
>
>
>
> On Fri, Sep 23, 2016 at 9:00 AM Khaja, Raziuddin (NIH/NLM/NCBI) [C] <
> raziuddin.kh...@nih.gov> wrote:
>
>> Thank you Joaquim for the advice.
>>
>>
>>
>> I seem to have sent this email with the wrong subject.  It should have
>> been *Upgrading from Cassandra 2.1.12 to 3.7*, but too late now.
>>
>>
>>
>> The plan is to upgrade from 2.1.12 to 3.7 and to maintain a heterogeneous
>> cluster only for a short time, while we observe how 3.7 reacts to our
>> client applications with traffic, then proceed with upgrading all DCs to
>> 3.7.
>>
>>
>>
>> In our current installation we are using *memtable_allocation_type:
>> offheap_objects*. Support for offheap_objects was removed in the 3.0.x
>> branch and only added back in 3.4+, so an upgrade to 3.0.9 will not be
>> possible for me unless I change this parameter.
>>
>> Still looking to hear from others about upgrade experiences, problems etc.
>>
>> -Razi
>>
>>
>>
>> *From: *Joaquin Casares <joaq...@thelastpickle.com>
>> *Reply-To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
>> *Date: *Friday, September 23, 2016 at 11:41 AM
>> *To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
>> *Cc: *"Khaja, Raziuddin (NIH/NLM/NCBI) [C]" <raziuddin.kh...@nih.gov>
>> *Subject: *Re: Upgrading from Cassandra 2.1.12 to 3.0.9
>>
>>
>>
>> Hello Razi,
>>
>>
>>
>> Since you were using a highly stable version of 2.1.x, you may want to
>> stick with using 3.0.9. 3.7 has introduced many great features, but has not
>> been as heavily tested in production as 3.0.9.
>>
>>
>>
>> Running heterogenous clusters, even when using the same major version
>> (e.g. 3.0.8 and 3.0.9), is never recommended. Running a cluster that spans
>> major releases, for longer than the timespan of a routine upgrade, is
>> strongly not advised.
>>
>>
>>
>> Hope that helps!
>>
>>
>> Joaquin Casares
>>
>> Consultant
>>
>> Austin, TX
>>
>>
>>
>> Apache Cassandra Consulting
>>
>> http://www.thelastpickle.com
>>
>>
>>
>> On Fri, Sep 23, 2016 at 8:17 AM, Khaja, Raziuddin (NIH/NLM/NCBI) [C] <
>> raziuddin.kh...@nih.gov> wrote:
>>
>> Hello all,
>>
>>
>>
>> I would like to upgrade my Cassandra cluster from 2.1.12 to 3.7.
>>
>>
>>
>> I have read the followi

Re: Scalability of Gossip protocol

[SmartCat - Scott Hirleman]

I'd search through some of the VLDB papers that have come out in the last
few years. C* can scale to 100+ nodes more easily than any other technology
I'm aware of, scalability is one of the key driving factors of C* adoption
picking up.

On Sun, Aug 28, 2016 at 11:28 AM, jean paul <researche...@gmail.com> wrote:

> Hi, thank you so much for help.
> Please is there a scientific study that evaluates the* scalability* of
> Cassandra? Bests.
>
> 2016-08-16 20:15 GMT+01:00 Jeff Jirsa <jeff.ji...@crowdstrike.com>:
>
>> Jason Brown has an interesting set of tickets:
>>
>>
>>
>> https://issues.apache.org/jira/browse/CASSANDRA-12345
>>
>>
>>
>> One of the sub-tickets there is https://issues.apache.org/jira
>> /browse/CASSANDRA-12347
>>
>>
>>
>> That ticket links to a relevant paper on the subject (and an alternative
>> to the existing approach): http://www.gsd.inesc-id.pt/~jl
>> eitao/pdf/srds10-mario.pdf
>>
>>
>>
>>
>>
>>
>>
>> *From: *jean paul <researche...@gmail.com>
>> *Reply-To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
>> *Date: *Tuesday, August 16, 2016 at 12:07 PM
>> *To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
>> *Subject: *Scalability of Gossip protocol
>>
>>
>>
>> Hi all;
>>
>> Please is there a scientific study that evaluates the scalability of
>> Gossip protocol ?
>>
>> Thank you so much for help
>>
>> Kind regards.
>>
>>
>>
>
>


-- 
*Scott Hirleman*
*Head of US Marketing and Sales*
www.smartcat.io
https://github.com/smartcat-labs <http://www.smartcat.io/>

<http://t.sidekickopen63.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg3LjyGCVdnPwd1q0Qm8VS9Tpj56dWxsf72jsj002?t=https%3A%2F%2Fgithub.com%2Fsmartcat-labs=6603702734159872=42893d32-e6b8-4382-c494-d9b198250931>

Re: Support/Consulting companies

[SmartCat - Scott Hirleman]

https://www.smartcat.io/ I'll throw our name in the ring; 2 C* MVPs and
counting :)

On Mon, Aug 22, 2016 at 7:54 AM, Andres de la Peña 
wrote:

> http://www.stratio.com/
>
>
> On 2016-08-19 20:02 (+0100), Roxy Ubi  wrote:
> > Howdy,
> >
> > I'm looking for a list of support or consulting companies that provide
> > contracting services related to Cassandra.  Is there a comprehensive
> list
> > somewhere?  Alternatively could you folks tell me who you use?
> >
> > Thanks in advance for any replies!
> >
> > Roxy
> >
>

Re: Open source equivalents of OpsCenter

[Scott Hirleman]

We built a Cassandra metrics tracking and monitoring project
https://github.com/smartcat-labs/cassandra-diagnostics that will pump said
metrics into your monitoring system; we are working on adding new features
(maybe repair and restart) but I've also always heard good things about
Spotify's Reaper https://github.com/spotify/cassandra-reaper re repairs

Scott
SmartCat - Big Data Development Consulting That Doesn't Suck

On Thu, Jul 14, 2016 at 3:48 AM, Michał Łowicki  wrote:

> My experience while looking for a replacement on
>
> https://medium.com/@mlowicki/alternatives-to-datastax-opscenter-8ad893efe063
> 
>
> 
> On Thursday, 14 July 2016, Stefano Ortolani  wrote:
>
>> Replaced OpsCenter with a mix of:
>>
>> * metrics-graphite-3.1.0.jar installed in the same classpath of C*
>> * Custom script to push system metrics (cpu/mem/io)
>> * Grafana to create the dashboard
>> * Custom repairs script
>>
>> Still not optimal but getting there...
>>
>> Stefano
>>
>> On Thu, Jul 14, 2016 at 10:18 AM, Romain Hardouin 
>> wrote:
>>
>>> Hi Juho,
>>>
>>> Out of curiosity, which stack did you use to make your dashboard?
>>>
>>> Romain
>>>
>>> Le Jeudi 14 juillet 2016 10h43, Juho Mäkinen  a
>>> écrit :
>>>
>>>
>>> I'm doing some work on replacing OpsCenter in out setup. I ended
>>> creating a Docker container which contains the following features:
>>>
>>>  - Cassandra 2.2.7
>>>  - MX4J (a JMX to REST bridge) as a java-agent
>>>  - metrics-graphite-3.1.0.jar (export some but not all JMX to graphite)
>>>  - a custom ruby which uses MX4J to export some JMX metrics to graphite
>>> which we don't otherwise get.
>>>
>>> With this I will get all our cassandra instances and their JMX exposed
>>> data to graphite, which allows us to use Grafana and Graphite to draw
>>> pretty dashboards.
>>>
>>> In addition I started writing some code which currently provides the
>>> following features:
>>>  - A dashboard which provides a similar ring view what OpsCenter does,
>>> with onMouseOver features to display more info on each node.
>>>  - Simple HTTP GET/POST based api to do
>>> - Setup a new non-vnode based cluster
>>> - Get a JSON blob on cluster information, all its tokens, machines
>>> and so on
>>> - Api for new cluster instances so that they can get a token slot
>>> from the ring when they boot.
>>> - Option to kill a dead node and mark its slot for replace, so the
>>> new booting node can use cassandra.replace_address option.
>>>
>>> The node is not yet packaged in any way for distribution and some parts
>>> depend on our Chef installation, but if there's interest I can publish at
>>> least some parts from it.
>>>
>>>  - Garo
>>>
>>> On Thu, Jul 14, 2016 at 10:54 AM, Romain Hardouin 
>>> wrote:
>>>
>>> Do you run C* on physical machine or in the cloud? If the topology
>>> doesn't change too often you can have a look a Zabbix. The downside is that
>>> you have to set up all the JMX metrics yourself... but that's also a good
>>> point because you can have custom metrics. If you want nice
>>> graphs/dashboards you can use Grafana to plot Zabbix data. (We're also
>>> using SaaS but that's not open source).
>>> For the rolling restart and other admin stuff we're using Rundeck. It's
>>> a great tool when working in a team.
>>>
>>> (I think it's time to implement an open source alternative to OpsCenter.
>>> If some guys are interested I'm in.)
>>>
>>> Best,
>>>
>>> Romain
>>>
>>>
>>>
>>>
>>> Le Jeudi 14 juillet 2016 0h01, Ranjib Dey  a
>>> écrit :
>>>
>>>
>>> we use datadog (metrics emitted as raw statsd) for the dashboard. All
>>> repair & compaction is done via blender & serf[1].
>>> [1]https://github.com/pagerduty/blender
>>>
>>>
>>> On Wed, Jul 13, 2016 at 2:42 PM, Kevin O'Connor 
>>> wrote:
>>>
>>> Now that OpsCenter doesn't work with open source installs, are there any
>>> runs at an open source equivalent? I'd be more interested in looking at
>>> metrics of a running cluster and doing other tasks like managing
>>> repairs/rolling restarts more so than historical data.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
> --
> BR,
> Michał Łowicki
>
>