Hi all,

Sorry for the late reply. Thanks for all the binding votes. I'll proceed
with the release announcement.

Sammi Chen <[email protected]> 於 2025年12月29日週一 下午2:51寫道:

> Hi Chung en,
>
> It looks like we have enough binding votes, and enough time open for
> voting, maybe we can consider wrapping up the voting result and start the
> post voting process, what do you think?
>
> Bests,
> Sammi
>
> On Tue, 23 Dec 2025 at 00:55, soumitra sulav <[email protected]> wrote:
>
> > +1
> > Thanks, @Chung En Lee.
> >
> > Functions that were earlier certified on RC0, works fine on RC3 as well.
> No
> > regression observed.
> > Tests from below features were covered :
> >
> > Ozone Filesystem
> > Ozone S3
> > Ozone wire encryption
> > Ozone HA (both OM and SCM)
> > Ozone Trash
> > Ozone SPNEGO
> > Ozone MapReduce
> > Ozone Container Replication/Re-replication
> > Ozone Pipeline
> > Ozone TDE (Transparent data encryption)
> > Ozone Container Balancer
> > Ozone Erasure Coding
> > Ozone Hive, Spark, Impala (Basic Integration)
> > Ozone Multitenancy
> > Ozone DN decommissioning
> > Ozone hsync
> > Ozone snapshots
> >
> > Thanks,
> > Soumitra
> >
> > On Sat, Dec 20, 2025 at 12:12 AM Attila Doroszlai <[email protected]
> >
> > wrote:
> >
> > > > There are start/stop-ozone.sh scripts in the sbin/ dir in the release
> > > > tarball.  How to use them?  I tried multiple times in the past years
> > but
> > > > never succeeded.  I should have asked this question earlier.  I
> suspect
> > > no
> > > > one uses them for a long time and the scripts are simply not working
> > > > anymore.
> > >
> > > I agree that they are obscure and rarely touched (12 commits over 7.5
> > > years).
> > >
> > > But a very basic smoke test for these scripts is part of CI, see
> > > hadoop-ozone/dist/src/main/compose/ozonescripts/README.md
> > >
> > > May be worth a separate discussion to see if anyone uses them or can be
> > > removed.
> > >
> > > -Attila
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
>

Reply via email to