Set entry fails under high volume of commits

[anomit]

[...]
2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}

2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}

2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}

2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}

2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}

2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}

2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}

2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}

2020-11-23 17:01:50,957 - skydb.skydb_utils - DEBUG - {"message":"Unable to update the registry: [provided revision number is invalid; registry update failed due reach sufficient redundancy]"}


Exception:
			The Registry Data was Invalid. Please do recheck that
			- you are not using the same revision number to update the data.
			- make sure that the keys used to sign the message come from the same seed value.

The above messages were repeated many number of times.

1. Possibly a lot of retries on writes causing the portal to lock up. Is there a way to utilize tenacity for better backoffs if that is the case?
2. Let a library consumer know with proper responses about this error.