[
https://issues.apache.org/jira/browse/IGNITE-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-4222:
--------------------------------
Description:
The usage and applicability of `ComputeJobContinuation` have to be documented
on Apache Ignite Readme.io which will help out to avoid discussion like those
[1] and [4]. The new page has to be created for the topic and placed here [2].
The content should consist not only of technical details but also provide use
cases for this API:
- don't block a thread from the public pool if a job is waiting for some
result. Put the thread back into the pool and wait for the result
asynchronously.
- splitting a job into several pieces that can be executed in parallel. Refer
to this example [3].
[1]
http://apache-ignite-users.70518.x6.nabble.com/Remote-Server-Thread-Not-exit-when-Job-finished-Cause-out-of-memory-tp8934p8947.html
[2] https://apacheignite.readme.io/docs/compute-grid#section-features
[3]
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java
[4]
http://apache-ignite-users.70518.x6.nabble.com/ignite-compute-job-continuation-documentation-td16725.html
was:
The usage and applicability of `ComputeJobContinuation` have to be documented
on Apache Ignite Readme.io which will help out to avoid discussion like that
[1]. The new page has to be created for the topic and placed here [2].
The content should consist not only of technical details but also provide use
cases for this API:
- don't block a thread from the public pool if a job is waiting for some
result. Put the thread back into the pool and wait for the result
asynchronously.
- splitting a job into several pieces that can be executed in parallel. Refer
to this example [3].
[1]
http://apache-ignite-users.70518.x6.nabble.com/Remote-Server-Thread-Not-exit-when-Job-finished-Cause-out-of-memory-tp8934p8947.html
[2] https://apacheignite.readme.io/docs/compute-grid#section-features
[3]
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java
> Document the usage of ComputeJobContinuation API
> ------------------------------------------------
>
> Key: IGNITE-4222
> URL: https://issues.apache.org/jira/browse/IGNITE-4222
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Denis Magda
> Assignee: Prachi Garg
> Fix For: 2.3
>
>
> The usage and applicability of `ComputeJobContinuation` have to be documented
> on Apache Ignite Readme.io which will help out to avoid discussion like those
> [1] and [4]. The new page has to be created for the topic and placed here [2].
> The content should consist not only of technical details but also provide use
> cases for this API:
> - don't block a thread from the public pool if a job is waiting for some
> result. Put the thread back into the pool and wait for the result
> asynchronously.
> - splitting a job into several pieces that can be executed in parallel. Refer
> to this example [3].
>
> [1]
> http://apache-ignite-users.70518.x6.nabble.com/Remote-Server-Thread-Not-exit-when-Job-finished-Cause-out-of-memory-tp8934p8947.html
> [2] https://apacheignite.readme.io/docs/compute-grid#section-features
> [3]
> https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java
> [4]
> http://apache-ignite-users.70518.x6.nabble.com/ignite-compute-job-continuation-documentation-td16725.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
