Task drops at consumer level with redis

[yashkumarverma-fampay]

Wanted to double down on a line mentioned in the docs about using redis as task broker.

Redis is also feature-complete, but is more susceptible to data loss in the event of abrupt termination or power failures. Detailed information about using Redis:

We're using redis as a broker in our production, and it has worked fine till now, but have noticed a strange behavior:

• we're using an AWS managed redis instance so it'd not go down abruptly, with django
• we process about 2418980 tasks/hour at our peak traffic.
• out of these, 1/2 tasks are dropped (never picked by consumer).
• the workers always do a warm shutdown, nothing is killed abruptly.

Questions

1. Has someone ever faced this behavior?
2. Is using redis risky (if we avert the power loss failure)
3. Is the warning about redis only because of the fact that redis doesn't have persistence, or there are other reasons as well;?