Skip to content

feat: add debug log output for shard open errors#1245

Merged
janl merged 2 commits intoapache:masterfrom
janl:feat/no-db-shard-errors
Mar 28, 2018
Merged

feat: add debug log output for shard open errors#1245
janl merged 2 commits intoapache:masterfrom
janl:feat/no-db-shard-errors

Conversation

@janl
Copy link
Copy Markdown
Member

@janl janl commented Mar 27, 2018

We have a number of issue reports that show “No DB shards could be opened” which we are stuck in resolving, because we don’t know why db shards can’t be opened. This PR aims to add debug logging for when shards can’t be opened.

@janl janl requested review from davisp, nickva, rnewson and wohali March 27, 2018 14:42
@janl janl added this to the 2.2.0 milestone Mar 27, 2018
@wohali
Copy link
Copy Markdown
Member

wohali commented Mar 27, 2018

This is extra logging at debug level, the No DB shards could be opened error stays, if I'm reading this right. If we don't have any deeper insight, this is reasonable. Would like to hear from someone else before +1.

@janl janl merged commit fe1ce42 into apache:master Mar 28, 2018
@janl janl deleted the feat/no-db-shard-errors branch March 28, 2018 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants