Odg: gateway sender queue
Hi, just to remind you on last question: what is your opinion on adding additional option in gfsh command "start gateway sender" to control clearing of existing queues --cleanQueues. This option will indicate, when gateway sender is started, should we discard/clean existing queue, or should we use existing queue. By default it will be to discard/clean existing queue. Best Regards, Mario Šalje: Mario Ivanac Poslano: 8. studenog 2019. 13:00 Prima: dev@geode.apache.org Predmet: Odg: gateway sender queue Hi all, one more clarification regarding 3rd question: "* Could we add extra option in gfsh command "start gateway sender" that allows to control queues reset (for instance --cleanQueues)" This option will indicate, when gateway sender is started, should we discard/clean existing queue, or should we use existing queue. By default it will be to discard/clean existing queue. Best Regards, Mario Šalje: Mario Ivanac Poslano: 7. studenog 2019. 9:01 Prima: Dan Smith ; dev@geode.apache.org Predmet: Odg: gateway sender queue Hi, thanks for answers. Some more details regarding 1st question. Is this behavior same (for serial and parallel gateway sender) in case queue is persistent? Meaning, should queue (persistent) be purged if we restart gateway sender? Thanks, Mario Šalje: Dan Smith Poslano: 5. studenog 2019. 18:52 Prima: dev@geode.apache.org Predmet: Re: gateway sender queue Some replies, inline: * During testing we have observed, different behavior in parallel and > serial gateway senders. In case we manually stop, than start gateway > senders, for parallel gateway senders, queue is purged, but for serial > gateway senders this is not the case. Is this normal behavior or bug? > Hmm, I also think stop is supposed to clear the queue. I think if you are seeing that it doesn't clear the queue, that might be a bug. > * What happens with the queues when whole cluster is stopped and later > started (In our tests with persistent queues, the events are kept)? > Persistent queues will keep all of the events when you restart. > * Could we add extra option in gfsh command "start gateway sender" > that allows to control queues reset (for instance --cleanQueues)? > If stop does clear the queue, would this be needed? It might still be reasonable - I've heard folks request a way to clear running queues as well. -Dan
[REPORT] Apache Geode - November 2019
## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Geode was founded 2016-11-15 (3 years ago) There are currently 104 committers and 52 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - Bill Burcham was added to the PMC on 2019-09-08 - Mario Ivanac was added to the PMC on 2019-09-08 - Bill Burcham was added as committer on 2019-09-09 - Mario Ivanac was added as committer on 2019-09-09 ## Project Activity: - Released Apache Geode 1.10.0 on 2019-09-26. - Released Apache Geode 1.9.1 on 2019-09-06. - Released Apache Geode 1.9.2 on 2019-10-29. ## Community Health: The community is actively contributing to the Apache Geode code base. In the past quarter: - 61 code contributors - 347 issues opened in JIRA - 275 issues closed in JIRA - 434 PRs opened on GitHub - 426 PRs closed on GitHub Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in Austin, Texas, with 500 attendees at the 12 sessions.
Re: Quick turnaround needed, feedback on this DRAFT Nov board report
Thanks Owen. I have revised our report, and you'll see the revised version as I email it to the Apache board. On Wed, Nov 13, 2019 at 11:25 AM Owen Nichols wrote: > We also released 1.9.2 on 2019-10-28 > > > On Nov 13, 2019, at 9:51 AM, Dave Barnes wrote: > > > > +1 LGTM > > > > On Wed, Nov 13, 2019 at 9:49 AM Karen Miller wrote: > > > >> Draft board report for November 2019. Submitting in 2 hours! Quick > >> feedback, please! > >> > >> ## Description: > >> The mission of Apache Geode is the creation and maintenance of software > >> related > >> to a data management platform that provides real-time, consistent > access to > >> data-intensive applications throughout widely distributed cloud > >> architectures. > >> > >> ## Issues: > >> There are no issues requiring board attention at this time. > >> > >> ## Membership Data: > >> Apache Geode was founded 2016-11-15 (3 years ago) > >> There are currently 104 committers and 52 PMC members in this project. > >> The Committer-to-PMC ratio is 2:1. > >> > >> Community changes, past quarter: > >> - Bill Burcham was added to the PMC on 2019-09-08 > >> - Mario Ivanac was added to the PMC on 2019-09-08 > >> - Bill Burcham was added as committer on 2019-09-09 > >> - Mario Ivanac was added as committer on 2019-09-09 > >> > >> ## Project Activity: > >> - Released Apache Geode 1.10.0 on 2019-09-26. > >> - Released Apache Geode 1.9.1 on 2019-09-06. > >> > >> > >> ## Community Health: > >> The community is actively contributing to the Apache Geode code base. In > >> the > >> past quarter: > >> - 61 code contributors > >> - 347 issues opened in JIRA > >> - 275 issues closed in JIRA > >> - 434 PRs opened on GitHub > >> - 426 PRs closed on GitHub > >> > >> Enjoyed great attendance at the Apache Geode Summit held October 7, > 2019, > >> in > >> Austin, Texas. > >> > >
Apache Geode Nov 2019 board report submitted
Here's the text of the board report I submitted (November 2019). Thank you everyone for the quick feedback. ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Geode was founded 2016-11-15 (3 years ago) There are currently 104 committers and 52 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - Bill Burcham was added to the PMC on 2019-09-08 - Mario Ivanac was added to the PMC on 2019-09-08 - Bill Burcham was added as committer on 2019-09-09 - Mario Ivanac was added as committer on 2019-09-09 ## Project Activity: - Released Apache Geode 1.10.0 on 2019-09-26. - Released Apache Geode 1.9.1 on 2019-09-06. ## Community Health: The community is actively contributing to the Apache Geode code base. In the past quarter: - 61 code contributors - 347 issues opened in JIRA - 275 issues closed in JIRA - 434 PRs opened on GitHub - 426 PRs closed on GitHub Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in Austin, Texas, with 500 attendees at the 12 sessions.
Re: Quick turnaround needed, feedback on this DRAFT Nov board report
We also released 1.9.2 on 2019-10-28 > On Nov 13, 2019, at 9:51 AM, Dave Barnes wrote: > > +1 LGTM > > On Wed, Nov 13, 2019 at 9:49 AM Karen Miller wrote: > >> Draft board report for November 2019. Submitting in 2 hours! Quick >> feedback, please! >> >> ## Description: >> The mission of Apache Geode is the creation and maintenance of software >> related >> to a data management platform that provides real-time, consistent access to >> data-intensive applications throughout widely distributed cloud >> architectures. >> >> ## Issues: >> There are no issues requiring board attention at this time. >> >> ## Membership Data: >> Apache Geode was founded 2016-11-15 (3 years ago) >> There are currently 104 committers and 52 PMC members in this project. >> The Committer-to-PMC ratio is 2:1. >> >> Community changes, past quarter: >> - Bill Burcham was added to the PMC on 2019-09-08 >> - Mario Ivanac was added to the PMC on 2019-09-08 >> - Bill Burcham was added as committer on 2019-09-09 >> - Mario Ivanac was added as committer on 2019-09-09 >> >> ## Project Activity: >> - Released Apache Geode 1.10.0 on 2019-09-26. >> - Released Apache Geode 1.9.1 on 2019-09-06. >> >> >> ## Community Health: >> The community is actively contributing to the Apache Geode code base. In >> the >> past quarter: >> - 61 code contributors >> - 347 issues opened in JIRA >> - 275 issues closed in JIRA >> - 434 PRs opened on GitHub >> - 426 PRs closed on GitHub >> >> Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, >> in >> Austin, Texas. >>
Re: Adding GEODE-7412 to 1.11 release
Thanks Udo. > On Nov 13, 2019, at 10:32 AM, Udo Kohlmeyer wrote: > > @Mark, > > According to investigation that has been done, GEODE-7412 is a non-issue.. > Fixed by another ticket, that is already part of /1.11/ and /develop/ > > --Udo > > On 11/8/19 3:35 PM, Mark Hanson wrote: >> Hi, >> >> Can someone give me a known good sha? >> >> I will add it in. >> >> Thanks, >> Mark >> >>> On Nov 8, 2019, at 2:20 PM, Jens Deppe wrote: >>> >>> Hmm, I thought this was implicitly fixed by various build refactorings that >>> went into 1.11.0. I see that we're creating local maven artifacts for >>> geode-pulse-1.11.0.war. The next question is then whether we're actually >>> publishing those. >>> >>> --Jens >>> >>> On Fri, Nov 8, 2019 at 12:56 PM Owen Nichols wrote: >>> +1 > On Nov 8, 2019, at 12:54 PM, Udo Kohlmeyer wrote: > > @Owen, > > I did not specifically check all web archives for this issue. Yes, I *should* have been caught in that ticket. > On 11/8/19 11:03 AM, Owen Nichols wrote: >> I’m curious, how was this missed in https://issues.apache.org/jira/browse/GEODE-7241 < https://issues.apache.org/jira/browse/GEODE-7241> ? >>> On Nov 8, 2019, at 10:56 AM, Udo Kohlmeyer wrote: >>> >>> Hi there Geode Dev, >>> >>> I would like to request that we add https://issues.apache.org/jira/browse/GEODE-7412 < https://issues.apache.org/jira/browse/GEODE-7412> to the 1.11 release. >>> This change is a build change that has crept in since 1.8. The issue that is to be fixed is that the web archive, (geode-pulse) has since 1.8 been uploaded as a jar file to maven central. >>> I would like to fix this by having the WAR artifact being pushed to maven central again. >>> --Udo >>>
Re: Quick turnaround needed, feedback on this DRAFT Nov board report
Could we add a few more details about the Geode Summit? 500 attendees 12 sessions > On Nov 13, 2019, at 9:49 AM, Karen Miller wrote: > > Draft board report for November 2019. Submitting in 2 hours! Quick > feedback, please! > > ## Description: > The mission of Apache Geode is the creation and maintenance of software > related > to a data management platform that provides real-time, consistent access to > data-intensive applications throughout widely distributed cloud > architectures. > > ## Issues: > There are no issues requiring board attention at this time. > > ## Membership Data: > Apache Geode was founded 2016-11-15 (3 years ago) > There are currently 104 committers and 52 PMC members in this project. > The Committer-to-PMC ratio is 2:1. > > Community changes, past quarter: > - Bill Burcham was added to the PMC on 2019-09-08 > - Mario Ivanac was added to the PMC on 2019-09-08 > - Bill Burcham was added as committer on 2019-09-09 > - Mario Ivanac was added as committer on 2019-09-09 > > ## Project Activity: > - Released Apache Geode 1.10.0 on 2019-09-26. > - Released Apache Geode 1.9.1 on 2019-09-06. > > > ## Community Health: > The community is actively contributing to the Apache Geode code base. In the > past quarter: > - 61 code contributors > - 347 issues opened in JIRA > - 275 issues closed in JIRA > - 434 PRs opened on GitHub > - 426 PRs closed on GitHub > > Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in > Austin, Texas.
Re: Release candidate target date...
Oh yes, Thanksgiving! That makes perfect sense. On Tue, Nov 12, 2019 at 5:52 PM Mark Hanson wrote: > What Owen said basically... I prefer to try for an early date and > reschedule to a later date if I must. Aiming for a later date leaves little > window to deal with surprises other than to miss the target date. Its > almost never bad to come in a few days early, but it is rarely good to come > in late. > > Finally, Thanksgiving in the US is very unpredictable for vacations and > thus a few days earlier guarantees more eyes. > > Thanks, > Mark > > Sent from my iPhone > > > On Nov 12, 2019, at 4:09 PM, Owen Nichols wrote: > > > > Could be: > > * not very many fixes have come in, so maybe there’s actually nothing > further we’re waiting for? > > * to give us a better chance of hitting Dec 2 goal, in case it takes > more than one RC? > > * some people might prefer to give feedback against a formal RC rather > than informally against the branch? > > * impact of Thanksgiving? > > > >> On Nov 12, 2019, at 4:05 PM, Alexander Murmann > wrote: > >> > >> I think it's really great to agree on the date by which we want to have > a > >> RC1 early. However, I thought the target release date is beginning of > >> December, which would probably bring us to December 2nd, given the > first is > >> a Sunday. The voting period is 3 days. I would have expected that we'd > >> create the RC around 11/26 (with the caveat that everything looks fine > by > >> then). What's the reasoning behind cutting it so early? > >> > >>> On Tue, Nov 12, 2019 at 3:47 PM Owen Nichols > wrote: > >>> > >>> +1 for cutting RC1 within two weeks of creating the release branch :) > >>> > On Nov 12, 2019, at 3:00 PM, Mark Hanson wrote: > > Hello Geode Dev Community, > > We have a release branch for Apache Geode 1.11.0 - “release/1.11.0”. > >>> People have been voting to pick up fixes and I have been cherry picking > >>> them accordingly. I think it is important that we look forward to a > release > >>> date and I have picked November 19th, 2019 as a time to try for. As > with > >>> any process, if a sufficiently scary issue comes up we will > reschedule, but > >>> this seems like a reasonable date. > > As always, please contact me with any concerns you might have. If no > >>> concerns are raised, we will start voting on the release on November > 20th, > >>> 2019. > > Regards > Mark Hanson > > >>> > >>> > >> > >> -- > >> Alexander J. Murmann > >> (650) 283-1933 > > >
Re: Adding GEODE-7412 to 1.11 release
@Mark, According to investigation that has been done, GEODE-7412 is a non-issue.. Fixed by another ticket, that is already part of /1.11/ and /develop/ --Udo On 11/8/19 3:35 PM, Mark Hanson wrote: Hi, Can someone give me a known good sha? I will add it in. Thanks, Mark On Nov 8, 2019, at 2:20 PM, Jens Deppe wrote: Hmm, I thought this was implicitly fixed by various build refactorings that went into 1.11.0. I see that we're creating local maven artifacts for geode-pulse-1.11.0.war. The next question is then whether we're actually publishing those. --Jens On Fri, Nov 8, 2019 at 12:56 PM Owen Nichols wrote: +1 On Nov 8, 2019, at 12:54 PM, Udo Kohlmeyer wrote: @Owen, I did not specifically check all web archives for this issue. Yes, I *should* have been caught in that ticket. On 11/8/19 11:03 AM, Owen Nichols wrote: I’m curious, how was this missed in https://issues.apache.org/jira/browse/GEODE-7241 < https://issues.apache.org/jira/browse/GEODE-7241> ? On Nov 8, 2019, at 10:56 AM, Udo Kohlmeyer wrote: Hi there Geode Dev, I would like to request that we add https://issues.apache.org/jira/browse/GEODE-7412 < https://issues.apache.org/jira/browse/GEODE-7412> to the 1.11 release. This change is a build change that has crept in since 1.8. The issue that is to be fixed is that the web archive, (geode-pulse) has since 1.8 been uploaded as a jar file to maven central. I would like to fix this by having the WAR artifact being pushed to maven central again. --Udo
Re: Quick turnaround needed, feedback on this DRAFT Nov board report
+1 On Wed, Nov 13, 2019 at 10:06 AM Udo Kohlmeyer wrote: > +1 > > Haven't double checked the numbers, but the rest LGTM > > On 11/13/19 9:49 AM, Karen Miller wrote: > > Draft board report for November 2019. Submitting in 2 hours! Quick > > feedback, please! > > > > ## Description: > > The mission of Apache Geode is the creation and maintenance of software > > related > > to a data management platform that provides real-time, consistent access > to > > data-intensive applications throughout widely distributed cloud > > architectures. > > > > ## Issues: > > There are no issues requiring board attention at this time. > > > > ## Membership Data: > > Apache Geode was founded 2016-11-15 (3 years ago) > > There are currently 104 committers and 52 PMC members in this project. > > The Committer-to-PMC ratio is 2:1. > > > > Community changes, past quarter: > > - Bill Burcham was added to the PMC on 2019-09-08 > > - Mario Ivanac was added to the PMC on 2019-09-08 > > - Bill Burcham was added as committer on 2019-09-09 > > - Mario Ivanac was added as committer on 2019-09-09 > > > > ## Project Activity: > > - Released Apache Geode 1.10.0 on 2019-09-26. > > - Released Apache Geode 1.9.1 on 2019-09-06. > > > > > > ## Community Health: > > The community is actively contributing to the Apache Geode code base. In > the > > past quarter: > > - 61 code contributors > > - 347 issues opened in JIRA > > - 275 issues closed in JIRA > > - 434 PRs opened on GitHub > > - 426 PRs closed on GitHub > > > > Enjoyed great attendance at the Apache Geode Summit held October 7, > 2019, in > > Austin, Texas. > > >
Re: Quick turnaround needed, feedback on this DRAFT Nov board report
+1 Haven't double checked the numbers, but the rest LGTM On 11/13/19 9:49 AM, Karen Miller wrote: Draft board report for November 2019. Submitting in 2 hours! Quick feedback, please! ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Geode was founded 2016-11-15 (3 years ago) There are currently 104 committers and 52 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - Bill Burcham was added to the PMC on 2019-09-08 - Mario Ivanac was added to the PMC on 2019-09-08 - Bill Burcham was added as committer on 2019-09-09 - Mario Ivanac was added as committer on 2019-09-09 ## Project Activity: - Released Apache Geode 1.10.0 on 2019-09-26. - Released Apache Geode 1.9.1 on 2019-09-06. ## Community Health: The community is actively contributing to the Apache Geode code base. In the past quarter: - 61 code contributors - 347 issues opened in JIRA - 275 issues closed in JIRA - 434 PRs opened on GitHub - 426 PRs closed on GitHub Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in Austin, Texas.
Re: Quick turnaround needed, feedback on this DRAFT Nov board report
+1 LGTM On Wed, Nov 13, 2019 at 9:53 AM Dick Cavender wrote: > +1 > > On Wed, Nov 13, 2019 at 9:52 AM Dave Barnes wrote: > > > +1 LGTM > > > > On Wed, Nov 13, 2019 at 9:49 AM Karen Miller wrote: > > > > > Draft board report for November 2019. Submitting in 2 hours! Quick > > > feedback, please! > > > > > > ## Description: > > > The mission of Apache Geode is the creation and maintenance of software > > > related > > > to a data management platform that provides real-time, consistent > access > > to > > > data-intensive applications throughout widely distributed cloud > > > architectures. > > > > > > ## Issues: > > > There are no issues requiring board attention at this time. > > > > > > ## Membership Data: > > > Apache Geode was founded 2016-11-15 (3 years ago) > > > There are currently 104 committers and 52 PMC members in this project. > > > The Committer-to-PMC ratio is 2:1. > > > > > > Community changes, past quarter: > > > - Bill Burcham was added to the PMC on 2019-09-08 > > > - Mario Ivanac was added to the PMC on 2019-09-08 > > > - Bill Burcham was added as committer on 2019-09-09 > > > - Mario Ivanac was added as committer on 2019-09-09 > > > > > > ## Project Activity: > > > - Released Apache Geode 1.10.0 on 2019-09-26. > > > - Released Apache Geode 1.9.1 on 2019-09-06. > > > > > > > > > ## Community Health: > > > The community is actively contributing to the Apache Geode code base. > In > > > the > > > past quarter: > > > - 61 code contributors > > > - 347 issues opened in JIRA > > > - 275 issues closed in JIRA > > > - 434 PRs opened on GitHub > > > - 426 PRs closed on GitHub > > > > > > Enjoyed great attendance at the Apache Geode Summit held October 7, > 2019, > > > in > > > Austin, Texas. > > > > > >
Re: Quick turnaround needed, feedback on this DRAFT Nov board report
+1 On Wed, Nov 13, 2019 at 9:52 AM Dave Barnes wrote: > +1 LGTM > > On Wed, Nov 13, 2019 at 9:49 AM Karen Miller wrote: > > > Draft board report for November 2019. Submitting in 2 hours! Quick > > feedback, please! > > > > ## Description: > > The mission of Apache Geode is the creation and maintenance of software > > related > > to a data management platform that provides real-time, consistent access > to > > data-intensive applications throughout widely distributed cloud > > architectures. > > > > ## Issues: > > There are no issues requiring board attention at this time. > > > > ## Membership Data: > > Apache Geode was founded 2016-11-15 (3 years ago) > > There are currently 104 committers and 52 PMC members in this project. > > The Committer-to-PMC ratio is 2:1. > > > > Community changes, past quarter: > > - Bill Burcham was added to the PMC on 2019-09-08 > > - Mario Ivanac was added to the PMC on 2019-09-08 > > - Bill Burcham was added as committer on 2019-09-09 > > - Mario Ivanac was added as committer on 2019-09-09 > > > > ## Project Activity: > > - Released Apache Geode 1.10.0 on 2019-09-26. > > - Released Apache Geode 1.9.1 on 2019-09-06. > > > > > > ## Community Health: > > The community is actively contributing to the Apache Geode code base. In > > the > > past quarter: > > - 61 code contributors > > - 347 issues opened in JIRA > > - 275 issues closed in JIRA > > - 434 PRs opened on GitHub > > - 426 PRs closed on GitHub > > > > Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, > > in > > Austin, Texas. > > >
Re: Quick turnaround needed, feedback on this DRAFT Nov board report
+1 LGTM On Wed, Nov 13, 2019 at 9:49 AM Karen Miller wrote: > Draft board report for November 2019. Submitting in 2 hours! Quick > feedback, please! > > ## Description: > The mission of Apache Geode is the creation and maintenance of software > related > to a data management platform that provides real-time, consistent access to > data-intensive applications throughout widely distributed cloud > architectures. > > ## Issues: > There are no issues requiring board attention at this time. > > ## Membership Data: > Apache Geode was founded 2016-11-15 (3 years ago) > There are currently 104 committers and 52 PMC members in this project. > The Committer-to-PMC ratio is 2:1. > > Community changes, past quarter: > - Bill Burcham was added to the PMC on 2019-09-08 > - Mario Ivanac was added to the PMC on 2019-09-08 > - Bill Burcham was added as committer on 2019-09-09 > - Mario Ivanac was added as committer on 2019-09-09 > > ## Project Activity: > - Released Apache Geode 1.10.0 on 2019-09-26. > - Released Apache Geode 1.9.1 on 2019-09-06. > > > ## Community Health: > The community is actively contributing to the Apache Geode code base. In > the > past quarter: > - 61 code contributors > - 347 issues opened in JIRA > - 275 issues closed in JIRA > - 434 PRs opened on GitHub > - 426 PRs closed on GitHub > > Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, > in > Austin, Texas. >
Quick turnaround needed, feedback on this DRAFT Nov board report
Draft board report for November 2019. Submitting in 2 hours! Quick feedback, please! ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache Geode was founded 2016-11-15 (3 years ago) There are currently 104 committers and 52 PMC members in this project. The Committer-to-PMC ratio is 2:1. Community changes, past quarter: - Bill Burcham was added to the PMC on 2019-09-08 - Mario Ivanac was added to the PMC on 2019-09-08 - Bill Burcham was added as committer on 2019-09-09 - Mario Ivanac was added as committer on 2019-09-09 ## Project Activity: - Released Apache Geode 1.10.0 on 2019-09-26. - Released Apache Geode 1.9.1 on 2019-09-06. ## Community Health: The community is actively contributing to the Apache Geode code base. In the past quarter: - 61 code contributors - 347 issues opened in JIRA - 275 issues closed in JIRA - 434 PRs opened on GitHub - 426 PRs closed on GitHub Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in Austin, Texas.
Re: [DISCUSS] how to record 1.9.2 release on master
Great, that sounds like a reasonable expectation & also the simplest solution! I cleaned up a few release branches that should have already been deleted. No further action is needed. -Owen > On Nov 13, 2019, at 8:07 AM, Anthony Baker wrote: > > The expectation is that master always points to the latest release (in this > case 1.10.0). There’s a rel/v1.9.2 tag already—what more is needed? We > don’t need the release branch since further patches can be branched from that > tag. IOW, I don’t understand why we should to overwrite master with an older > release. > > Anthony > > >> On Nov 12, 2019, at 6:48 PM, Robert Houghton wrote: >> >> I think we should look at other examples of git-flow merge practices for >> this kind of thing. We can't be the only project that does this. >> >> But I vote for a merge commit >> >> On Tue, Nov 12, 2019, 16:20 Owen Nichols wrote: >> >>> It’s been a few weeks since 1.9.2 release was announced, and there is >>> still no record of it on master. What should we do? >>> >>> A) never record 1.9.2 on master; instead keep the most recent >>> release/1.9.x branch around indefinitely (normally we delete release >>> branches after pushing them to master). >>> B) push 1.9.2 to head of master (on top of 1.10.0). This gives master all >>> of the correct tags, even if they are in release-date order rather than >>> semantic-version order. >>> C) rewrite history (use force-push to insert 1.9.2 onto master in between >>> 1.9.1 and 1.10.0) >>> D) other? >>> >>> If it is generally desirable that checking out the head of master should >>> always give the latest release (by semantic-version order), we could still >>> consider option B, but wait to do it until just before we ship 1.11.0... >>> >>> -Owen >>> On Oct 28, 2019, at 6:51 AM, Jens Deppe wrote: The Apache Geode community is pleased to announce the availability of Apache Geode 1.9.2. Apache Geode is a data management platform that provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high >>> concurrency processing. Geode 1.9.2 contains a number of improvements and bug fixes. - Added the ability to specify that when an asynchronous event queue (AEQ) first starts, event processing should be paused. A `resume` >>> command is provided to start event processing at the desired time. Three gfsh commands were added or modified to support this capability: "create async-event-queue --pause-event-processing", "alter async-event-queue --pause-event-processing", and "resume async-event-queue-dispatcher". >>> See the gfsh command reference in the Geode User Guide for details. - Publish war artifacts for geode-web , geode-web-api and geode-web-management to Maven Central. - Fix compatibility with launching geode-web (admin REST API) when Spring 5.x jars are on the classpath. For the full list of changes please review the release notes: >>> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.9.2 The release artifacts can be downloaded from the project website: http://geode.apache.org/releases/ The release documentation is available at: http://geode.apache.org/docs/guide/19/about_geode.html We would like to thank all the contributors that made the release >>> possible. Regards, Jens Deppe on behalf of the Apache Geode team >>> >>> >
Re: Propose adding GEODE-7400 fix to 1.11 release
FYI, this has been added to the release/1.11.0 branch. Thanks, Mark > On Nov 11, 2019, at 9:42 AM, Jason Huynh wrote: > > +1 > > On Mon, Nov 11, 2019 at 9:41 AM Kirk Lund wrote: > >> I propose merging the fix for GEODE-7400 (merged to develop today) to the >> 1.11 release branch. >> >> My fix for GEODE-7330 (merged to develop in late October) introduced >> GEODE-7400 which is the potential for RejectedExecutionException to be >> thrown within FederatingManager. >> >> Thanks, >> Kirk >> >> commit 3c5a6ccf40b03c345f53f28214513a9d76a1e024 >> Author: Aaron Lindsey >> Date: Mon Nov 11 09:36:24 2019 -0800 >> >>GEODE-7400: Prevent RejectedExecutionException in FederatingManager >> (#4270) >> >>Commit f0c96db73263bb1b3cb04558f2a720d70f43421f changed the >>FederatingManager class so that it reuses the same ExecutorService >>between restarts. After that change, if we start the manager after >>previously starting and stopping it, we get RejectedExecutionException >>because it tries to invoke a task on the same ExecutorService which has >>been shut down. >> >>This commit changes the FederatingManager so that it invokes a supplier >>to get a new ExecutorService each time it is started to prevent the >>RejectedExecutionException. >> >>Co-authored-by: Aaron Lindsey >>Co-authored-by: Kirk Lund >>
Re: [DISCUSS] how to record 1.9.2 release on master
The expectation is that master always points to the latest release (in this case 1.10.0). There’s a rel/v1.9.2 tag already—what more is needed? We don’t need the release branch since further patches can be branched from that tag. IOW, I don’t understand why we should to overwrite master with an older release. Anthony > On Nov 12, 2019, at 6:48 PM, Robert Houghton wrote: > > I think we should look at other examples of git-flow merge practices for > this kind of thing. We can't be the only project that does this. > > But I vote for a merge commit > > On Tue, Nov 12, 2019, 16:20 Owen Nichols wrote: > >> It’s been a few weeks since 1.9.2 release was announced, and there is >> still no record of it on master. What should we do? >> >> A) never record 1.9.2 on master; instead keep the most recent >> release/1.9.x branch around indefinitely (normally we delete release >> branches after pushing them to master). >> B) push 1.9.2 to head of master (on top of 1.10.0). This gives master all >> of the correct tags, even if they are in release-date order rather than >> semantic-version order. >> C) rewrite history (use force-push to insert 1.9.2 onto master in between >> 1.9.1 and 1.10.0) >> D) other? >> >> If it is generally desirable that checking out the head of master should >> always give the latest release (by semantic-version order), we could still >> consider option B, but wait to do it until just before we ship 1.11.0... >> >> -Owen >> >>> On Oct 28, 2019, at 6:51 AM, Jens Deppe wrote: >>> >>> The Apache Geode community is pleased to announce the availability of >>> Apache Geode 1.9.2. >>> >>> Apache Geode is a data management platform that provides a database-like >>> consistency model, reliable transaction processing and a shared-nothing >>> architecture to maintain very low latency performance with high >> concurrency >>> processing. >>> >>> Geode 1.9.2 contains a number of improvements and bug fixes. >>> >>> >>> - Added the ability to specify that when an asynchronous event queue >>> (AEQ) first starts, event processing should be paused. A `resume` >> command >>> is provided to start event processing at the desired time. Three gfsh >>> commands were added or modified to support this capability: "create >>> async-event-queue --pause-event-processing", "alter async-event-queue >>> --pause-event-processing", and "resume async-event-queue-dispatcher". >> See >>> the gfsh command reference in the Geode User Guide for details. >>> - Publish war artifacts for geode-web , geode-web-api and >>> geode-web-management to Maven Central. >>> - Fix compatibility with launching geode-web (admin REST API) when >>> Spring 5.x jars are on the classpath. >>> >>> >>> For the full list of changes please review the release notes: >>> >> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.9.2 >>> >>> The release artifacts can be downloaded from the project website: >>> http://geode.apache.org/releases/ >>> >>> The release documentation is available at: >>> http://geode.apache.org/docs/guide/19/about_geode.html >>> >>> We would like to thank all the contributors that made the release >> possible. >>> >>> Regards, >>> Jens Deppe on behalf of the Apache Geode team >> >>
Restart gateway-receiver
Hi geode dev, After creating gateways senders and receivers between two geode clusters replications is established. After restart gateway receiver, sender will not connect to it until we send some entry from sender to receiver. Is this a normal behavior or a bug? Should geode have some mechanism for checking if connection is established no matter if entry is sent or not? BR, Mario
