flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3678) Make Flink logs directory configurable
Date Tue, 29 Mar 2016 17:28:25 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216397#comment-15216397
] 

ASF GitHub Bot commented on FLINK-3678:
---------------------------------------

GitHub user stefanobaghino opened a pull request:

    https://github.com/apache/flink/pull/1837

    [FLINK-3678] Make Flink logs directory configurable

    * Edit config.sh
    * Document the newly defined log directory configuration key

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/radicalbit/flink 3678

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1837.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 #1837
    
----
commit 05002c01345425d6fe9814ea7f669630fa5514b3
Author: Stefano Baghino <stefano.baghino@radicalbit.io>
Date:   2016-03-29T17:10:46Z

    [FLINK-3678] Make Flink logs directory configurable
    
    * Edit config.sh
    * Document the newly defined log directory configuration key

----


> Make Flink logs directory configurable
> --------------------------------------
>
>                 Key: FLINK-3678
>                 URL: https://issues.apache.org/jira/browse/FLINK-3678
>             Project: Flink
>          Issue Type: Improvement
>          Components: Start-Stop Scripts
>    Affects Versions: 1.0.0
>            Reporter: Stefano Baghino
>            Assignee: Stefano Baghino
>            Priority: Minor
>             Fix For: 1.0.1
>
>
> Currently Flink logs are stored under {{$FLINK_HOME/log}} and the user cannot configure
an alternative storage location. It would be nice to add a configuration key in the {{flink-conf.yaml}}
and edit the {{bin/flink}} launch script accordingly to get the value if present or default
to the current behavior if no value is provided.



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

Mime
View raw message