Flume
  1. Flume
  2. FLUME-481

Unmapping a logic node leaves node in node status list

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: v0.9.4
    • Fix Version/s: v0.9.5
    • Component/s: Master
    • Labels:
      None

      Description

      If you unmap a logic node it remains in the master node status list until the master is restarted. Without looking at code I'd imagine this may be partially related to FLUME-108/FLUME-150.

      I think it should eather remove right away, or after a delayed time. However it should always remove from 1 master if it shows up on another.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Blocked Blocked
        19d 16h 55m 1 09/Feb/11 10:08
        Blocked Blocked Open Open
        103d 13h 27m 1 Jonathan Hsieh 24/May/11 00:35
        Open Open Resolved Resolved
        288d 11h 48m 1 Alexander Alten-Lorenz 07/Mar/12 11:24
        Resolved Resolved Reopened Reopened
        7h 26m 1 Alexander Alten-Lorenz 07/Mar/12 18:50
        Reopened Reopened Resolved Resolved
        972d 14h 36m 1 Ashish Paliwal 05/Nov/14 09:26
        Ashish Paliwal made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Won't Fix [ 2 ]
        Hide
        Ashish Paliwal added a comment -

        Won't fix. 0.X branch not maintained anymore

        Show
        Ashish Paliwal added a comment - Won't fix. 0.X branch not maintained anymore
        Alexander Alten-Lorenz made changes -
        Resolution Won't Fix [ 2 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Hide
        Arvind Prabhakar added a comment -

        @Steve - I think this is a mistake. I am looking into further details regarding this and other Jiras that got closed and will get back soon on it.

        Show
        Arvind Prabhakar added a comment - @Steve - I think this is a mistake. I am looking into further details regarding this and other Jiras that got closed and will get back soon on it.
        Hide
        Steve Hoffman added a comment -

        After 7 months of being open, can we get a little context around the "won't fix"? Is this because of flume-ng and flume original's multi-master being abandoned?

        Show
        Steve Hoffman added a comment - After 7 months of being open, can we get a little context around the "won't fix"? Is this because of flume-ng and flume original's multi-master being abandoned?
        Alexander Alten-Lorenz made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Won't Fix [ 2 ]
        Arvind Prabhakar made changes -
        Affects Version/s v0.9.4 [ 12317557 ]
        Hide
        Steve Hoffman added a comment - - edited

        I have found that the purge command removes the node from the first table (node status), but the entry in the 3rd table remains (Physical/Logical Node mapping).
        I have not found a way to remove an old node from this list even though it has been unconfig/unmap/decommission/and purged.

        I don't know if it matters that the physical & logical names are the same, but they are in my case if that helps. Also still on CDH3u0.

        Show
        Steve Hoffman added a comment - - edited I have found that the purge command removes the node from the first table (node status), but the entry in the 3rd table remains (Physical/Logical Node mapping). I have not found a way to remove an old node from this list even though it has been unconfig/unmap/decommission/and purged. I don't know if it matters that the physical & logical names are the same, but they are in my case if that helps. Also still on CDH3u0.
        Mark Thomas made changes -
        Project Import Tue Aug 02 16:57:12 UTC 2011 [ 1312304232406 ]
        Jonathan Hsieh made changes -
        Fix Version/s v0.9.4 [ 10050 ]
        Fix Version/s v0.9.5 [ 10090 ]
        Jonathan Hsieh made changes -
        Status Patch Available [ 10000 ] Open [ 1 ]
        Hide
        Jonathan Hsieh added a comment -

        It does not broadcast to all masters. I'm currently considering a new version of the master that properly supports multi-master completely across all aspects, where that problem would get specifically addressed.

        Show
        Jonathan Hsieh added a comment - It does not broadcast to all masters. I'm currently considering a new version of the master that properly supports multi-master completely across all aspects, where that problem would get specifically addressed.
        Jonathan Hsieh made changes -
        Fix Version/s v0.9.4 [ 10050 ]
        Anonymous made changes -
        Field Original Value New Value
        Status Open [ 1 ] Patch Available [ 10000 ]
        Hide
        Nicholas Verbeck added a comment -

        That may work for now. Does this broadcast to all masters or just the connected master? What is the idea behind keeping these noncommissioned node around in the status list anyway? As well as could we not extend the unmap command to clear a node from the status list when ran? Since most likely when you remap it it will appear on a different master.

        Show
        Nicholas Verbeck added a comment - That may work for now. Does this broadcast to all masters or just the connected master? What is the idea behind keeping these noncommissioned node around in the status list anyway? As well as could we not extend the unmap command to clear a node from the status list when ran? Since most likely when you remap it it will appear on a different master.
        Hide
        Jonathan Hsieh added a comment -

        There is the 'purge' command implemented in FLUME-240, that removes all the node statuses and waits for a refresh.

        Is this sufficient?

        Show
        Jonathan Hsieh added a comment - There is the 'purge' command implemented in FLUME-240 , that removes all the node statuses and waits for a refresh. Is this sufficient?
        Nicholas Verbeck created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Nicholas Verbeck
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development