Is crashing really how it should deal with restricted memory? Seems like if this was true either a minimum required memory needs to be defined, or it should adjust how it uses memory in the absence of it...
On Fri, Apr 16, 2010 at 11:07 AM, Avinash Lakshman < avinash.laksh...@gmail.com> wrote: > Those memtable thresholds also need looking into. You are using some real > poor hardware configuration - 1.7 GB RAM is not a configuration worth > experimenting with IMO. Typical production deployments are running 16 GB RAM > and quad core 64 bit machines. Its hard I would presume to make any > recommendations with this kind of configuration. > > Avinash > > > On Fri, Apr 16, 2010 at 10:58 AM, Paul Brown <paulrbr...@gmail.com> wrote: > >> >> On Apr 16, 2010, at 10:50 AM, Lee Parker wrote: >> > [...] >> > I am trying to migrate data from mysql into the cluster using the >> following methodology: >> > 1. get 500 rows (12 columns each) from mysql >> > 2. build a batch_mutate to insert these rows into one CF (1 row = 1 row >> ) >> > 3. build a second batch_mutate to insert an index of those rows into a >> second CF ( 1 row = 1 column ) >> > 4. loop around and do it again until all data has migrated. >> >> If you have row caching turned on and are putting a lot of data in each >> row, you might be causing the memory issues. Maybe turn row caching off? >> >> -- Paul >> >> >
