incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Les Hazlewood <...@katasoft.com>
Subject Re: 99.999% uptime - Operations Best Practices?
Date Thu, 23 Jun 2011 00:31:57 GMT
Hi Thoku,

You were able to more concisely represent my intentions (and their
reasoning) in this thread than I was able to do so myself.  Thanks!

On Wed, Jun 22, 2011 at 5:14 PM, Thoku Hansen <thokuh@gmail.com> wrote:

> I think that Les's question was reasonable. Why *not* ask the community for
> the 'gotchas'?
>
> Whether the info is already documented or not, it could be an opportunity
> to improve the documentation based on users' perception.
>
> The "you just have to learn" responses are fair also, but that reminds me
> of the days when running Oracle was a black art, and accumulated wisdom made
> DBAs irreplaceable.
>

Yes, this was my initial concern.  I know that Cassandra is still young, and
I expect this to be the norm for a while, but I was hoping to make that
process a bit easier (for me and anyone else reading this thread in the
future).

Some recommendations *are* documented, but they are dispersed / stale /
> contradictory / or counter-intuitive.
>
> Others have not been documented in the wiki nor in DataStax's doco, and are
> instead learned anecdotally or The Hard Way.
>
> For example, whether documented or not, some of the 'gotchas' that I
> encountered when I first started working with Cassandra were:
>
> * Don't use OpenJDK. Prefer the Sun JDK. (Wiki says this<http://wiki.apache.org/cassandra/GettingStarted>
> , Jira says that <https://issues.apache.org/jira/browse/CASSANDRA-2441>).
> * Its not viable to run without JNA installed.
> * Disable swap memory.
> * Need to run nodetool repair on a regular basis.
>
> I'm looking forward to Edward Capriolo's Cassandra book<https://www.packtpub.com/cassandra-apache-high-performance-cookbook/book>
which
> Les will probably find helpful.
>

Thanks for linking to this.  I'm pre-ordering right away.

And thanks for the pointers, they are exactly the kind of enumerated things
I was looking to elicit.  These are the kinds of things that are hard to
track down in a single place.  I think it'd be nice for the community to
contribute this stuff to a single page ('best practices', 'checklist',
whatever you want to call it).  It would certainly make things easier when
getting started.

Thanks again,

Les

Mime
View raw message