Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
2.1.0
-
None
-
None
Description
Transactional reties not needed for failures while persisting MSentryHmsNotification which are because of duplicate key.
There are only inserts that happen on this table. If an insert failed because of duplicate entry, it will likely fail in the subsequent retires. There is no need to retry.
Specially in HA mode when multiple sentry servers can act as leader (split Brian situation) this will cause additional load on the database for no reason.
Attachments
Attachments
Issue Links
- relates to
-
SENTRY-1904 TransactionManager should limit the max time spent by transaction retry
- Patch Available