[ 
https://issues.apache.org/jira/browse/KAFKA-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408605#comment-16408605
 ] 

ASF GitHub Bot commented on KAFKA-6697:
---------------------------------------

lindong28 opened a new pull request #4752: KAFKA-6697; JBOD configured broker 
should not die if log directory is invalid
URL: https://github.com/apache/kafka/pull/4752
 
 
   Currently JBOD configured broker will still die on startup if 
dir.getCanonicalPath() throws IOException. We should mark such log directory as 
offline and broker should still run if there is good disk.
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> JBOD configured broker should not die if log directory is invalid
> -----------------------------------------------------------------
>
>                 Key: KAFKA-6697
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6697
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Dong Lin
>            Assignee: Dong Lin
>            Priority: Major
>
> Currently JBOD configured broker will still die on startup if 
> dir.getCanonicalPath() throws IOException. We should mark such log directory 
> as offline and broker should still run if there is good disk.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to