Details

    • Type: Sub-task Sub-task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: namenode
    • Labels:
      None

      Description

      Separate the BM from NN by running it with with its own thread-pool and RPC protocol but still in the same process as NN.
      NN and BM will in interact through some loopback call that will simulate a separate service.
      This sprint still assumes a one to one relation between NN and BM and does not split the BM to a separate process, only simulates such a split inside the same VM. This allows us to defer any configuration issue / Testing support / scripts changes to later tasks.
      This task will therefore also not handle any HA issue to the BM itself. It will, however, deal with having BM code actually running in a different thread to the NN code and will handle building the initialisation / lifecycle code to an independent BM.

        Activity

        Hide
        Amir Langer added a comment -

        BM = Block Manager

        Show
        Amir Langer added a comment - BM = Block Manager
        Hide
        jay vyas added a comment -

        Sorry to ask, but... whats "BM" ? Is that the BackupNameNode?

        Show
        jay vyas added a comment - Sorry to ask, but... whats "BM" ? Is that the BackupNameNode?

          People

          • Assignee:
            Unassigned
            Reporter:
            Amir Langer
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development