Hi, You can run 1 Cassandra, and 1 ES instance. In doing so, you will lose all fault tolerance . When we were running it at Apigee, we have a minimum of 3 nodes of both ES and Cassandra in 2 regions.
If you're willing to take this risk, it can be done. You'll want to update the options for creating the Keyspaces, and the ES indexes to only have an RF = 1. You'll want to apply the CQL in this directory to Cassandra Keyspaces to ensure it keeps running smoothly as your data set size grows. Otherwise you'll encounter performance issues, especially around locks as the lock tombstones grow with the default settings. https://github.com/apache/usergrid/tree/063595805cbf3efad6b961a9170bdf4953aa2e9d/deployment/aws/src/main/cql On Wed, Aug 29, 2018 at 4:18 PM Morescratch <[email protected]> wrote: > Hi there, > > So I have been looking at the estimated cost of running the cloud > formation template provided and it’s quite expensive (~$3K/month). Is there > a minimal specification? The one provided looks likes something that Apigee > would have used. I have tried installing it on a single Instance and it was > fine until I got to around half a million records then it bogged down. So > clearly I need to implement a load balance cluster. Does anyone have > experience with running a minimal stack? I need to keep costs below > $500/month. Not sure it’s even possible. > > Thanks!
