ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15613) Provide a mapping for service/component to log ID
Date Wed, 30 Mar 2016 08:09:25 GMT

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

Hadoop QA commented on AMBARI-15613:
------------------------------------

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

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

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

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

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

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6089//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6089//console

This message is automatically generated.

> Provide a mapping for service/component to log ID	
> --------------------------------------------------
>
>                 Key: AMBARI-15613
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15613
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15613.patch
>
>
> Add of logfile IDs to the metainfo.xml files to support the upcoming logsearch service.
These ids are the identifier to each log collections and represent a log file on disk. Ambari
APIs need the ability to map the IDs to the actual service/component as well.
> Example:
> {code}
> <component>
>   <name>HBASE_MASTER</name>
>   <displayName>HBase Master</displayName>
>   <category>MASTER</category>
>   <cardinality>1+</cardinality>
>   <versionAdvertised>true</versionAdvertised>
>   <timelineAppid>HBASE</timelineAppid>
>   <logs>
>     <log>
>       <logId>hbase_master</logId>
>     </log>
>   </logs>
>   ...
> </component>
> {code}
> A component can have more than one logId - e.g. AMS Collector.
> Eventually <log>...</log> can contain other metadata such as log type (regular
or audit), the link to the log feeder configuration, etc.



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

Mime
View raw message