Sasha,
The idea behind the ticket was as follows: currently, the rebalanceDelay
property is set in CacheConfiguration, which is not very flexible. In
certain circumstances, a user might expect particularly large load on some
segments of the cluster and want to disable rebalancing for those
(existi
Hi Alexandr,
Yes, I'm using a StreamReceiver since I'm mostly using the cache as a
router. The implementation is more-or-less like the following:
The StreamPipeline is managed by the data node which contains the stages
that make up the pipeline and what service is responsible for each stage
(th
As far as I can see from ticket title reporter wants to disable rebalancing
on per-node basis. So, some nodes would not load partitions from other
nodes while others should load normally. Disabling partition map exchange
will stop rebalancing all over the grid (however, I find this pretty useful
fe
to Nick,
could you please describe in more detail the use of DataStreamer (do you
use StreamReceiver)?
It seems that you've unnecessary care about synchronous service startup and
cache rebalance. Service should start quickly after node has joined the
topology, and will process all the data has be
I can outline a use-case I have which may help define requirements for this
task. For context, I was originally going to try and address the below
use-case by disabling automatic rebalancing on a per-cache basis and use a
cluster-wide task to orchestrate manual rebalancing; however, this issue
soun
