You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2008/10/16 23:46:46 UTC

[jira] Created: (HADOOP-4434) Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant

Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant
---------------------------------------------------------------------------------------------------------------

                 Key: HADOOP-4434
                 URL: https://issues.apache.org/jira/browse/HADOOP-4434
             Project: Hadoop Core
          Issue Type: Improvement
         Environment: Redhat Enterprise Linux 4.5, Java 6
            Reporter: Eric Yang


- Chukwa Agent does not handle rotated log correctly.  The current design requires the logging process to pause the agent, rotate the log, then resume the log streaming.  The three communication between the running process and chukwa agent could become a problem when either or one of the process is down.  The implementation should be able to detect log rotation in the chukwa agent.
- Chukwa Agent should detect and prevent the same log being streamed more than once.
- Chukwa Agent should synchronize data streaming addition when picking up the check point file.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4434) Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated HADOOP-4434:
------------------------------

    Attachment: HADOOP-4434.patch

- Added returning of adaptor id when processing a command.
- Added test case to make sure adaptor can be started correctly.
- Added test case for Start streaming data in the middle of the file.
- Changed adaptor interface to remember stream name.
- Added logic to check for existing data stream and prevent the same data stream being added twice.
- Increased maximum post size to 2MB.

> Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4434
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4434
>             Project: Hadoop Core
>          Issue Type: Improvement
>         Environment: Redhat Enterprise Linux 4.5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>         Attachments: HADOOP-4434.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> - Chukwa Agent does not handle rotated log correctly.  The current design requires the logging process to pause the agent, rotate the log, then resume the log streaming.  The three communication between the running process and chukwa agent could become a problem when either or one of the process is down.  The implementation should be able to detect log rotation in the chukwa agent.
> - Chukwa Agent should detect and prevent the same log being streamed more than once.
> - Chukwa Agent should synchronize data streaming addition when picking up the check point file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4434) Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant

Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated HADOOP-4434:
----------------------------------

      Resolution: Duplicate
    Hadoop Flags: [Incompatible change, Reviewed]  (was: [Reviewed, Incompatible change])
          Status: Resolved  (was: Patch Available)

Incorporated in HADOOP-4709

> Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4434
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4434
>             Project: Hadoop Core
>          Issue Type: Improvement
>         Environment: Redhat Enterprise Linux 4.5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>         Attachments: HADOOP-4434.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> - Chukwa Agent does not handle rotated log correctly.  The current design requires the logging process to pause the agent, rotate the log, then resume the log streaming.  The three communication between the running process and chukwa agent could become a problem when either or one of the process is down.  The implementation should be able to detect log rotation in the chukwa agent.
> - Chukwa Agent should detect and prevent the same log being streamed more than once.
> - Chukwa Agent should synchronize data streaming addition when picking up the check point file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-4434) Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645442#action_12645442 ] 

Hadoop QA commented on HADOOP-4434:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12393353/HADOOP-4434.patch
  against trunk revision 711734.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 12 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 Eclipse classpath. The patch retains Eclipse classpath integrity.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3540/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3540/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3540/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3540/console

This message is automatically generated.

> Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4434
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4434
>             Project: Hadoop Core
>          Issue Type: Improvement
>         Environment: Redhat Enterprise Linux 4.5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>         Attachments: HADOOP-4434.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> - Chukwa Agent does not handle rotated log correctly.  The current design requires the logging process to pause the agent, rotate the log, then resume the log streaming.  The three communication between the running process and chukwa agent could become a problem when either or one of the process is down.  The implementation should be able to detect log rotation in the chukwa agent.
> - Chukwa Agent should detect and prevent the same log being streamed more than once.
> - Chukwa Agent should synchronize data streaming addition when picking up the check point file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (HADOOP-4434) Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang reassigned HADOOP-4434:
---------------------------------

    Assignee: Eric Yang

> Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4434
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4434
>             Project: Hadoop Core
>          Issue Type: Improvement
>         Environment: Redhat Enterprise Linux 4.5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> - Chukwa Agent does not handle rotated log correctly.  The current design requires the logging process to pause the agent, rotate the log, then resume the log streaming.  The three communication between the running process and chukwa agent could become a problem when either or one of the process is down.  The implementation should be able to detect log rotation in the chukwa agent.
> - Chukwa Agent should detect and prevent the same log being streamed more than once.
> - Chukwa Agent should synchronize data streaming addition when picking up the check point file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-4434) Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated HADOOP-4434:
------------------------------

    Release Note: 
- Added returning of adaptor id when processing a command.
- Added test case to make sure adaptor can be started correctly.
- Added test case for Start streaming data in the middle of the file.
- Changed adaptor interface to remember stream name.
- Added logic to check for existing data stream and prevent the same data stream being added twice.
- Increased maximum post size to 2MB.
    Hadoop Flags: [Incompatible change, Reviewed]
          Status: Patch Available  (was: Open)

> Improve log rotation and reduce communication between agent and logging process, make agent more fault tolerant
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4434
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4434
>             Project: Hadoop Core
>          Issue Type: Improvement
>         Environment: Redhat Enterprise Linux 4.5, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>         Attachments: HADOOP-4434.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> - Chukwa Agent does not handle rotated log correctly.  The current design requires the logging process to pause the agent, rotate the log, then resume the log streaming.  The three communication between the running process and chukwa agent could become a problem when either or one of the process is down.  The implementation should be able to detect log rotation in the chukwa agent.
> - Chukwa Agent should detect and prevent the same log being streamed more than once.
> - Chukwa Agent should synchronize data streaming addition when picking up the check point file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.