[ 
https://issues.apache.org/jira/browse/IGNITE-25769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024630#comment-18024630
 ] 

Ignite TC Bot commented on IGNITE-25769:
----------------------------------------

{panel:title=Branch: [pull/12166/head] Base: [master] : Possible Blockers 
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility 1{color} [[tests 
1|https://ci2.ignite.apache.org/viewLog.html?buildId=8631595]]
* IgniteControlUtilityTestSuite: 
KillCommandsControlShTest.testCancelConsistencyTaskSequential[cmdHnd=cli] - 
Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Snapshots 2{color} [[tests 0 Out Of Memory Error 
|https://ci2.ignite.apache.org/viewLog.html?buildId=8631660]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
3|https://ci2.ignite.apache.org/viewLog.html?buildId=8631627]]
* DotNetCore: ThickClientExamplesTest.TestThickExample(Streaming) - History for 
base branch is absent.
* DotNetCore: ProjectFilesTest.TestCsprojFiles(Streaming) - History for base 
branch is absent.
* DotNetCore: ProjectFilesTest.TestVsCodeFiles - Test has low fail rate in base 
branch 0,0% and is not flaky

{color:#d04437}SPI{color} [[tests 
1|https://ci2.ignite.apache.org/viewLog.html?buildId=8631642]]
* IgniteSpiTestSuite: TcpCommunicationSpiDropNodesTest.testOneNode - Test has 
low fail rate in base branch 0,0% and is not flaky

{panel}
{panel:title=Branch: [pull/12166/head] Base: [master] : New Tests 
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#00008b}Platform .NET (Windows){color} [[tests 
2|https://ci2.ignite.apache.org/viewLog.html?buildId=8631628]]
* {color:#013220}exe: ComputeTaskContinuousMapperTest.SendsJobsToSpecificNode - 
PASSED{color}
* {color:#013220}exe: 
ComputeTaskContinuousMapperTest.DistributesJobsUsingLoadBalancer - PASSED{color}

{color:#00008b}Platform .NET (Core Linux){color} [[tests 
4|https://ci2.ignite.apache.org/viewLog.html?buildId=8631627]]
* {color:#013220}DotNetCore: 
ComputeTaskContinuousMapperTest.SendsJobsToSpecificNode - PASSED{color}
* {color:#013220}DotNetCore: 
ComputeTaskContinuousMapperTest.DistributesJobsUsingLoadBalancer - PASSED{color}
* {color:#8b0000}DotNetCore: 
ThickClientExamplesTest.TestThickExample(Streaming) - FAILED{color}
* {color:#8b0000}DotNetCore: ProjectFilesTest.TestCsprojFiles(Streaming) - 
FAILED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8631670&buildTypeId=IgniteTests24Java8_RunAll]

> ComputeTaskContinuousMapper in Ignite.NET
> -----------------------------------------
>
>                 Key: IGNITE-25769
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25769
>             Project: Ignite
>          Issue Type: Improvement
>          Components: .NET
>    Affects Versions: 2.17
>            Reporter: Alexey Kukushkin
>            Assignee: Alexey Kukushkin
>            Priority: Major
>              Labels: ise
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We are missing {{ComputeTaskContinuousMapper}} in Ignite.NET, which is 
> available in the Ignite Java API but not in .NET. The official Ignite 
> documentation only briefly mentions {{ComputeTaskContinuousMapper}} in the 
> [Pre-defined 
> Resources|https://ignite.apache.org/docs/latest/resources-injection#pre-defined-resources]
>  section. Based on our practical experience, we have identified additional 
> requirements that could be addressed by this feature:
>  * Enable development of distributed computations in .NET without requiring 
> an upfront definition of all compute jobs on the "mapping" node.
>  * Optimize memory usage: our application occasionally creates over one 
> hundred thousand compute jobs, each with a significant memory footprint. This 
> might lead to the "mapping" node going out of memory.
>  * Facilitate better job management and fine-tuning. Continuous job creation 
> enables optimization of job parameters based on the current runtime.
> In summary, these requirements necessitate *streaming* of compute jobs. 
> Exposing the existing Java API's {{ComputeTaskContinuousMapper}} 
> functionality in .NET would satisfy these needs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to