Re: Commercial Support Providers?

[SmartCat - Scott Hirleman]

Other one I've run across is Insight In Data .
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 
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  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 

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 
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 

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  wrote:

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



-- 
*Scott Hirleman*
*Head of US Marketing and Sales*
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 

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  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 
>> *Reply-To: *"user@cassandra.apache.org" 
>> *Date: *Friday, September 23, 2016 at 11:41 AM
>> *To: *"user@cassandra.apache.org" 
>> *Cc: *"Khaja, Raziuddin (NIH/NLM/NCBI) [C]" 
>> *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 following documentation:
>>
>> · http://docs.datastax.com/en/latest-upgrade/upgrade/
>> cassandra/upgrdCassandra.html
>>
>> · https://github.com/apache/cassandra/blob/cassandra-3.7/NEWS.txt
>>
>>
>>
>> but still had some questions:
>>
>> · The upgrdCassandra.html page says : “Upgrade from Cassandra
>> 2.1 versions later or equal to 2.1.9 directly to Cassandra 3.0.x”, and I am
>> not sure if this includes 3.x, my question is: Can I upgrade directly to
>> 3.7?
>>
>> · Can I run a heterogeneous cluster, with one DC running 2.1.12
>> and another DC running 3.7?
>>
>>
>>
>> Thanks,
>>
>> -Razi
>>
>>
>>
>


-- 
*Scott Hirleman*
*Head of US Marketing and Sales*

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  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 :
>
>> 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 
>> *Reply-To: *"user@cassandra.apache.org" 
>> *Date: *Tuesday, August 16, 2016 at 12:07 PM
>> *To: *"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 

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
> >
>