You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/02 17:20:00 UTC
[jira] [Updated] (HDDS-878) Do the disk failure check before
ContainerSet initialization
[ https://issues.apache.org/jira/browse/HDDS-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-878:
-------------------------------
Target Version/s: 0.7.0 (was: 0.5.0)
> Do the disk failure check before ContainerSet initialization
> ------------------------------------------------------------
>
> Key: HDDS-878
> URL: https://issues.apache.org/jira/browse/HDDS-878
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Yiqun Lin
> Assignee: Yiqun Lin
> Priority: Major
>
> OzoneContainer won't handle any disk failures before initializing the ContainerSet. In a very extreme case, all the disk are bad and the OzoneContainer can still be running. We can improve this and add disk failure tolerance, like DataNode already did.
> {code:java}
> private void buildContainerSet() {
> Iterator<HddsVolume> volumeSetIterator = volumeSet.getVolumesList()
> .iterator();
> ArrayList<Thread> volumeThreads = new ArrayList<Thread>();
> //TODO: diskchecker should be run before this, to see how disks are.
> // And also handle disk failure tolerance need to be added
> while (volumeSetIterator.hasNext()) {
> HddsVolume volume = volumeSetIterator.next();
> Thread thread = new Thread(new ContainerReader(volumeSet, volume,
> containerSet, config));
> thread.start();
> volumeThreads.add(thread);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org