Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 19 Feb 2016 11:04:18 +0000 (UTC)
From: "Maximilian Michels (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12940469.1455879834000.92571.1455879858111@Atlassian.JIRA>
In-Reply-To: <JIRA.12940469.1455879834000@Atlassian.JIRA>
References: <JIRA.12940469.1455879834000@Atlassian.JIRA>
 <JIRA.12940469.1455879834963@arcas>
Subject: [jira] [Created] (FLINK-3448) Move initialization of handlers to
 start() method
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Maximilian Michels created FLINK-3448:
-----------------------------------------

             Summary: Move initialization of handlers to start() method
                 Key: FLINK-3448
                 URL: https://issues.apache.org/jira/browse/FLINK-3448
             Project: Flink
          Issue Type: Bug
          Components: Webfrontend
    Affects Versions: 1.0.0
            Reporter: Maximilian Michels
            Assignee: Maximilian Michels
            Priority: Minor
             Fix For: 1.0.0


HTTP handlers are initialized upon instance creation of {{WebRuntimeMonitor}}. However, this is useless because the initialization is not completed until the start(jobManager) method is called. In the meantime, user gets messages about ongoing leader elections from the webfrontend.

I would suggest to move the starting code in the constructor to the start(jobManager) method.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)