Hi Andor,
Please keep us updated how itbll goes with the new server side config. Your
result will be used a datapoint as well.
Thanks,
Huaxiang
On 2022/03/25 17:51:49 Huaxiang Sun wrote:
> Hi Andor,
>
> I get what you are saying. The HFile refreshing is the old way for replica
> regions to refresh hfiles periodically, default is 5 minutes. In this itbll
> case, we need to have the wal replication enabled for meta replica. Please
> check out,
> https://hbase.apache.org/book.html#_async_wal_replication_for_meta_table_as_of_hbase_2_4_0.
> Basically, you need to set
> "hbase.region.replica.replication.catalog.enabled" to true in the
> configuration and rerun itbll. Otherwise, all meta changes at the primary
> meta region wont be updated at the replica meta regions and it will result in
> itbll failures.
>
> Hope this helps,
>
> Huaxiang
>
>
> On 2022/03/25 13:46:42 Andor Molnar wrote:
> > Hi Huaxiang,
> >
> > We use 2.4.6 for the tests.
> >
> > I run itbll with the following command:
> >
> > hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList generator
> > 15 1000000 /tmp/hbase-itbll
> >
> > for the generator step and essentially jobs have failed. We can see the
> > meta request are spanning out to replicas, but writes start failing after
> > this due to the stale cache which is not getting updated.
> >
> > Would you please tell me more about ‘hfile refresh’ and how to configure it?
> >
> > Thanks,
> > Andor
> >
> >
> >
> >
> > > On 2022. Mar 24., at 17:43, Huaxiang Sun <[email protected]> wrote:
> > >
> > > Hi Andor,
> > >
> > > Which 2.4 release do you test in your lab? We use this feature at
> > > production cluster with 2.4.5.
> > > At server side, we use hfile refresh instead of wal replication. I used
> > > to run itbll for each release with this feature enabled. How did you find
> > > the errors, did itbll fail?
> > >
> > > Regards,
> > > Huaxiang
> >
> >
>
