+1 for http://opensourceconnections.com/blog/2013/08/31/building- the-perfect-cassandra-test-environment/ <http://opensourceconnections.com/blog/2013/08/31/building-the-perfect-cassandra-test-environment/>
We also run Cassandra on t2.mediums for our Developer clusters. You can force Cassandra to do most "memory" things by hitting the disk instead (on disk compaction passes, flush immediately to disk) and by throttling client connections. In fact on the t2 series memory is not the biggest concern, but rather the CPU credit issue. On Mon, 7 Mar 2016 at 11:53 Robert Coli <rc...@eventbrite.com> wrote: > On Fri, Mar 4, 2016 at 8:27 PM, Jack Krupansky <jack.krupan...@gmail.com> > wrote: > >> Please review the minimum hardware requirements as clearly documented: >> >> http://docs.datastax.com/en/cassandra/3.x/cassandra/planning/planPlanningHardware.html >> > > That is a document for Datastax Cassandra, not Apache Cassandra. It's > wonderful that Datastax provides docs, but Datastax Cassandra is a superset > of Apache Cassandra. Presuming that the requirements of one are exactly > equivalent to the requirements of the other is not necessarily reasonable. > > Please adjust your hardware usage to at least meet the clearly documented >> minimum requirements. If you continue to encounter problems once you have >> corrected your configuration error, please resubmit the details with >> updated hardware configuration details. >> > > Disagree. OP specifically stated that they knew this was not a recommended > practice. It does not seem unlikely that they are constrained to use this > hardware for reasons outside of their control. > > >> Just to be clear, development on less than 4 GB is not supported and >> production on less than 8 GB is not supported. Those are not suggestions or >> guidelines or recommendations, they are absolute requirements. >> > > What does "supported" mean here? That Datastax will not provide support if > you do not follow the above recommendations? Because it certainly is > "supported" in the sense of "it can be made to work" ... ? > > The premise of a minimum RAM level seems meaningless without context. How > much data are you serving from your 2GB RAM node? What is the rate of > client requests? > > To be clear, I don't recommend trying to run production Cassandra with > under 8GB of RAM on your node, but "absolute requirement" is a serious > overstatement. > > > http://opensourceconnections.com/blog/2013/08/31/building-the-perfect-cassandra-test-environment/ > > Has some good discussion of how to run Cassandra in a low memory > environment. Maybe someone should tell John that his 64MB of JVM heap for a > test node is 62x too small to be "supported"? :D > > =Rob > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer
