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

Hadoop QA commented on AMBARI-15679:
------------------------------------

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

    {color:red}-1 @author{color}.  The patch appears to contain 9 @author tags 
which the Hadoop community has agreed to not allow in code contributions.

    {color:green}+1 tests included{color}.  The patch appears to include 29 new 
or modified test files.

      {color:red}-1 javac{color}.  The applied patch generated 74 javac 
compiler warnings (more than the trunk's current 72 warnings).

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 
ambari-logsearch/ambari-logsearch-assembly 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6300//testReport/
Javac warnings: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6300//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6300//console

This message is automatically generated.

> Initial commit for LogSearch service definition
> -----------------------------------------------
>
>                 Key: AMBARI-15679
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15679
>             Project: Ambari
>          Issue Type: Technical task
>          Components: stacks
>    Affects Versions: 2.4.0
>            Reporter: Sumit Mohanty
>            Assignee: Olivér Szabó
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15679.patch
>
>
> LogSearch service includes three major components:
> * A Solr cloud to store logs and query
> * Log collectors/feeders that consume log files being generated by the 
> services
> * Log search service that provides REST API and UI front end
> The above components are managed by Ambari through a stack definition. The 
> stack definition provides the mechanism to have the LogSearch service 
> configured to read log files created by other services, including Ambari 
> Server. This integration allows customizing log locations and letting 
> LogSearch service be aware of the locations.
> Final peace is to provide an integration from the Ambari UI to LogSearch 
> service so that the logs for a service is easily accessible from the service 
> dashboards.



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

Reply via email to