Around 1TB
On Sat, Sep 5, 2020 at 9:45 AM Aakash Pandhi
wrote:
> How much data to restore and repair on that node?
>
> Sincerely,
>
> Aakash Pandhi
>
>
> On Friday, September 4, 2020, 11:08:56 PM CDT, manish khandelwal <
> manishkhandelwa...@gmail.com> wrote:
>
>
> 3.11.2 to 2.1.16
>
> On Sat,
How much data to restore and repair on that node?
Sincerely,
Aakash Pandhi
On Friday, September 4, 2020, 11:08:56 PM CDT, manish khandelwal
wrote:
3.11.2 to 2.1.16
On Sat, Sep 5, 2020 at 9:27 AM Surbhi Gupta wrote:
Hi Manish,
Please provide both versions.
Thanks Surbhi
On Fri,
3.11.2 to 2.1.16
On Sat, Sep 5, 2020 at 9:27 AM Surbhi Gupta
wrote:
> Hi Manish,
>
> Please provide both versions.
>
> Thanks
> Surbhi
>
> On Fri, Sep 4, 2020 at 8:55 PM manish khandelwal <
> manishkhandelwa...@gmail.com> wrote:
>
>> Hi
>>
>> We have been forced into rolling back our Cassandra
Hi Manish,
Please provide both versions.
Thanks
Surbhi
On Fri, Sep 4, 2020 at 8:55 PM manish khandelwal <
manishkhandelwa...@gmail.com> wrote:
> Hi
>
> We have been forced into rolling back our Cassandra after 1 node upgrade.
> The node was upgraded 10 days ago. We have the backup of the old
Hi
We have been forced into rolling back our Cassandra after 1 node upgrade.
The node was upgraded 10 days ago. We have the backup of the old data.
Strategy one which we are thinking :
1. Rollback to old binaries and configuration.
2. Restore the old data from backup.
3. Run Repair.
Another
As someone else pointed out it’s the same number of tombstones. Doing distinct
queries gives you a bit more flexibility to retry it one fails, but multiple in
one command avoids some contention on the memtable partition objects.
If you’re happen to be using type1 uuids (timeuuid) AND you’re
>
> Would there be a difference (in terms of generated tombstones) if I would
>
> a) issue delete one-by-one like
> DELETE FROM ... WHERE ... uuid = 'a'
> DELETE FROM ... WHERE ... uuid = 'b'
> ...
> DELETE FROM ... WHERE ... uuid = 'z'
>
> or
>
> b) issue delete in a group fashion like
> DELETE
Hi C* gurus,
I'm looking for the best strategy to delete records from a "wide" table.
"wide" means the table stores records which have a UUID-style id element
of the key - within each partition
So yes, its not the partitioning key... The partitioning key is actually
kind of a customerId at
