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/10/16 17:05: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=16652075#comment-16652075 ]
ASF GitHub Bot commented on METRON-1778:
----------------------------------------
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/1197
Any idea why this is failing?
```
Running org.apache.metron.profiler.storm.integration.ProfilerIntegrationTest
2018-09-28 14:02:45 ERROR FluxTopologyComponent:198 -
NotAliveException(msg:profiler is not alive)
at org.apache.storm.daemon.nimbus$check_storm_active_BANG_.invoke(nimbus.clj:1017)
at org.apache.storm.daemon.nimbus$fn__9109$exec_fn__1371__auto__$reify__9138.killTopologyWithOpts(nimbus.clj:1550)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
at org.apache.storm.LocalCluster$_killTopologyWithOpts.invoke(LocalCluster.clj:90)
at org.apache.storm.LocalCluster.killTopologyWithOpts(Unknown Source)
at org.apache.metron.integration.components.FluxTopologyComponent.killTopology(FluxTopologyComponent.java:216)
at org.apache.metron.integration.components.FluxTopologyComponent.stop(FluxTopologyComponent.java:174)
at org.apache.metron.integration.ComponentRunner.stop(ComponentRunner.java:136)
at org.apache.metron.profiler.storm.integration.ProfilerIntegrationTest.tearDownAfterClass(ProfilerIntegrationTest.java:399)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 289.466 sec <<< FAILURE! - in org.apache.metron.profiler.storm.integration.ProfilerIntegrationTest
testProcessingTimeWithTimeToLiveFlush(org.apache.metron.profiler.storm.integration.ProfilerIntegrationTest) Time elapsed: 136.722 sec <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.apache.metron.profiler.storm.integration.ProfilerIntegrationTest.testProcessingTimeWithTimeToLiveFlush(ProfilerIntegrationTest.java:210)
...
```
> 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)