Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1
    • Fix Version/s: future release
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      This is a request for adding a validate-nodes-multicast command. This would be
      a remote command (running in the DAS) that would use the SSH information in SSH
      nodes to start validate-multicast on each node, and then would collect the
      output and give a picture of what the multicast situation is for the entire
      collection of nodes that are defined for the domain.

      For example, if all nodes can communicate with each other via multicast (the
      ideal situation for GMS), the output might be:

      Multicast Groups:
      1: localhost (DAS), n1, n2, n3, n4

      However, if we have only n1<->n2 and n3<->n4 communicating, and the DAS can't
      multicast to any of them, then the output could be:

      Multicast Groups:
      1: n1, n2
      2: n3, n4

      Isolated Nodes:
      localhost (DAS)

      If we had the situation where multicast doesn't work at all, the output could
      be:

      Isolated Nodes:
      localhost (DAS), n1, n2, n3, n4

      This information can currently be derived by running "asadmin validate-
      multicast" on all of the nodes, and then analyzing the output. The idea of this
      command is to automate the running of the command on all the nodes and to
      analyze the output for the user.

        Activity

        Hide
        Bobby Bissett added a comment -

        Moving to Joe since I'm no longer on project.

        Show
        Bobby Bissett added a comment - Moving to Joe since I'm no longer on project.
        Hide
        Bobby Bissett added a comment -

        The command should definitely use the cluster configuration information in domain.xml, such as multicast address/port, or whatever is being used for non-multicast setups. Based on user feedback, the command should also give some warning about settings that are NOT specified in the config. For instance, if no network adapter is specified for a node, the tool should let the user know that it's not specifying one when run.

        Show
        Bobby Bissett added a comment - The command should definitely use the cluster configuration information in domain.xml, such as multicast address/port, or whatever is being used for non-multicast setups. Based on user feedback, the command should also give some warning about settings that are NOT specified in the config. For instance, if no network adapter is specified for a node, the tool should let the user know that it's not specifying one when run.
        Hide
        Joe Fialli added a comment -

        Recommend broadening this command to encompass validate-cluster.

        In GlassFish 3.2, there will exist a mode to enable GMS without UDP multicast.
        It would be helpful if this command could verify GMS discovery based on current cluster configuration,
        independent of whether multicast is enabled or not.

        Show
        Joe Fialli added a comment - Recommend broadening this command to encompass validate-cluster. In GlassFish 3.2, there will exist a mode to enable GMS without UDP multicast. It would be helpful if this command could verify GMS discovery based on current cluster configuration, independent of whether multicast is enabled or not.

          People

          • Assignee:
            Joe Fialli
            Reporter:
            Tom Mueller
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: