Skip to content

fix possible 'Null storage adapter found' when segments are swapped#2981

Closed
xvrl wants to merge 1 commit intoapache:masterfrom
metamx:fix-null-storage-adapter
Closed

fix possible 'Null storage adapter found' when segments are swapped#2981
xvrl wants to merge 1 commit intoapache:masterfrom
metamx:fix-null-storage-adapter

Conversation

@xvrl
Copy link
Copy Markdown
Member

@xvrl xvrl commented May 18, 2016

It was possible for a query to get a closed adapter before the new one was put in place.

@xvrl xvrl added the Bug label May 18, 2016
@xvrl xvrl added this to the 0.9.1 milestone May 18, 2016
@gianm
Copy link
Copy Markdown
Contributor

gianm commented May 18, 2016

@xvrl the old code doesn't look buggy to me; queries get Segments from getAndIncrementSegment which is synchronized with swapSegment. If a query had got the Segment, then the "close" in swapSegment will just decrement the refcount, not actually close the segment.

@gianm
Copy link
Copy Markdown
Contributor

gianm commented May 18, 2016

do you have a stack trace of the error you're seeing?

@xvrl
Copy link
Copy Markdown
Member Author

xvrl commented May 18, 2016

my bad, this issue was already fixed in #2301 and was just looking at some old logs

@xvrl xvrl closed this May 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants