[jira] [Commented] (METRON-239) NOOP Bulk Writer

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on METRON-239:
---------------------------------------

GitHub user cestella opened a pull request:

    https://github.com/apache/incubator-metron/pull/162

    METRON-239: NOOP Bulk Message Writer

    We should have a NOOP Writer that will sleep at random. This will help differentiate write slowdowns between index misconfiguration and storm/kafka misconfiguration.
    
    It should be configurable from the object as well as from zookeeper.
    * In zookeeper, the "noopLatency" field should be a string defining the latency.
    * On the object, there should be a "withLatency" function which allows you to define the latency.
    
    The latency is defined via string in one of two modes:
    * An integer which provides a fixed latency
    * A comma separated range (i.e. "10, 20") which allows for a random latency between the bounds.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cestella/incubator-metron noop_writer

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-metron/pull/162.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #162
    
----
commit 93170002ba3c10c82cacc69597082bfb9cea21f8
Author: cstella <ce...@gmail.com>
Date:   2016-06-20T15:37:21Z

    METRON-239: NOOP Bulk Message Writer

----


> NOOP Bulk Writer
> ----------------
>
>                 Key: METRON-239
>                 URL: https://issues.apache.org/jira/browse/METRON-239
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Casey Stella
>            Assignee: Casey Stella
>
> We should have a NOOP Writer that will sleep at random.  This will help differentiate write slowdowns between index misconfiguration and storm/kafka misconfiguration.
> It should be configurable from the object as well as from zookeeper.
> In zookeeper, the "noopLatency" field should be a string defining the latency.
> On the object, there should be a "withLatency" function which allows you to define the latency.
> The latency is defined via string in one of two modes, either an integer which provides a fixed latency or a comma separated range (i.e. "10, 20") which allows for a random latency between the bounds.



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