[ https://issues.apache.org/jira/browse/HDFS-11154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chen Liang updated HDFS-11154: ------------------------------ Attachment: HDFS-11154-HDFS-7240.005.patch The v005 patch was somehow checked by Jenkins twice. The first run was fine, all the warnings were unrelated. The second run complained about a number of things but the report links are all dead. So I suspect it hit some Jenkins internal issues in the second run. Upload v005 patch a second time to trigger one more Jenkins check. > Block Storage : store server state to persistent storage > -------------------------------------------------------- > > Key: HDFS-11154 > URL: https://issues.apache.org/jira/browse/HDFS-11154 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs > Reporter: Chen Liang > Assignee: Chen Liang > Attachments: HDFS-11154-HDFS-7240.001.patch, > HDFS-11154-HDFS-7240.002.patch, HDFS-11154-HDFS-7240.003.patch, > HDFS-11154-HDFS-7240.004.patch, HDFS-11154-HDFS-7240.005.patch, > HDFS-11154-HDFS-7240.005.patch > > > Currently, all the storage state are kept in server memory. If server > crashes, we would lose all the volume information. This JIRA stores server > internal state into its local disk. Such that on server failure, we can > simply restart server and restore volume information from disk. > More specifically, the internal state written to disk is mainly the mapping > from volume to its underlying containers, plus some meta information such as > volume size, block size, etc. > Note that this is only a simple, minimum set mechanism for persistence. It is > more like a counterpart of fsimage in HDFS, but without edit logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org