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

Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/11/14 18:27:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16686957#comment-16686957 ] 

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

Github user nickwallen commented on the issue:

    https://github.com/apache/metron/pull/1197
  
    @JonZeolla That error is a pre-existing condition that is tracked here;[ METRON-1810](https://issues.apache.org/jira/browse/METRON-1810).  I am not sure what the root cause is.


> 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
>
> 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)