Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-290

bigdata hup sometimes required on federation restart.

    Details

      Description

      Once the run state of a bigdata federation has been set to 'stop', changing the run state to 'start' does not always cause all services to restart in a timely manner. The workaround for this is to wait two minute (so most services will start) and then change the run state to 'hup' for one minute (so the services managers will rescan zookeeper and reinitialize their service start logic). After one minute at 'hup' the run state can be returned to 'start' or set to 'status'.

        Activity

        Hide
        bryanthompson bryanthompson added a comment -
        Show
        bryanthompson bryanthompson added a comment - This is the same as http://sourceforge.net/apps/trac/bigdata/ticket/111 .
        Hide
        bryanthompson bryanthompson added a comment -

        Resolved by Committed revision 3418.

        This change set implements a workaround for the problem reported by
        https://sourceforge.net/apps/trac/bigdata/ticket/111 and https://sourceforge.net/apps/trac/bigdata/ticket/94. The underlying problem is described in https://sourceforge.net/apps/trac/bigdata/ticket/111 and is a problem in the rules-based service startup logic. The workaround removes the TXRunningConstraint from the configuration files and modifies the StoreManager to wait for the transaction service to be discovered before proceeding with its startup. The changes made by this workaround are appropriate and close out https://sourceforge.net/apps/trac/bigdata/ticket/94, but I am going to leave https://sourceforge.net/apps/trac/bigdata/ticket/111 open since it documents the underlying problem which has not been resolved.

        Show
        bryanthompson bryanthompson added a comment - Resolved by Committed revision 3418. This change set implements a workaround for the problem reported by https://sourceforge.net/apps/trac/bigdata/ticket/111 and https://sourceforge.net/apps/trac/bigdata/ticket/94 . The underlying problem is described in https://sourceforge.net/apps/trac/bigdata/ticket/111 and is a problem in the rules-based service startup logic. The workaround removes the TXRunningConstraint from the configuration files and modifies the StoreManager to wait for the transaction service to be discovered before proceeding with its startup. The changes made by this workaround are appropriate and close out https://sourceforge.net/apps/trac/bigdata/ticket/94 , but I am going to leave https://sourceforge.net/apps/trac/bigdata/ticket/111 open since it documents the underlying problem which has not been resolved.

          People

          • Assignee:
            Unassigned
            Reporter:
            bryanthompson bryanthompson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: