[SENTRY-1486] Sentry should use repeatable-read consistency level

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0, 2.0.0
• Fix Version/s: 1.8.0
• Component/s: Sentry
• Assignee: Alex Kolbasov
• Reporter: Alex Kolbasov
• Created: 03/Oct/16 22:21
• Updated: 24/Jul/17 14:44
• Resolved: 06/Oct/16 23:48

Description

Currently Sentry uses the "read-committed" consistency level which is the default for the Datanucleus JDO library. This causes potential problems since the state visible to each transaction can actually see updates from another transactions, so it is very difficult to reason about any code that reads multiple pieces of data.

Instead it should use repeatable read" consistency which guarantees that any transaction only sees the state at the beginning of a transaction plus any updates done within a transaction.

Issue Links

• blocks: SENTRY-872 Uber jira for HMS HA + Sentry HA redesign
• breaks: SENTRY-1534 Oracle supports serializable instead of repeatable-read
• is related to: SENTRY-1493 Evaluate performance impact of using repeatable-read vs read-committed for Sentry