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

Mikhail Petrov updated IGNITE-12925:
------------------------------------
    Description: 
It is needed to fix flaky tests:

SystemViewSelfTest.testContinuousQuery test  – [TC 
history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2075278944640125900&tab=testDetails&branch_IgniteTests24Java8=pull%2F7696%2Fhead]

SqlViewExporterSpiTest#testContinuousQuery – [TC 
history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&buildTypeId=&tab=testDetails&testNameId=-5486808152570919536&order=START_DATE_DESC&branch_IgniteTests24Java8=pull%2F7622%2Fhead&itemsCount=50]

JmxExporterSpiTest#testContinuousQuery – no failures so far but the same test 
scenario is used as above.

It seems that QueryCursor#close method 
 gives no guarantees that CQ routine will be cleared from all nodes before its 
returning. This behavior is due to StopRoutineDiscoveryMessage is immutable and 
so StopRoutineAckDiscoveryMessage can be received (QueryCoursor#close method 
returns) before GridContinuousProcessor#processStopRequest completion on all 
nodes.

  was:
It is needed to fix SystemViewSelfTest.testContinuousQuery test, which is flaky 
– [TC 
history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2075278944640125900&tab=testDetails&branch_IgniteTests24Java8=pull%2F7696%2Fhead].

It seems that QueryCursor#close method 
 gives no guarantees that CQ routine will be cleared from all nodes before its 
returning. This behavior is due to StopRoutineDiscoveryMessage is immutable and 
so StopRoutineAckDiscoveryMessage can be received (QueryCoursor#close method 
returns) before GridContinuousProcessor#processStopRequest completion on all 
nodes.


> Flaky test SystemViewSelfTest.testContinuousQuery.
> --------------------------------------------------
>
>                 Key: IGNITE-12925
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12925
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Mikhail Petrov
>            Assignee: Mikhail Petrov
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> It is needed to fix flaky tests:
> SystemViewSelfTest.testContinuousQuery test  – [TC 
> history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2075278944640125900&tab=testDetails&branch_IgniteTests24Java8=pull%2F7696%2Fhead]
> SqlViewExporterSpiTest#testContinuousQuery – [TC 
> history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&buildTypeId=&tab=testDetails&testNameId=-5486808152570919536&order=START_DATE_DESC&branch_IgniteTests24Java8=pull%2F7622%2Fhead&itemsCount=50]
> JmxExporterSpiTest#testContinuousQuery – no failures so far but the same test 
> scenario is used as above.
> It seems that QueryCursor#close method 
>  gives no guarantees that CQ routine will be cleared from all nodes before 
> its returning. This behavior is due to StopRoutineDiscoveryMessage is 
> immutable and so StopRoutineAckDiscoveryMessage can be received 
> (QueryCoursor#close method returns) before 
> GridContinuousProcessor#processStopRequest completion on all nodes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to