runzhiwang,
Thanks a lot for working hard on Ratis Streaming and running the
benchmarks! Ratis Streaming is going to be a big improvement in Ozone.
It is anticipated that Ratis Streaming can
- improve the performance as shown in the benchmark results;
- improve the scalability of Ozone since Str
Hi Ozone dev,
We should discuss whether we want to do "merge" or "rebase" for
the HDDS-4454 branch. This a standard git question:
https://stackoverflow.com/questions/804115/when-do-you-use-git-rebase-instead-of-git-merge
I suggest to do "rebase" rather than "merge" since it can keep the commit
h
> I am wondering why this "merge or rebase" question does not arise for
other
tickets. Is it because HDDS-4454 brings significant change or something
else ?
Thanks for the question. As Arpit mentioned, this is only relevant to the
development branches. Individual development branches can decide
> I am wondering why this "merge or rebase" question does not arise for
other
tickets. Is it because HDDS-4454 brings significant change or something
else ?
Thanks for the question. As Arpit mentioned, this is only relevant to the
development branches. Individual development branches can decide
> IMHO if we need to trace the commit history later, we could keep the
branch after merging it instead of deleting it.
This usually does not work well since the new commits won't be merged to
the feature branch anymore.
> From the whole project angle, +1 on Rebase. Cleaner history, easier
trouble
ebasing.
> > > >> There is a sentence "to tell the story in the way that’s best for
> > future
> > > >> readers" in this article and it makes sense.
> > > >>
> > > >> "Merge" is more friendly for branch developers, and
+1
We should merge it so that more people can try it. We can work on the
remaining tasks in the master branch. Thanks a lot!
Tsz-Wo
On Thu, Apr 7, 2022 at 1:17 PM Aravindan Vijayan
wrote:
> +1 for the merge. Thanks for the great work!
>
>
>
> On Wed, Apr 6, 2022 at 9:45 PM Prashant Pogde >
>
+1. Thanks a lot for working on this!
Tsz-Wo
On Wed, May 25, 2022 at 3:08 AM NILOTPAL NANDI
wrote:
> +1 for the merge.
>
> Thanks,
> Nilotpal Nandi
>
> On Tue, May 24, 2022 at 8:40 PM Hanisha Koneru
> wrote:
>
> > +1 for merge.
> >
> > Thanks
> > Hanisha
> >
> > On Tue, May 24, 2022 at 5:08 A
Checked LICENSE.txt and NOTICE.txt. Found the following problems:
*** LICENSE.txt ***
- hadoop-hdds/docs/themes/ozonedoc/static/js/bootstrap.min.js
is under "BSD 3-Clause" but it actually is "MIT License".
- hadoop-hdds/framework/src/main/resources/webapps/static/d3-3.5.17.min.js
is under "B
Dear Ozone Devs,
We would like to start this discussion thread for the proposal to merge
https://issues.apache.org/jira/browse/HDDS-4454 Ozone Streaming Write
Pipeline to the master branch.
Currently, Ozone write pattern is bursty and involves multiple buffers
copies as well multiple ratis log sy
to have streaming writes enabled automatically
> for large files?
>
> ----- Original message -
> From: Tsz Wo Sze
> To: dev Ozone
> Subject: [DISCUSS] Proposal to merge HDDS-4454 Ozone Streaming Write
> Pipeline into master
> Date: Thursday, December 01, 2022 12:24 P
e
> >>
> >> On Tue, 06 Dec 2022 09:35:42 +0800 Arpit Agarwal wrote ---
> >>> +1 for merging this feature. This is an important performance
> >> improvement for Ozone.
> >>>
> >>> Nicholas, what's the plan to have streaming wr
Hi Ozone Dev,
This is the VOTE thread following to the discussion thread
https://lists.apache.org/thread/nt7jwrxklk79qvmjwpv8noor760p156t
Here is my +1. The VOTE will close in 7 days. Thank you in advance!
Tsz-Wo
+1
- Verified all checksums and signatures.
- Checked LICENSE.txt and NOTICE.txt.
- Compared the files in the src tarball with the files in git.
- Built from source successfully.
- Able to run yarn job with docker.
Job Finished in 28.312 seconds
Estimated value of Pi is 3.14146667
Reminder: The VOTE will close tomorrow.
Tsz-Wo
On Fri, Dec 9, 2022 at 3:06 PM Tsz Wo Sze wrote:
> Hi Ozone Dev,
>
> This is the VOTE thread following to the discussion thread
> https://lists.apache.org/thread/nt7jwrxklk79qvmjwpv8noor760p156t
>
> Here is my +1. The VOTE wi
Reminder: Only 3 days left to vote.
Tsz-Wo
On Sun, Dec 11, 2022 at 1:11 AM mingchao zhao wrote:
> Hello all,
>
> As discussed earlier, I am calling for a vote on Apache Ozone 1.3.0 RC2.
>
> Compared with RC1, we mainly solve the problems of NOTICE and LICENSE.
> In addition, we introduced some
nus Chow wrote:
> +1
>
> --
> Symious
>
>
> Siyao Meng 于2022年12月16日周五 03:55写道：
>
> > +1
> >
> > -Siyao
> >
> > On Dec 15, 2022 at 1:45:02 AM, Tsz Wo Sze wrote:
> >
> > > Reminder: The VOTE will close tomorrow.
> > >
&g
+1
Tsz-Wo
On Sat, Jan 21, 2023 at 3:26 AM Siddharth Wagle wrote:
> +1 for the merge.
>
> - Sid
>
> On Fri, Jan 20, 2023 at 11:21 AM Uma Maheswara Rao Gangumalla <
> umaganguma...@gmail.com> wrote:
>
> > +1
> >
> > Regards,
> > Uma
> >
> > On Wed, Jan 18, 2023 at 11:08 AM Prashant Pogde
> >
> >
+1
Tsz-Wo
On Thu, Feb 9, 2023 at 11:21 AM Prashant Pogde
wrote:
> +1
>
> Prashant
>
> > On Feb 9, 2023, at 2:50 AM, NILOTPAL NANDI
> wrote:
> >
> > +1 for the merge (non-binding).
> >
> > - Nilotpal Nandi
> >
> > On Thu, Feb 9, 2023 at 8:57 AM Ayush Saxena wrote:
> >
> >> +1
> >>
> >> -Ayush
>
+1
Tsz-Wo
On Mon, Feb 27, 2023 at 11:12 PM Sadanand Shenoy wrote:
> +1 for merge.
>
> -Sadanand
>
> On Tue, Feb 28, 2023 at 12:26 PM Yi-Sheng Lien wrote:
>
> > +1 for merging it.
> >
> > Zita Dombi 於 2023年2月27日 週一 下午11:01 寫道：
> >
> > > Hi Ozone Devs!
> > >
> > > I’m starting this vote thread f
+1
The change list looks good. Thanks.
Tsz-Wo
On Wed, Mar 15, 2023 at 4:59 PM Sammi Chen wrote:
> +1.
>
> It's good to have minor releases of 1.3 to include all important bug fixes.
>
> Bests,
> Sammi Chen
>
> On Tue, 14 Mar 2023 at 14:52, Ritesh Shukla
> wrote:
>
> > Folks,
> > As part of th
+1 We should have a users@ mailing list.
Tsz-Wo
On Wed, Jun 28, 2023 at 7:30 AM Wei-Chiu Chuang wrote:
> Hi Ozone community,
>
> Many Apache projects have users@ mailing lists for users to seek answers.
> As the focus of the project moves from core developers to regular users, I
> wonder if it
Hi Ozone Dev,
Ratis just have rolled out the thirdparty 1.0.5 release. The Ratis 3.0.0
release will come out soon. I will keep testing it with Ozone [1].
Currently, we have the following blockers targeted to Ozone 1.4.0:
- HDDS-5230 Select best licenses for each dual licensed dependencies
- HDD
> Is suggested to evaluate HDDS-9279 ...
Thanks a lot for checking HDDS-9279! The pull request is basically working
and ready for evaluation. The main missing part is that if a client fails
to talk to a server, it should failover to another server. Please keep me
posted and feel free to let me
> 1. 1.4.0 release.
> RATIS 3.0 release is under voting.
> There are two remaining blocker issues targeting 1.4.0.
The Ratis 3.0.0 vote [1] has been passed. We could start rolling Ozone
1.4.0 once we have fixed all the blockers [2].
Tsz-Wo
[1] Ratis 3.0.0 vote:
https://lists.apache.org/threa
Hi Janus,
Thanks for working on the 1.4.0 release!
For HDDS-9784, it probably is not a blocker since it is about the
performance of setting various values of a conf. Users could change the
conf as they please. There are trade-offs between system behaviors. It
probably won't have a perfect conf
Hi Yiyang,
Thanks for creating the 1.4.0 branch!
We have 1.4.0 two blockers, HDDS-9342 and HDDS-9876, which are
closely related.
Tsz-Wo
> ... If for any reason, the ratis need to be reset and transaction ID
will start from 0 again, then it will cause updateID compare issue and
duplicate object ID issue after that. ...
We could add a new feature to Ratis in order to let the state machine pass
the starting log index. It seems a ge
do you think?
>
> Bests,
> Sammi
>
> On Wed, 10 Jan 2024 at 04:14, Tsz Wo Sze wrote:
>
> > > ... If for any reason, the ratis need to be reset and transaction ID
> > will start from 0 again, then it will cause updateID compare issue and
> > duplicate object ID iss
> 3. Discussed HDDS-10385 ... a high GC pressure is also observed if
ThreadLocal is replaced with create object for each OMClientRequest. ...
In HDDS-10385 (https://github.com/apache/ozone/pull/6234), it claims that
"Instance object is having thread local object, which can have memory leak
as th
> b. Observed that many objects in OM are serialized and deserialized
multiple times, which add the pressure to GC.
Here is an idea to avoid multiple serialization/deserialization in OM:
https://issues.apache.org/jira/browse/HDDS-9290
Tsz-Wo
On Wed, Mar 6, 2024 at 12:30 AM Devesh Singh
wrote:
+1 It is good to release Ozone 1.4.1. Let's also update the Ratis version.
Tsz-Wo
On Sun, Apr 7, 2024 at 4:28 AM wanghongbing wrote:
> +1, Releasing 1.4.1 is meaningful.
>
>
> > On Apr 3, 2024, at 13:15, Sammi Chen wrote:
> >
> > Dear Ozone Devs,
> >
> > We have released 1.4.0 on Jan 19th.
>
Ratis release.The next
> version of Ratis is 3.1.0. Can I ask when Ratis 3.1.0 will be
> released?Xi Chen
> At 2024-04-08 06:52:20, "Tsz Wo Sze" wrote:
> >+1 It is good to release Ozone 1.4.1. Let's also update the Ratis
> version.
> >
> >Tsz-Wo
> >
Hi Sammi,
Attila, Duong, Siyao and I are testing Ozone with the latest Ratis code.
We found that some tests may fail mysteriously. We must fix these failures
first.
- TestECKeyOutputStreamWithZeroCopy may fail with
GroupMismatchException: 3ff8772d-f587-4fdc-a76a-606c19c41894:
group-9B86
+1
Tsz-Wo
On Tue, Jul 9, 2024 at 1:47 PM Ayush Saxena wrote:
> +1
>
> -Ayush
>
> On Tue, 9 Jul 2024 at 08:18, Attila Doroszlai
> wrote:
> >
> > > I would like to propose merging into master the feature branch
> > > HDDS-10656-atomic-key-overwrite, which was used to develop Atomic Key
> > > Ove
+1 for merging the hsync branch.
Tsz-Wo
On Tue, Jul 30, 2024 at 8:14 PM Ashish kumar wrote:
> Thanks WeiChiu, Ethan, Siyao for the vote.
> Anyone else like to vote?
>
> On Wed, Jul 31, 2024 at 5:37 AM Siyao Meng
> wrote:
>
> > +1 on the merge.
> >
> > Disclaimer: I have contributed to branch H
> Will there be any compatibility issues after moving enum
`StorageTypeProto` from `ScmServerDatanodeHeartbeatProtocol.proto` to
`hdds.proto` and standardize, and change all the places where
`StorageTypeProto` is used in the existing protobuf to
`hdds.proto#StorageTypeProto`?
There are different l
word that is used to reserve field IDs is not
> > supported either in proto2.
> > This was found while trying to remove the listTrash and recoverTrash APIs
> > as a part of HDDS-11251
> >
> > On Mon, 19 Aug 2024 at 22:05, Tsz Wo Sze wrote:
> >
> > > > W
> (2) Key put fails for large files (> 20GB) due to a memory leak in Ratis 3.1.0
...
Duong & Wei-chiu,
Thanks for finding this problem!
Agree that we should have a Ratis 3.1.1 release.
BTW, "Memory leak" usually means that memory was allocated but not
released; see https://en.wikipedia.org/wiki/
+1 for Ozone 2.0
> (1) I want to drop Hadoop2 support.
It would be great if we can also replace proto 2 with proto 3. However, it
will take some time for the replacement. It probably has to wait till
Ozone 3.0. Hopefully, it won't be 4 more years.
@Wei-Chiu Chuang , thanks a lot for starting
Hi,
Thanks for the discussion (and thanks Sammi for the summary) !
> - Ozone 1.4.1 release, waiting for RATIS 3.1.1 release
RATIS 3.1.1 will be out soon. We are preparing the rc0.
> - Ozone Hadoop 2 filesytem jar is used currently for YARN cluster
For Ozone Hadoop 2, would it be possible to m
DS-11136>, which is good. What is
> the overall status update? Are we ready for the next release candidate?
>
>
> Ethan
>
> On Wed, Aug 21, 2024 at 12:33 PM Tsz Wo Sze wrote:
>
> > > (2) Key put fails for large files (> 20GB) due to a memory leak in
> Ratis
>
> it's confirmed.
>
> Sammi
>
> On Tue, 29 Oct 2024 at 01:21, Tsz Wo Sze wrote:
>
> > > Follower reader feature is used in production environment with a bit of
> > customization.
> >
> > Weiming/Weiming/Jianghua, That is great! Could you submit a p
On Fri, Oct 25, 2024 at 2:16 AM Sammi Chen wrote:
> Hi Tsz-Wo,
>
> What's the impact of https://issues.apache.org/jira/browse/RATIS-2149?
> Will it cause OM HA leader audo election fail in some circumstances?
>
> Thanks,
> Sammi
>
> On Wed, 23 Oct 2024 at 05:43
> Follower reader feature is used in production environment with a bit of
customization.
Weiming/Weiming/Jianghua, That is great! Could you submit a pull request
for https://issues.apache.org/jira/browse/HDDS-9279 ? Thank you in advance.
Tsz-Wo
On Mon, Oct 28, 2024 at 9:15 AM Wei-Chiu Chuang
Congratulations! Thanks everyone for providing high quality works on Apache
Ozone!
Xi, Thanks for rolling out the release!
Tsz-Wo
On Thu, Nov 28, 2024 at 1:03 AM Sammi Chen wrote:
> Xi,
>
> Thank you for leading and driving this release to completion! It's really
> a journey longer than we
> ... Is there any particular reason we want Java 11?
Just want to be more inclusive. Requiring a higher Java version
may exclude more applications. We could be forcing the dependent projects
such as HBase to bump their Java version. Not sure if it is true.
> So for these reasons I think makin
+1
- Verified all checksums and signatures.
- Checked LICENSE and NOTICE.Found that LICENSE-glyphicons.txt and
LICENSE-guava.txt are missing from the ./licenses dir; see the file
list at the end. Should they be copied? Or, should they be removed
from hadoop-ozone/dist?
- Compared the files in
Hi Attila,
Thanks for starting the discussion! Could it be that only Recon requires
Java 21? For Ozone in general, we could change it to require Java 11.
Tsz-Wo
On Fri, Nov 15, 2024 at 12:56 PM Attila Doroszlai
wrote:
> Hi Apache Ozone community,
>
> Ozone currently requires minimum Java 8
Sammi, thanks for fixing the license file copying!
Attila, Sammi, I agree that the issue is minor so I have +1'ed on my vote.
Tsz-Wo
On Thu, Nov 21, 2024 at 1:21 AM Attila Doroszlai
wrote:
> Thanks Ayush, Tsz-Wo, for finding these problems.
>
> > I think it should be OK to use this RC.
>
> I
> 8. Two Follower SCMs shutdown due to state machine failure after SCM
leader
transfer. It's highly suspected to be related with raft log reapply.
Is there a JIRA? If not, please file one. We can debug it together.
Tsz-Wo
On Fri, Apr 25, 2025 at 1:25 AM Sammi Chen wrote:
> Attenders: Pony,
+1 on md over google doc.
> ... Google Docs do not show up in Google searches ...
This is bad for our design docs. How about the other search engines?
Ritest, thanks for bringing this up!
Tsz-Wo
On Tue, Apr 15, 2025 at 1:44 AM Abhishek Pal
wrote:
> Thanks for the proposal Ritesh.
>
> I thi
52 matches
Mail list logo
