I fully agree with Benedict here. I would much prefer to keep this sort of toxic behavior off the ML. People can link to whatever helpful docs / blogs they choose.
On Fri, Sep 9, 2016 at 1:12 PM Benedict Elliott Smith <bened...@apache.org> wrote: > Come on. This kind of inconsistent 'policing' is not helpful. > > By all means, push the *committers* to improve the project docs as is > happening, and to promote the internal resources over external ones. > > But Mark has absolutely no formal connection with the project, and his > contributions have only been to file a couple of JIRA (all of which have so > far been ignored by those of his colleagues who *are* active community > members, I'll note!). Shaming him for not linking docs that describe > something *other* than what he was even talking about is crossing the > line IMO. > > Linking to third-party resources is commonplace, the only difference I can > see here is that these have been called "docs" by the authors, instead of > a blog post, and Mark has a DataStax email address. > > Would you have reacted this way if Aaron Morton linked a blog post by > thelastpickle? Or a random user posted their own resources? Obviously not. > > I was initially all for the ASF endeavour to counteract DataStax' outsized > influence on the project, and was hopeful you might achieve some positive > change. Perhaps you may well still do. But it seems to me that the ASF > behaviour is beginning to cross from constructive criticism of the project > participants to prejudicially hostile behaviour against certain community > members - and that is unlikely to result in a better project. > > You should be treating everyone consistently, in a manner that promotes > project health. > > > > On Friday, 9 September 2016, Mark Thomas <ma...@apache.org> wrote: > >> On 09/09/2016 16:46, Mark Curtis wrote: >> > If your partition sizes are over 100MB iirc then you'll normally see >> > warnings in your system.log, this will outline the partition key, at >> > least in Cassandra 2.0 and 2.1 as I recall. >> > >> > Your best friend here is nodetool cfstats which shows you the >> > min/mean/max partition sizes for your table. It's quite often used to >> > pinpoint large partitons on nodes in a cluster. >> > >> > More info >> > here: >> https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsCFstats.html >> >> Folks, >> >> It is *Apache* Cassandra. If you are going to point to docs, please >> point to the official Apache docs unless there is a very good reason not >> to. >> >> In this case: >> >> >> http://cassandra.apache.org/doc/latest/configuration/cassandra_config_file.html#compaction_large_partition_warning_threshold_mb >> >> looks to the place. >> >> Mark >> >> >> > >> > Thanks >> > >> > Mark >> > >> > >> > On 9 September 2016 at 02:53, Anshu Vajpayee <anshu.vajpa...@gmail.com >> > <mailto:anshu.vajpa...@gmail.com>> wrote: >> > >> > Is there any way to get partition size for a partition key ? >> > >> > >> >>