Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-1362

Management console shows nothing when there are no working nodes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • JDG 7.1.0 GA
    • Management and Monitoring
    • None
    • Hide

      1. Add a management user and start the domain controller by "domain.sh --host-config=host-master.xml ...". Then access to http://localhost:9990/.

      2. Start the next host controller on another host by "domain.sh --host-config=host-slave.xml --master-address=$MASTER ...". Stop one node by CLI (/host=<slave>/server-config=server-one:stop), then access the console.

      Show
      1. Add a management user and start the domain controller by " domain.sh --host-config=host-master.xml ... ". Then access to http://localhost:9990/ . 2. Start the next host controller on another host by " domain.sh --host-config=host-slave.xml --master-address=$MASTER ... ". Stop one node by CLI ( /host=<slave>/server-config=server-one:stop ), then access the console.

      1. When you start the domain controller using host-master.xml, which defines no working nodes, the management console shows a white blank page. A JavaScript error can be found by the browser's developer tool.

      2. Then if you start a slave host controller using host-slave.xml, the console starts working. But the cache container status becomes "DEGRADED" if you stop some nodes. According to ISPN-6394, this is because the status is based on the server-group information. The red label of "DEGRADED" status looks an error but leaving some nodes stopped is a quite common operation and and it shuoldn't look like an error. In addition to that, the wording reminds the degraded mode of partition handling but it seems there is no connection to the feature.

              vblagoje Vladimir Blagojevic (Inactive)
              rhn-support-onagano Osamu Nagano
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: