cassandra-stress has some (many) limitations - that I had planned to address now it's seeing wider adoption, but since I no longer work on the project for my day job I am unlikely to now... so, sorry but you'll have to tolerate them :)
In particular, the problem you encounter here is that a given clustering *tier* must be generated in its entirety before performing any operation that touches any of its values (read or write), regardless of how many are actually needed. So, if you have a single clustering column in your primary key, the client must generate the entire partition. And if you have a million of them, you may just be watching your cassandra-stress instance enter a GC spiral and die slowly; in all likelihood the data you see is just the partitions that get randomly assigned a modest size in your range. If you need to generate giant partitions, at the moment you need to have multiple clustering columns, and preferably keep the cardinality of each to at most a few hundred. The smaller, the faster queries that only touch small portions of the partition will run (such as point or range queries, or partial insertions) On 15 June 2016 at 13:24, Peter Kovgan <peter.kov...@ebsbrokertec.com> wrote: > Hi, > > > > The cassandra-stress is not helping really to populate the disk > sufficiently. > > > > I tried several table structures, providing > > cluster: UNIFORM(1..10000000000) on clustering parts of the PK. > > > > Partition part of PK makes about 660 000 partitions. > > > > The hope was create enough cells in a row, make the row really WIDE. > > > > No matter what I tried, does no matter how long it runs, I see maximum 2-3 > SSTables per node and maximum 300Mb of data per node. > > > > (I have 6 nodes and very active 400 threads stress) > > > > It looks, like It is impossible to make the row really wide and disk > really full. > > > > Is it intentional? > > > > I mean, if there was an intention to avoid really wide rows, why there is > no hint on this in docs? > > > > Do you have similar experience and do you know how resolve that? > > > > Thanks. > > > > > > > > > > > ************************************************************************************************************************ > This communication and all or some of the information contained therein > may be confidential and is subject to our Terms and Conditions. If you have > received this communication in error, please destroy all electronic and > paper copies and notify the sender immediately. Unless specifically > indicated, this communication is not a confirmation, an offer to sell or > solicitation of any offer to buy any financial product, or an official > statement of ICAP or its affiliates. Non-Transactable Pricing Terms and > Conditions apply to any non-transactable pricing provided. All terms and > conditions referenced herein available at www.icapterms.com. Please > notify us by reply message if this link does not work. > > ************************************************************************************************************************ >
