Any chance your server has been running for the last two weeks with the leap second bug? http://www.datastax.com/dev/blog/linux-cassandra-and-saturdays-leap-second-problem
-Tupshin On Jul 12, 2012 1:43 PM, "Leonid Ilyevsky" <lilyev...@mooncapital.com> wrote: > I am loading a large set of data into a CF with composite key. The load > is going pretty slow, hundreds or even thousands times slower than it would > do in RDBMS.**** > > I have a choice of how granular my physical key (the first component of > the primary key) is, this way I can balance between smaller rows and too > many keys vs. wide rows and fewer keys. What are the guidelines about this? > How the width of the physical row affects the speed of load?**** > > ** ** > > I see that Cassandra is doing a lot of processing behind the scene, even > when I kill the client, the server is still consuming a lot of CPU for a > long time.**** > > ** ** > > What else should I look at ? Anything in configuration? **** > > ------------------------------ > This email, along with any attachments, is confidential and may be legally > privileged or otherwise protected from disclosure. Any unauthorized > dissemination, copying or use of the contents of this email is strictly > prohibited and may be in violation of law. If you are not the intended > recipient, any disclosure, copying, forwarding or distribution of this > email is strictly prohibited and this email and any attachments should be > deleted immediately. This email and any attachments do not constitute an > offer to sell or a solicitation of an offer to purchase any interest in any > investment vehicle sponsored by Moon Capital Management LP (“Moon > Capital”). Moon Capital does not provide legal, accounting or tax advice. > Any statement regarding legal, accounting or tax matters was not intended > or written to be relied upon by any person as advice. Moon Capital does not > waive confidentiality or privilege as a result of this email. >
