You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Nick Allen (JIRA)" <ji...@apache.org> on 2019/04/23 19:51:00 UTC

[jira] [Updated] (METRON-1778) Out-of-order timestamps may delay flush in Storm Profiler

     [ https://issues.apache.org/jira/browse/METRON-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Allen updated METRON-1778:
-------------------------------
    Fix Version/s:     (was: Next + 1)
                   0.7.1

> Out-of-order timestamps may delay flush in Storm Profiler
> ---------------------------------------------------------
>
>                 Key: METRON-1778
>                 URL: https://issues.apache.org/jira/browse/METRON-1778
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>             Fix For: 0.7.1
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When timestamps are received out-of-order there can be cases where a flush signal should have been signalled, but is not.  The flush signal can be either delayed slightly or occur prematurely.
> The smaller the profile period is, the more likely this is to impact the results.  I would not expect this to greatly impact the results of the Profiler under normal usage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)