Re: 0.2.0 release?
Quick update: TLDR; We need RATIS-227/RATIS-228 (and imho RATIS-229) for the 0.2.0 release. Current Blocker/Patch Available jiras: BLOCKER: RATIS-227 TestRaftWithGrpc.testBasicAppendEntriesWithAllReplication fails --> No patch, yet RATIS-228 Handle zero size log_inprogress file --> Patch available, seems to be ok for me, but not enough experience with the file writing. Please review if you have time. NON-BLOCKER: RATIS-229 GRpcLogAppender should trigger a heartbeat when appendEntries Patch Available -> but "need more testing". Seems to be a real problem which should be included, question is open about the implementation. RATIS-230: Improve gRPC log messages Patch Available -> seems to be ok for me, checkstyle issues RATIS-222 Handle Error exception when Unassigned Variable is tried to get . Patch Available --> I think it should be fixed in different location with fixing the error handling of the arithmetic state machine RATIS-218 Optimize heartbeating in Ratis for Grpc protocol --> Reviewed, response is pending Marton On 04/17/2018 05:35 AM, Tsz Wo Sze wrote: I agreed that RATIS-227 is a blocker. Let me ping Kit for fixing it. Tsz-Wo On Tue, Apr 17, 2018 at 4:53 AM, Elek, Martonwrote: Fair enough, I modified the priority of RATIS-227 to blocker. Let's see if we can get it soon. In the meantime I created a preview version of the release: https://home.apache.org/~elek/ratis-preview (NON OFFICIAL ARTIFACTS!) And requested reviews from the incubator mentors. Hopefully we can start a vote at the end of this week. Marton On 04/16/2018 05:31 PM, Lokesh Jain wrote: I think we can have RATIS-227 in 0.2.0 release as well. There might be a possible bug which needs to be fixed. Thanks Lokesh
Re: [RESULT][VOTE#2] Merge RATIS-5 to a new branch and publish the new site
And finally: https://ratis.incubator.apache.org/ is up and running. The source code is at the asf-site-source branch and the html files are commited to the asf-site branch. Thank you all the help, Marton On 01/20/2018 10:37 AM, Elek, Marton wrote: Thank you very much your votes. The Vote is passed with: * 7 of +1 vote (thx Anu, Jitendra, Mukul, Tsz-Wo, Lokesh, Shashikant, Arpit) * and without -1 vote. I will merge the source code and the rendered version to the proposed branches and open the infra ticket to publish the site. Marton ps: I read a lot of asf policies to understand binding/non-binding in case of an incubator project. Fortunately this vote is passed anyway. My understanding is that for an incubator merge vote it's not needed to calculate bindig/non-binding separated but any commiter could veto the merge. Anyway, thanks again the review and vote for all of you. On 01/18/2018 08:12 PM, Arpit Agarwal wrote: +1 On 1/15/18, 4:58 AM, "Marton, Elek" <e...@apache.org> wrote: Hi, We got valuable feedback from the incubator mailing list an improved the proposed site according to the apache guidelines. So I start a new Vote to merge it. Please have a final look to the proposed web site and VOTE if you agree to publish it. As a reminder: * Rendered site is here: https://elek.github.io/ratis-site/ * Source is on the RATIS-5 branch * both the rendered and source version is uploaded to RATIS-5. This VOTE will open for 5 days and will end of 20th of January. Thanks, Marton FTR. The original vote thread started here: http://mail-archives.apache.org/mod_mbox/ratis-dev/201712.mbox/browser
[VOTE#2] Merge RATIS-5 to a new branch and publish the new site
Hi, We got valuable feedback from the incubator mailing list an improved the proposed site according to the apache guidelines. So I start a new Vote to merge it. Please have a final look to the proposed web site and VOTE if you agree to publish it. As a reminder: * Rendered site is here: https://elek.github.io/ratis-site/ * Source is on the RATIS-5 branch * both the rendered and source version is uploaded to RATIS-5. This VOTE will open for 5 days and will end of 20th of January. Thanks, Marton FTR. The original vote thread started here: http://mail-archives.apache.org/mod_mbox/ratis-dev/201712.mbox/browser
Re: ratis website proposal
Thanks again, We addressed all the issues. (the developer specific subpage will be created later, we don't have enough content, yet. We plan to add more documentation in the next phase.). If no more suggestions/objections we will restart the vote on the ratis dev list. Thanks your help, Marton On 01/04/2018 02:22 PM, sebb wrote: On 4 January 2018 at 01:04, Justin Mcleanwrote: Hi, You may want to change the wording under the Source link as you have develop is master it could be seen as you are distributing unofficial code to users there. Just add some words to the effect that this is for development use only and not intended for use by the general public and are not part of an official release checked by the PMC. IMO it would be better to have some pages which are clearly aimed at developers and put such links there. Some other nits: "higly customizable" => "highly customizable" However it might be more accurate to say 'fully' (are there aspects that are not customisable?) --- quote --- Raft is a easily understandable consensus algorithm to manage replicated log. Apache Ratis could be used in any Java application where a state should be replicated between multiple instances. --- quote --- 'replicated log' does not read well. Does it mean 'replicated log files' or ' replicated logging' or something else? I'm not sure how 'log' relates to 'a state'? Also 'a state' should probably be 'state' as the former could imply a single state. Still some mentions of 'java' "Start three Ratis server" => "Start the Ratis server" ? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
contribution
Hi, I would like to contribute to Ratis. I have two proposals: 1. I would like to create and register JMX beans for every RaftServerImpl to display at least the current leader, term, index,... I would like to show this information from the (under devepolment) Ozone web ui interfaces. 2. I would like to add a simple Server and Client class to the example project. Currently it could be tested only from unit test. I think it would be more easily to try out ratis by starting standalon example servers with `java -jar...`. (And check on the JMX interface, if everything is fine...) Please comment my ideas, and if agree, add my user (https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elek) to the contributors group. Thanks Marton