ambari-issues mailing list archives

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

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

Hudson commented on AMBARI-15613:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4563 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4563/])
AMBARI-15613. Provide a mapping for service/component to log ID (Miklos (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7bc68e1626c8ea82820cbea391a3026d8824c586])
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/metainfo.xml
* ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
* ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/metainfo.xml
* ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml
* ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/metainfo.xml
* ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/metainfo.xml
* ambari-server/src/main/resources/common-services/RANGER/0.4.0/metainfo.xml
* ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/metainfo.xml
* ambari-server/src/main/java/org/apache/ambari/server/state/LogDefinition.java
* ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/metainfo.xml
* ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/metainfo.xml
* ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/metainfo.xml
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/metainfo.xml
* ambari-server/src/test/resources/stacks/HDP/2.1.1/services/HDFS/metainfo.xml
* ambari-server/src/main/java/org/apache/ambari/server/state/ComponentInfo.java
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/metainfo.xml
* ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/metainfo.xml
* ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/metainfo.xml
* ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/metainfo.xml


> 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