question

rajib76 avatar image
rajib76 asked rajib76 commented

DSBulk returns "Unable to perform authorization of permissions: Operation timed out - received only 0 responses"

I am getting an error with DSBULK after loading of some rows. It says Unable to perform authorization of permissions: Operation timed out - received only 0 responses

Below is the error I am getting. I am not using the default Cassandra user. I have created a separate role without super user access.

5,700,936 | 0 | 81,375 | 14.78 | 149.95 | 327.16 | 13.16

total | failed | rows/s | p50ms | p99ms | p999ms | batches

6,137,178 | 0 | 81,768 | 14.80 | 149.95 | 327.16 | 13.05

total | failed | rows/s | p50ms | p99ms | p999ms | batches

6,521,416 | 0 | 81,460 | 15.13 | 158.33 | 331.35 | 13.32

total | failed | rows/s | p50ms | p99ms | p999ms | batches

6,727,752 | 0 | 79,080 | 15.39 | 164.63 | 341.84 | 13.48

Operation LOAD_20220131-221122-030207 failed: Unable to perform authorization of permissions: Operation timed out - received only 0 responses.

I have checked the system_auth table also, it has 3 replication factor

dsbulk
10 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered rajib76 commented

This error indicates that the replicas were unresponsive (received only 0 responses) so the authentication operation timed out.

This error is just a symptom of another problem. My guess is that your cluster is overloaded and cannot keep up with the writes from the load.

If you are loading data to your own cluster, I'd recommend adding more nodes to increase the capacity of your cluster. The alternative is to reduce the size of your bulk loads to just 50K records at a time and leave a few minutes pause between loads to allow the cluster to recover and stabilise from the overload. Cheers!

1 comment Share
10 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

rajib76 avatar image rajib76 commented ·
Thanks Erick, I just truncated the table and ran the DSBULK. It ran fine now. I think the problem was that I was running DSBULK multiple times on the table. It created lot of tombstones and SSTABLEs and that caused the overload. My understanding is that when I truncated the table, it removed the tombstones and the SSTABLES immediately.
0 Likes 0 ·