From issues-return-149091-archive-asf-public=cust-asf.ponee.io@flink.apache.org Tue Jan 23 15:30:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 7E2B4180621 for ; Tue, 23 Jan 2018 15:30:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6DF7B160C39; Tue, 23 Jan 2018 14:30:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B2AE0160C17 for ; Tue, 23 Jan 2018 15:30:03 +0100 (CET) Received: (qmail 90073 invoked by uid 500); 23 Jan 2018 14:30:02 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 90064 invoked by uid 99); 23 Jan 2018 14:30:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2018 14:30:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 575C11A0B8B for ; Tue, 23 Jan 2018 14:30:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.711 X-Spam-Level: X-Spam-Status: No, score=-100.711 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id BsovHR4xY7WD for ; Tue, 23 Jan 2018 14:30:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0D7205F1F3 for ; Tue, 23 Jan 2018 14:30:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7121EE01A7 for ; Tue, 23 Jan 2018 14:30:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2CC2720DF3 for ; Tue, 23 Jan 2018 14:30:00 +0000 (UTC) Date: Tue, 23 Jan 2018 14:30:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-8495) Serve main cluster components log and stdout file MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLINK-8495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335832#comment-16335832 ] ASF GitHub Bot commented on FLINK-8495: --------------------------------------- GitHub user tillrohrmann opened a pull request: https://github.com/apache/flink/pull/5341 [FLINK-8495] [flip6] Enable main cluster component's log and stdout file retrieval ## What is the purpose of the change This commit enables the log and stdout file retrieval of the cluster's main component via the web ui. This happens via the StaticFileServerHandler which serves the log and stdout file. ## Verifying this change - Tested manually ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not applicable) You can merge this pull request into a Git repository by running: $ git pull https://github.com/tillrohrmann/flink enableWebLogRetrieval Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/5341.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5341 ---- commit a2672b713917f7ea09242684c0106aaf407cf867 Author: Till Rohrmann Date: 2018-01-23T14:17:16Z [FLINK-8495] [flip6] Enable main cluster component's log and stdout file retrieval This commit enables the log and stdout file retrieval of the cluster's main component via the web ui. This happens via the StaticFileServerHandler which serves the log and stdout file. ---- > Serve main cluster components log and stdout file > ------------------------------------------------- > > Key: FLINK-8495 > URL: https://issues.apache.org/jira/browse/FLINK-8495 > Project: Flink > Issue Type: Sub-task > Components: REST, Webfrontend > Affects Versions: 1.5.0 > Reporter: Till Rohrmann > Assignee: Till Rohrmann > Priority: Major > Labels: flip-6 > Fix For: 1.5.0 > > > The {{WebMonitorEndpoint}} should be able to serve the main cluster components log and stdout file via the web ui. -- This message was sent by Atlassian JIRA (v7.6.3#76005)