The way how hints work under the hood was improved in C* 3.0.
Please take a look at
http://www.datastax.com/dev/blog/whats-coming-to-cassandra-in-3-0-improved-hint-storage-and-delivery
for further details
On Tue, Sep 20, 2016 at 8:12 AM, Dikang Gu wrote:
> In our 2.1 cluster, I find that hints
In our 2.1 cluster, I find that hints handoff is using a lot of memory on
our proxy nodes, when delivering hints to a data node that was dead for 3+
hours (our hints window is 3 hours). It makes the young gen GC time as long
as 2 secs.
I'm using 64G max heap size, and 4G young gen size. I'm consid
Hi,
I wanted to know if there are any guidelines for contributors to give
out unit and integration tests along with the patches. If not, we should
discuss and have them in place.
I know we are making good progress with test coverage but we should add
guidelines around adding unit and integrati
On Fri, Sep 16, 2016 at 5:05 AM, Sylvain Lebresne wrote:
> In light of all this, my suggesting for a release cycle woud be:
> - To have 3 branches: 'features', 'testing' and 'stable', with an X month
> rotation: 'features' becomes 'testing' after X months and then 'stable'
> after
> X more, be
On Thu, Sep 15, 2016 at 9:33 PM, Mick Semb Wever wrote:
> - keep bimonthly feature releases,
> - revert from tick-tock to SemVer numbering scheme,
> - during the release vote also vote on the quality label (feature branches
> start with a 'Alpha' and the first patch release as 'Beta'),
> - acc
With 11 binding +1, 5 non-binding +1 and no -1 the vote passes. I will
publish.
On Mon, Sep 19, 2016 at 2:19 AM, Tommy Stendahl wrote:
> +1 (non binding)
>
>
>
> On 2016-09-15 20:57, Jake Luciani wrote:
>
>> I propose the following artifacts for release as 3.0.9.
>>
>> sha1: d600f51ee1a3eb7b30ce
