Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.6.0
    • Component/s: docs
    • Labels:

      Description

      Given that recovering from a failed namenode in 1.6 could be tricky (see ACCUMULO-1832). I think we should recommend using viewfs:// or HA namenodes in documentation. Using either of these approaches, there would be no need to rewrite uris in Accumulo. Only hadoop config would need to be changed if the namenode is moved.

        Issue Links

          Activity

          Hide
          Josh Elser added a comment -

          Agreed – In the HA Namenode case, you actually wouldn't have to do anything (Accumulo or Hadoop). If you haven't configured Accumulo otherwise with instance.dfs.uri, you'll automatically get the nameservice URI, which means you don't have to do anything if a namenode fails over.

          Show
          Josh Elser added a comment - Agreed – In the HA Namenode case, you actually wouldn't have to do anything (Accumulo or Hadoop). If you haven't configured Accumulo otherwise with instance.dfs.uri, you'll automatically get the nameservice URI, which means you don't have to do anything if a namenode fails over.
          Hide
          Mike Drob added a comment -

          Is this a documentation issue?

          Show
          Mike Drob added a comment - Is this a documentation issue?
          Hide
          Josh Elser added a comment -

          It does say documentation in the desc – not sure if Keith was thinking about anything else too.

          Show
          Josh Elser added a comment - It does say documentation in the desc – not sure if Keith was thinking about anything else too.
          Hide
          Mike Drob added a comment -

          Yea, I was just confused by components being tserver/master, which make me think there is code change.

          Show
          Mike Drob added a comment - Yea, I was just confused by components being tserver/master, which make me think there is code change.
          Hide
          Keith Turner added a comment -

          Interesting, I suspect it inherited the components from the parent ticket. I look at some of the other sub task and they all had the same components as the parent.

          Show
          Keith Turner added a comment - Interesting, I suspect it inherited the components from the parent ticket. I look at some of the other sub task and they all had the same components as the parent.
          Hide
          Mike Drob added a comment -

          Looks like this documentation was added to the user manual in commit 2ef2d88.

          Show
          Mike Drob added a comment - Looks like this documentation was added to the user manual in commit 2ef2d88 .
          Hide
          Keith Turner added a comment -

          oh yeah, I meant to ref this ticket in the commit msg but forgot to

          Show
          Keith Turner added a comment - oh yeah, I meant to ref this ticket in the commit msg but forgot to

            People

            • Assignee:
              Keith Turner
              Reporter:
              Keith Turner
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development