Can you please file a bug (https://github.com/eBay/cassandra-river/issues) or share the stacktrace?
Thanks, -Utkarsh On Tue, Feb 4, 2014 at 8:54 AM, AKhan <ansa...@gmail.com> wrote: > cassandra-river is not working in my case too and I am getting exceptions > on server side. > > elasticsearch.common.UUID; > > On Friday, March 29, 2013 10:01:14 PM UTC+1, utkar...@gmail.com wrote: >> >> Hello, >> >> I have been working on a cassandra river which triggers periodically and >> indexes all data in a cassandra column family. The implementation for now >> spawns 10 threads and processes 10k documents (with 13 columns)/thread. >> The performance initially was very good. It indexed 1M documents in >> 10mins. But after a 1hour, the indexing became very slow and it indexed >> around 8M documents. I am trying to index a total of 50M documents. >> >> I have attached a screenshot of the memory and CPU usage. What I noticed >> was, a lot of merge threads spawned up which reduced the speed considerably: >> "elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]" >> daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000] >> >> So, I believe this has to do with some configuration which I can tweak to >> improve bulk indexing. I am running 1 node with 5 shared with 2GB of >> ES_HEAP_SIZE and no replicas for now. >> >> Shay mentioned some tips here: https://groups.google.com/ >> forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeU in 2011. >> Wanted to know if there are any bulk indexing performance improvements? >> >> I am also using: bulk.execute().addListener() (async) in place of >> bulk.execute().actionGet() (sync) >> >> I am planning to share the cassandra-river as soon its achieves acceptable >> performance. >> >> >> >> <https://lh5.googleusercontent.com/-G8kxNXFaUmc/UVYAPHN-NFI/AAAAAAAAAgw/rmcLu6P1Urg/s1600/bigdesk_ES.png> >> >> >> >> >> <https://lh3.googleusercontent.com/-8RokQMwPSW0/UVYAJFwUvrI/AAAAAAAAAgo/GTEdX5MkTwA/s1600/visualvm_Es.png> >> >> >> Thanks, >> -Utkarsh >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elasticsearch/M1aJqvAIpZE/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/1f5550ca-d53e-4513-b691-8992e0504533%40googlegroups.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- Thanks, -Utkarsh -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CADjjot9uWLyBw%3D7ESYL%3D-sHLJmBLigPx4iON1UjsXNgpWsm18g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
