[
https://issues.apache.org/jira/browse/IGNITE-7963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411276#comment-16411276
]
Dmitriy Pavlov commented on IGNITE-7963:
----------------------------------------
[~ilyak], I've checked
https://ci.ignite.apache.org/viewLog.html?buildId=1152323&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll
Unfortunately It is too much test failure there [tests 72 suites 4].
Especially suspicious are
IgniteCacheTestSuite2: CachePartitionStateTest.testPartitionState1_1 (fail
rate 0,0%)
IgniteSpiTestSuite:
GridTcpCommunicationSpiConcurrentConnectSslSelfTest.testWithLoad (fail rate
0,0%)
IgnitePdsTestSuite2:
IgnitePdsPageEvictionDuringPartitionClearTest.testPageEvictionOnNodeStart (fail
rate 0,0%)
IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryExecuteInPrimaryTest.testReplicatedCache (fail rate 0,0%)
IgniteBinaryCacheTestSuite:
GridCacheBalancingStoreSelfTest.testConcurrentLoadAll (fail rate 0,0%)
As simplest step you can merge current master into your branch and re-run
tests. Probably these tests were already fixed.
Also feel free to create investigations for remaining failures to component
mainteiners.
> Futures from DataStreamer.addData() fail to complete if DataStreamer.flush()
> is never called
> --------------------------------------------------------------------------------------------
>
> Key: IGNITE-7963
> URL: https://issues.apache.org/jira/browse/IGNITE-7963
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.3
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Priority: Minor
> Labels: usability
>
> DataStreamer.addData() will return futures for operation.
> Thus the naive use of DataStreamer will look like this:
> {code}
> for (Data d : data)
> futs.add(dataStreamer.addData(d));
> for (IgniteFuture f : futs)
> f.get();
> dataStreamer.close();
> {code}
> However, this does not work. Unless flush is called (manual or otherwisE),
> futures are not being processed. This code will likely hang on f.get().
> The solution, IMHO, is to introduce dataStreamer-flushing clause in f.get().
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
