Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 8 Aug 2016 12:36:20 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12990669.1468911446000.248626.1470659780553@Atlassian.JIRA>
In-Reply-To: <JIRA.12990669.1468911446000@Atlassian.JIRA>
References: <JIRA.12990669.1468911446000@Atlassian.JIRA> <JIRA.12990669.1468911446517@arcas>
Subject: [jira] [Commented] (AMBARI-17785) Provide support for S3 as a first
 class destination for log events
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 08 Aug 2016 12:36:22 -0000


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

Hadoop QA commented on AMBARI-17785:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12822508/AMBARI-17785-2.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8323//console

This message is automatically generated.

> Provide support for S3 as a first class destination for log events
> ------------------------------------------------------------------
>
>                 Key: AMBARI-17785
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17785
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-logsearch
>    Affects Versions: 2.4.0
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-17785-1.patch, AMBARI-17785-2.patch, AMBARI-17785.patch
>
>
> AMBARI-17045 added support for uploading Hadoop service logs from machines to S3. The intended usage there was as a one time trigger where, on-demand, the log files matching certain paths can be uploaded to a given S3 bucket and path.
> While useful, there are some use cases where we might need more than this one time activity, particularly when clusters are deployed on ephemeral machines such as cloud instances:
> * The machines running the logfeeder could be irrevocably lost and in that case we would not be able to retrieve any logs.
> * If we are copying logs at one time, that were generated over a long period of time, the time to copy all the logs at the end could extend cluster up-time and cost.
> It would be nice to have an ability to support S3 as another output destination in logsearch just like Kafka, Solr etc. This JIRA is to track work towards this enhancement.


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