You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Prachi Garg (JIRA)" <ji...@apache.org> on 2017/05/30 22:24:05 UTC

[jira] [Commented] (IGNITE-5182) Document Job Stealing API Usage

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

Prachi Garg commented on IGNITE-5182:
-------------------------------------

[~dmagda], I thought it is more appropriate to place Job Stealing documentation on Job Scheduling page since both are related to Collision SPI.

Please review - https://apacheignite.readme.io/docs/job-scheduling#job-stealing

> Document Job Stealing API Usage
> -------------------------------
>
>                 Key: IGNITE-5182
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5182
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Denis Magda
>            Assignee: Prachi Garg
>             Fix For: 2.1
>
>
> There is no documentation for job stealing capabilities on readme.io:
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/collision/jobstealing/JobStealingCollisionSpi.html
> Let's add it do this doc saying that it's "late load balancing technique".:
> https://apacheignite.readme.io/docs/load-balancing
> The other load balancing algorithms described there are for "early load balancing".
> T discussion that spotted the gap:
> http://stackoverflow.com/questions/43846316/one-task-per-node-only-in-apache-ignite/



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)