FAQ
Namespace recovery from the secondary image should be documented.
-----------------------------------------------------------------

Key: HADOOP-3541
URL: https://issues.apache.org/jira/browse/HADOOP-3541
Project: Hadoop Core
Issue Type: Task
Components: dfs, documentation
Affects Versions: 0.18.0
Reporter: Konstantin Shvachko
Assignee: Konstantin Shvachko
Priority: Blocker
Fix For: 0.18.0


HADOOP-2585 introduced a new feature which lets starting name-node from an image stored on the secondary node.
This need to be documented in "HDFS Admin Guide".

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

  • Konstantin Shvachko (JIRA) at Jun 24, 2008 at 3:18 am
    [ https://issues.apache.org/jira/browse/HADOOP-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Konstantin Shvachko updated HADOOP-3541:
    ----------------------------------------

    Attachment: SecondaryDoc.patch

    Here is the documentation.
    Namespace recovery from the secondary image should be documented.
    -----------------------------------------------------------------

    Key: HADOOP-3541
    URL: https://issues.apache.org/jira/browse/HADOOP-3541
    Project: Hadoop Core
    Issue Type: Task
    Components: dfs, documentation
    Affects Versions: 0.18.0
    Reporter: Konstantin Shvachko
    Assignee: Konstantin Shvachko
    Priority: Blocker
    Fix For: 0.18.0

    Attachments: SecondaryDoc.patch


    HADOOP-2585 introduced a new feature which lets starting name-node from an image stored on the secondary node.
    This need to be documented in "HDFS Admin Guide".
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Lohit Vijayarenu (JIRA) at Jun 24, 2008 at 3:51 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607658#action_12607658 ]

    Lohit Vijayarenu commented on HADOOP-3541:
    ------------------------------------------

    +1 Looks good
    - Can we describe <i>create an empty storage directory</i>, to be more explicit saying we should not have name/current directory
    - Would it be good idea to document about <i>fs.checkpoint.period</i> and <i>fs.checkpoint.size</i>.

    PS: Shouldnt the patch contain only .xml file changes?
    Namespace recovery from the secondary image should be documented.
    -----------------------------------------------------------------

    Key: HADOOP-3541
    URL: https://issues.apache.org/jira/browse/HADOOP-3541
    Project: Hadoop Core
    Issue Type: Task
    Components: dfs, documentation
    Affects Versions: 0.18.0
    Reporter: Konstantin Shvachko
    Assignee: Konstantin Shvachko
    Priority: Blocker
    Fix For: 0.18.0

    Attachments: SecondaryDoc.patch


    HADOOP-2585 introduced a new feature which lets starting name-node from an image stored on the secondary node.
    This need to be documented in "HDFS Admin Guide".
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Lohit Vijayarenu (JIRA) at Jun 24, 2008 at 4:21 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607658#action_12607658 ]

    lohit edited comment on HADOOP-3541 at 6/24/08 9:19 AM:
    -------------------------------------------------------------------

    +1 Looks good
    - Can we describe _create an empty storage directory_, to be more explicit saying we should not have name/current directory
    - Would it be good idea to document about _fs.checkpoint.period_ and _fs.checkpoint.size_.

    PS: Shouldnt the patch contain only .xml file changes?

    was (Author: lohit):
    +1 Looks good
    - Can we describe <i>create an empty storage directory</i>, to be more explicit saying we should not have name/current directory
    - Would it be good idea to document about <i>fs.checkpoint.period</i> and <i>fs.checkpoint.size</i>.

    PS: Shouldnt the patch contain only .xml file changes?
    Namespace recovery from the secondary image should be documented.
    -----------------------------------------------------------------

    Key: HADOOP-3541
    URL: https://issues.apache.org/jira/browse/HADOOP-3541
    Project: Hadoop Core
    Issue Type: Task
    Components: dfs, documentation
    Affects Versions: 0.18.0
    Reporter: Konstantin Shvachko
    Assignee: Konstantin Shvachko
    Priority: Blocker
    Fix For: 0.18.0

    Attachments: SecondaryDoc.patch


    HADOOP-2585 introduced a new feature which lets starting name-node from an image stored on the secondary node.
    This need to be documented in "HDFS Admin Guide".
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Konstantin Shvachko (JIRA) at Jun 24, 2008 at 11:01 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Konstantin Shvachko updated HADOOP-3541:
    ----------------------------------------

    Attachment: SecondaryDoc.patch

    It is a good idea to document fs.checkpoint.period and .size properties. I did that.
    By saying "create empty directory" I actually mean creating an empty directory that is the one that does not
    contain anything inside. Don' know how to clarify it better.
    Yes you are right that the implementation checks only that the directory does not contain a legal image,
    but I think the documentation should say empty directory, that way there will be no confusion if we ever
    change any thing in the internal directory structure.
    I thought we commit xml files as well as the generated by forrest html and pdf files. So my patch contains all three.
    Please let me know if this is wrong.
    Namespace recovery from the secondary image should be documented.
    -----------------------------------------------------------------

    Key: HADOOP-3541
    URL: https://issues.apache.org/jira/browse/HADOOP-3541
    Project: Hadoop Core
    Issue Type: Task
    Components: dfs, documentation
    Affects Versions: 0.18.0
    Reporter: Konstantin Shvachko
    Assignee: Konstantin Shvachko
    Priority: Blocker
    Fix For: 0.18.0

    Attachments: SecondaryDoc.patch, SecondaryDoc.patch


    HADOOP-2585 introduced a new feature which lets starting name-node from an image stored on the secondary node.
    This need to be documented in "HDFS Admin Guide".
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Lohit Vijayarenu (JIRA) at Jun 24, 2008 at 11:20 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Lohit Vijayarenu updated HADOOP-3541:
    -------------------------------------

    Hadoop Flags: [Reviewed]

    +1 Looks good.
    Namespace recovery from the secondary image should be documented.
    -----------------------------------------------------------------

    Key: HADOOP-3541
    URL: https://issues.apache.org/jira/browse/HADOOP-3541
    Project: Hadoop Core
    Issue Type: Task
    Components: dfs, documentation
    Affects Versions: 0.18.0
    Reporter: Konstantin Shvachko
    Assignee: Konstantin Shvachko
    Priority: Blocker
    Fix For: 0.18.0

    Attachments: SecondaryDoc.patch, SecondaryDoc.patch


    HADOOP-2585 introduced a new feature which lets starting name-node from an image stored on the secondary node.
    This need to be documented in "HDFS Admin Guide".
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Konstantin Shvachko (JIRA) at Jun 25, 2008 at 12:56 am
    [ https://issues.apache.org/jira/browse/HADOOP-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Konstantin Shvachko resolved HADOOP-3541.
    -----------------------------------------

    Resolution: Fixed

    I just committed this.
    Namespace recovery from the secondary image should be documented.
    -----------------------------------------------------------------

    Key: HADOOP-3541
    URL: https://issues.apache.org/jira/browse/HADOOP-3541
    Project: Hadoop Core
    Issue Type: Task
    Components: dfs, documentation
    Affects Versions: 0.18.0
    Reporter: Konstantin Shvachko
    Assignee: Konstantin Shvachko
    Priority: Blocker
    Fix For: 0.18.0

    Attachments: SecondaryDoc.patch, SecondaryDoc.patch


    HADOOP-2585 introduced a new feature which lets starting name-node from an image stored on the secondary node.
    This need to be documented in "HDFS Admin Guide".
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hudson (JIRA) at Jun 25, 2008 at 12:38 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608020#action_12608020 ]

    Hudson commented on HADOOP-3541:
    --------------------------------

    Integrated in Hadoop-trunk #529 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/529/])
    Namespace recovery from the secondary image should be documented.
    -----------------------------------------------------------------

    Key: HADOOP-3541
    URL: https://issues.apache.org/jira/browse/HADOOP-3541
    Project: Hadoop Core
    Issue Type: Task
    Components: dfs, documentation
    Affects Versions: 0.18.0
    Reporter: Konstantin Shvachko
    Assignee: Konstantin Shvachko
    Priority: Blocker
    Fix For: 0.18.0

    Attachments: SecondaryDoc.patch, SecondaryDoc.patch


    HADOOP-2585 introduced a new feature which lets starting name-node from an image stored on the secondary node.
    This need to be documented in "HDFS Admin Guide".
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedJun 11, '08 at 10:47p
activeJun 25, '08 at 12:38p
posts8
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Hudson (JIRA): 8 posts

People

Translate

site design / logo © 2023 Grokbase