possible to log the different delays involved in each
operation-- for example, 0.1 seconds to get digests from all nodes, 1 second
to transfer data, etc.?
Thanks,
Mohammad Hajjat
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Logging-Cassandra
Blair, thanks for the clarification! My friend actually just told me the
same..
Any idea on how to do logging??
Thanks!
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Logging-Cassandra-Reads-Writes-tp7588893p7588896.html
Sent from the cassand
ight help you with
> this.
>
> On Tue, Jul 9, 2013 at 1:31 PM, Blair Zajac <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=7588930&i=1>
> > wrote:
>
>> No idea on the logging, I'm pretty new to Cassandra.
>>
>> Regards,
>&
Hi,
Is there a recommended data size for Reads/Writes in Cassandra? I tried
inserting 10 MB objects and the latency I got was pretty high. Also, I was
never able to insert larger objects (say 50 MB) since Cassandra kept
crashing when I tried that.
Here is my experiment setup:
I used two Large VM
“/Insert-heavy workloads will actually be CPU-bound in Cassandra before being
memory-bound/”
However, from reading the documentation
(http://www.datastax.com/docs/1.2/dml/about_writes) it seems the disk is the
real bottleneck in Writes rather than the CPU. This is because everything is
*first *wri
andra Consultant
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.com
>
> On 22/07/2013, at 8:58 AM, hajjat <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=7589236&i=0>>
> wrote:
>
> “/Insert-heavy workloads will actually be CPU-bound in Cassandra bef
ssary.
>
>
> On Thu, Jul 18, 2013 at 4:31 PM, Andrey Ilinykh wrote:
>
>> there is a limit of thrift message ( thrift_max_message_length_in_mb), by
>> default it is 64m if I'm not mistaken. This is your limit.
>>
>>
>> On Thu, Jul 18, 2013 at 2:03 PM, hajj
tually be CPU-bound in Cassandra before
>> being memory-bound”
>>
>> ** **
>>
>> Can someone explain why the internals of why writes are CPU bound ?
>>
>> ** **
>>
>> ** **
>>
>
>
--
*Mohammad Hajjat*
*Ph.D. Student*
*Electrical and Computer Engineering*
*Purdue University*
:
> Everything is written to the commit log. In the case of a crash, cassandra
> recovers by replaying the log.
>
>
> On Sat, Jul 20, 2013 at 9:03 AM, Mohammad Hajjat wrote:
>
>> Patricia,
>>
>> Thanks for the info. So are you saying that the *whole* data is b
they have to be equal, one
less than another, etc.?
The documentation here is not really helping much!
http://www.datastax.com/docs/1.2/configuration/node_configuration#rpc-send-buff-size-in-bytes
Thanks!
--
*Mohammad Hajjat*
*Ph.D. Student*
*Electrical and Computer Engineering*
*Purdue University*
ert-heavy workloads will actually be
> CPU-bound in Cassandra before being memory-bound"?
> What is the source of the quote ?
>
> Cheers
> -
> Aaron Morton
> Cassandra Consultant
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.
the nodes and the latter
> for communication between nodes themselves as evident by the name of the
> property. Please feel free to correct me if I am wrong.
>
> Regards,
> Shahab
>
>
> On Saturday, July 20, 2013, Mohammad Hajjat wrote:
>
>> Hi,
>>
>&g
nd up with same key having two different
values on the two nodes)? Or would each node forward the write request to
the node responsible to hold that key (determined by the hash function)?
Thanks!
--
*Mohammad Hajjat*
*Ph.D. Student*
*Electrical and Computer Engineering*
*Purdue University*
13 matches
Mail list logo