Daijiro Fukuda

Thanks for summarizing this issue! I'm willing to consider this issue in December. Here are my impressions at present. > It is also hard to tell which chunks was corrupted...

I am examining this issue. The most important thing is to detect file corruption at abnormal system termination, such as a machine power failure. To handle this, we should improve...

I have created some PRs for this issue. * Add logs to identify the time period of potentially broken data * #4027 * #4028 * Backup a broken chunk file...

> I have created some PRs for this issue. All PRs are merged, thanks for the reviews! I will add documents and a release note about #4025 soon. > About...

Added documentation. * https://github.com/fluent/fluentd-docs-gitbook/pull/448 The following feature would be helpful, but I will not be able to work on it for a while. > About adding more checks for buffer...

> Not sure it's possible but if we could add checksums for the buffer contents, it would be helpful to verify the correctness of the buffers. This is already implemented...

Thanks for summarizing this issue! I agree.

We will vote on the new rules with the current rules. For the new rules, the followings are currently assumed. * No objection ballot * At least effective 3-organization affirmative...

> "effective 3-person affirmative vote" with a shorter voting period can't solve "Hey, I forgot to vote for a objection, but voting period is over and the proposal was accepted...

Summarizing the opinions so far, how about the following rule? * No objection ballot * At least effective **3-person** affirmative vote * At least effective **2-organization** affirmative vote * Effective...