Stream ordering and out of order insertions.
Handle the fact that events can be persisted out of order, and so to get the "current max" stream token becomes non trivial - as we need to make sure that *all* stream tokens less than the current max have also successfully been persisted.
Showing
- synapse/storage/_base.py 3 additions, 43 deletionssynapse/storage/_base.py
- synapse/storage/events.py 7 additions, 2 deletionssynapse/storage/events.py
- synapse/storage/stream.py 3 additions, 20 deletionssynapse/storage/stream.py
- synapse/storage/util/__init__.py 14 additions, 0 deletionssynapse/storage/util/__init__.py
- synapse/storage/util/id_generators.py 126 additions, 0 deletionssynapse/storage/util/id_generators.py
Loading
Please register or sign in to comment