[
https://issues.apache.org/jira/browse/IGNITE-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030334#comment-16030334
]
Denis Magda commented on IGNITE-5182:
-------------------------------------
[~pgarg], frankly, I as a user doesn't expect to find this paragraph on "Job
Scheduling" section. Personally, it perfectly fits the load balancing.
Extra notes:
* Please add a Java version of the configuration example.
* We have to note that
{{org.apache.ignite.spi.failover.jobstealing.JobStealingFailoverSpi}} has to be
enabled. Otherwise, this collision SPI will have no effect.
> 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: Denis Magda
> 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)
