We at VerizonMedia (Yahoo!) have been running FavoredNodes for about 4
years now in production and it has helped us a lot with our scale.
Since we started working on this many years ago, we have contributed
patches to upstream, although not much recently. We will resume
contributing the remaining
On Mon, Apr 26, 2021 at 7:30 PM Mallikarjun
wrote:
> Inline reply
>
> On Tue, Apr 27, 2021 at 1:03 AM Stack wrote:
>
> > On Mon, Apr 26, 2021 at 12:30 PM Stack wrote:
> >
> > > On Mon, Apr 26, 2021 at 8:10 AM Mallikarjun
> > > wrote:
> > >
> > >> We use FavoredStochasticBalancer, which by
Inline reply
On Tue, Apr 27, 2021 at 1:03 AM Stack wrote:
> On Mon, Apr 26, 2021 at 12:30 PM Stack wrote:
>
> > On Mon, Apr 26, 2021 at 8:10 AM Mallikarjun
> > wrote:
> >
> >> We use FavoredStochasticBalancer, which by description says the same
> thing
> >> as FavoredNodeLoadBalancer.
On Mon, Apr 26, 2021 at 12:30 PM Stack wrote:
> On Mon, Apr 26, 2021 at 8:10 AM Mallikarjun
> wrote:
>
>> We use FavoredStochasticBalancer, which by description says the same thing
>> as FavoredNodeLoadBalancer. Ignoring that fact, problem appears to be
>>
>>
>
> Other concerns:
>
> *
On Mon, Apr 26, 2021 at 8:10 AM Mallikarjun
wrote:
> We use FavoredStochasticBalancer, which by description says the same thing
> as FavoredNodeLoadBalancer. Ignoring that fact, problem appears to be
>
Does this work?
> favor node balancer is a problem, as it stores the favor node
We use FavoredStochasticBalancer, which by description says the same thing
as FavoredNodeLoadBalancer. Ignoring that fact, problem appears to be
favor node balancer is a problem, as it stores the favor node information
> in hbase:meta.
>
Going a step back.
Did we ever consider giving a thought
As you all know, we always want to reduce the size of the hbase-server
module. This time we want to separate the balancer related code to another
sub module.
The design doc:
https://docs.google.com/document/d/1T7WSgcQBJTtbJIjqi8sZYLxD2Z7JbIHx4TJaKKdkBbE/edit#
You can see the bottom of the design
