Re: Incorrect progress percentage while repairing

Forgot to add the C* version. That would be 3.0.6. Regards, Stefano Ortolani On Thu, Jun 2, 2016 at 3:55 PM, Stefano Ortolani wrote: > Hi, > > While running incremental (parallel) repairs on the first partition range > (-pr), I rarely see the progress percentage going over

Re: Library/utility announcements?

On Wed, Jun 1, 2016 at 6:48 PM, James Carman wrote: > Some user lists allow it. Does the Cassandra community mind folks announcing > their super cool Cassandra libraries on this list? I think it's probably OK; People do occasionally announce such things here. > Is

Incorrect progress percentage while repairing

Hi, While running incremental (parallel) repairs on the first partition range (-pr), I rarely see the progress percentage going over 20%/25%. 2016-06-02 14:12:23,207] Repair session cceae4c0-28b0-11e6-86d1-0550db2f124e for range [(8861148493126800521,8883879502599079650]] finished (progress:

Re: Internal Handling of Map Updates

If it's overwrites and append only with no removes, an UPDATE will let you do that to standard collections. Like INSERT, UPDATE acts like an UPSERT. On Thu, Jun 2, 2016, 12:52 AM Matthias Niehoff < matthias.nieh...@codecentric.de> wrote: > JSON would be an option, yes. A frozen collection would

Re: Error while rebuilding a node: Stream failed

I gave up completely with rebuild. Now I am running `nodetool repair` and in case of network issues I retry for the token ranges that failed using the -st and -et options of `nodetool repair`. That would be good enough for now, till we fix our network problems. On Sat, May 28, 2016 at 7:05 PM,

Upgredesstables doing 4K reads

Hi, I've got a 6 node C* cluster (all nodes are equal both in OS and HW setup, they are DL380 Gen9 with Smart Array RAID 50,3 on SAS 15K HDDs) which has been recently updated from 2.2.5 to 3.5. As part of the update I've done the upgradesstables. On 4 nodes the average request size issued to the

Re: (Full) compaction does not delete (all) old files

Hi Dongfeng, 3: Restarting the code does NOT remove those files. I stopped and restarted > C* many times and it did nothing. Finally, my solution was to manually delete those old files. I actually > deleted them while C* is running and did not see any errors/warnings in > system.log. My guess is

Re: Internal Handling of Map Updates

JSON would be an option, yes. A frozen collection would not work for us, as the updates are both overwrites of existing values and appends of new values (but never a remove of values). So we end up with 3 options: 1. use clustering columns 2. use json 3. save the row not using the