Yeah, this is often implemented by some coordinator like zookeeper etc. If we know the total count and index location of every alpha, the shading policy is very easy.
> On 29 Sep 2018, at 1:17 PM, Willem Jiang <[email protected]> wrote: > > We may introduce some shading policy to let the Alpha instance to hold > a certain kind of global transactions. > If there is something wrong with the instance, the other Alpha may > take the control of the global transactions which is loaded from DB. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Sep 28, 2018 at 9:42 PM cherrylzhao <[email protected]> wrote: >> >> Hi, all >> >> In order to find timeout global transaction, we need a scanner to handle the >> global transaction. >> If scanner was started as same logic within many alpha, it will cause >> concurrent access with same db record. >> So it seem that we need a registration to manage the alpha machine, >> then we can design some data sharding logic to make a global traction will >> only be handle by one alpha. >> >> Any thought?
