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

ASF GitHub Bot commented on APEXCORE-563:
-----------------------------------------

GitHub user DT-Priyanka opened a pull request:

    https://github.com/apache/apex-core/pull/432

    APEXCORE-563: Add log filename and offset to the container/operator e…

    …rror events

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

    $ git pull https://github.com/DT-Priyanka/incubator-apex-core 
APEXCORE-563-event-log-update

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

    https://github.com/apache/apex-core/pull/432.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 #432
    
----
commit 3d2f48f6aca65f99a2a427154af23dbbc5b0ae5d
Author: Priyanka Gugale <[email protected]>
Date:   2016-12-13T11:52:47Z

    APEXCORE-563: Add log filename and offset to the container/operator error 
events

----


> Have a pointer to container log file name and offset in stram events that 
> deliver a container or operator failure event.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: APEXCORE-563
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-563
>             Project: Apache Apex Core
>          Issue Type: New Feature
>            Reporter: Sanjay M Pujare
>            Assignee: Priyanka Gugale
>
> The default DailyRollingFileAppender does not take into account of how many 
> backup files to keep and it will result in unbounded growth of log files, 
> especially for long running applications.
> The below is an interesting add-on to the default DailyRollingFileAppender 
> that supports maxBackupIndex.
> http://wiki.apache.org/logging-log4j/DailyRollingFileAppender



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

Reply via email to