Cache Queues And Load Balancing in GridGain -


In Docs (), it has been mentioned that the balance of alternative instrument loads by the work worker grid on the cache queue.

I examined this concept of this type:

  1. A constructor was implemented, which would allow grid-earning jobs on a split cache (distributed block queue) Attaches. I had to use a partitioned queue (because the local queue is not suited for multi-grid access, by definition).
  2. A user has been implemented, which at startup, creates nodes threads that always block on, work on the queue, consumer (take operation) to send it from the job to the grid, Take the next () operation before blocking. Question:

    1. (2) The right way to implement a listener (one option presented to listener's jobs rather than listener threads within the consumer
    2. While this architecture provides dynamic load balancing, T appears that provides several benefits that provide regular gridgen models such as failover, affinity transfer (distributed cash) Goes - so in the calculation of data Have to be taken not)

    What are my comments right thing? Thanks

It seems that you are on the right track, if you need to use load balancing based On GridGain distributed queue

However, it seems that it would be better if you use the standard grid compute API to simply send the grid to your grid-arne-worthy jobs. Grid-Gain will automatically load these tasks in the background.


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

c# - MySQL Parameterized Select Query joining tables issue -