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-17561) Enable simulating logfeeder inputs
Date Wed, 06 Jul 2016 12:11:11 GMT

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

Hudson commented on AMBARI-17561:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #5235 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5235/])
AMBARI-17561. Enable simulating logfeeder inputs (Miklos Gergely via (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c56844922cb958c2879c292b0b57d2e5edf4a8a4])
* ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/InputSimulate.java
* ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/LogFeeder.java
* ambari-logsearch/ambari-logsearch-logfeeder/src/main/resources/alias_config.json


> Enable simulating logfeeder inputs
> ----------------------------------
>
>                 Key: AMBARI-17561
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17561
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-logsearch
>    Affects Versions: 2.4.0
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17561.patch
>
>
> Enable simulating input files in a configurable way. The parameters has to be set at
custom logfeeder.properties
> Available parameters:
> logfeeder.simulate.input_number - number of paralell inputs (threads) loading the logs,
if it is set and not 0 then all the rest of the configured inputs are ignored (running in
simulation mode)!!
> logfeeder.simulate.log_ids - comma separated list of the log ids to propagate at random,
if not set by default all the available logs are propagated at random, example: storm_drpc,storm_logviewer,storm_nimbus
> logfeeder.simulate.log_level - the level of the simulated log messages, by default WARN
> logfeeder.simulate.log_message_size - the length of the simulated log messages, can't
be less then 50 due to log message prefix, the rest is filled with 'X' characters
> logfeeder.simulate.sleep_milliseconds - the time interval at which each simulated inputs
writes one log message at random
> The text of the log message is like this:
> Simulated log message for testing, line 00000001 XXXXXXXXXXXXXXXXXXXXXXXXXX



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

Mime
View raw message