Fix potential deadlock in `TieredStorage.flushMemory()`

[juliusv]

AFACIS t.appendToDiskQueue is produced and consumed only from the same goroutine, in sequence, with no capacity checking on the producer side. That looks like the producer could potentially deadlock forever if the channel fills up, because the consumer would only run after it.

[matttproud]

Great catch. There were so many things that changed in that last
simplification round that I could imagine how this would have been
overlooked.
Am 28.05.2013 17:23 schrieb "juliusv" notifications@github.com:

AFACIS t.appendToDiskQueue is produced and consumed only from the same
goroutine, in sequence, with no capacity checking on the producer side.
That looks like the producer could potentially deadlock forever if the
channel fills up, because the consumer would only run after it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/275
.

[juliusv]

The old storage is gone. Closing this.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.