Verify valid state after updating spatial index #208

Merged
merged 2 commits into from Feb 14, 2017

Projects

None yet

2 participants

@nathansobo
Contributor

⚠️ In order for this to work on 1.14-releases, we'll need to cherry-pick atom/atom@2ad6f83 to that branch. ⚠️

We're seeing some rare exceptions in production that seemed to be caused by the spatial index getting into an invalid state, where it implies the existence of rows beyond the end of the last buffer row. This carries a cost but we want to find out if and when this is happening in production.

/cc @maxbrunsfeld

nathansobo and others added some commits Feb 13, 2017
@nathansobo nathansobo Verify valid state after updating spatial index
We're seeing some rare exceptions in production that seemed to be caused
by the spatial index getting into an invalid state, where it implies the
existence of rows beyond the end of the last buffer row. This carries a
cost but we want to find out if and when this is happening in
production.
dac8c8b
@maxbrunsfeld maxbrunsfeld Remove trailing comma
2cde398
@maxbrunsfeld maxbrunsfeld merged commit ed6af15 into master Feb 14, 2017

3 checks passed

continuous-integration/appveyor/branch AppVeyor build succeeded
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@maxbrunsfeld maxbrunsfeld deleted the ns-mb-investigate-exceptions branch Feb 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment