Re: Proposal to backport GEODE-8167

+1 > On May 21, 2020, at 8:51 AM, Owen Nichols wrote: > > Some automated scans have flagged Geode Pulse as potentially containing > “high" security vulnerability CVE-2020-5407. > > Analysis shows that this saml vulnerability is not applicable to Geode Pulse. > > It is low risk to bump the spr

Re: [PROPOSAL]: GEODE-8150 into support/1.13

+1 thanks Juan > On May 21, 2020, at 8:12 AM, Ju@N wrote: > > Hello devs, > > I'd like to propose bringing *GEODE-8150 [1] *to the *support/1.13* branch. > The ticket is basically to revert the upgrade of the *classgraph* [2] > library, we found some performance issues that are not addressed ev

Re: 1.13 potential change

https://github.com/apache/geode/pull/5110 Sorry, I’m bad at emailing today. On May 15, 2020, at 4:28 PM, Donal Evans mailto:doev...@pivotal.io>> wrote: Is there a link to the PR in question? I don't see anything on GitHub. On Fri, May 15, 2020 at 4:23 PM Anthony Baker

1.13 potential change

Whoops, this got stuck on the wrong thread. Resending. We’re continuing to investigate some compatibility issues; there may be further changes needed. Anthony > On May 15, 2020, at 11:46 AM, Anthony Baker wrote: > > Barry and I tossed up a draft PR to fix a problem in sess

Re: [DISCUSS] enable GitHub PR blocking on API breaking changes

Barry and I tossed up a draft PR to fix a problem in session state replication with Tomcat. If we can get this completed I’d like to include it with v1.13.0. I believe our tests will fail with any version of Tomcat after 9.0.21. Anthony > On May 15, 2020, at 1:27 AM, Ju@N wrote: > > +1 >

Re: [DISCUSS] Adding Google Analytics to our website

Unfortunately not. There doesn’t seem to be a recovery option that worked for me. Anthony > On May 6, 2020, at 3:29 PM, Alexander Murmann wrote: > > Anthony, thank you for looking into this! Did you have any luck recovering > the account? > > On Mon, May 4, 2020 at 12:0

Re: [DISCUSS] Adding Google Analytics to our website

We may be able to use the account from the ApacheGeode YouTube channel. If not, I would suggest creating a google account whose creds are managed by the PMC. Anthony > On May 4, 2020, at 11:57 AM, Alexander Murmann wrote: > > Seems like nobody has objections to adding this. > > Google An

Re: Handling packet drop between sites

TCP behaves really poorly in the face of significant packet loss. You can look into tcp_retries1 and tcp_retries2 [1] for some explanations and tuning. Eventually, TCP will give up attempting to deliver a packet but this may take up to 30min depending on configuration. IIRC, it’s only at that

Re: [DISCUSS] Publish Builds, not Snapshots

ton wrote: > > @anthony > /develop would say 1.13.0-build.230 (as of this morning). > Once cut, /release/1.13 would say 1.13.0-build.231, and /develop would > switch to 1.14.0-build.1. > > gfsh would return that full value. That is the artifact version. > > On Mon, A

Re: [DISCUSS] Publish Builds, not Snapshots

If I build the /develop branch and run `gfsh version` what will it print? If I build the soon-to-be /release/1.13 branch and run `gfsh version` what will it print? Anthony On 4/27/20, 4:32 PM, "Robert Houghton" wrote: The artifact would change from "1.13.0-SNAPSHOT" to "1.13.0-build.123

Re: [DISCUSS] Publish Builds, not Snapshots

@Robert, can you show some examples of what the build number would be under this proposal? Does 1.13.0-SNAPSHOT become 1.13.0.N where N increments every build? Seems reasonable. Since the consumers of pre-release artifacts are either a) this project or b) close related projects for integratio

Re: Proposal to include fix for GEODE-8020 in support/1.12

+1 > On Apr 27, 2020, at 9:14 AM, Kirk Lund wrote: > > +1 > > On Mon, Apr 27, 2020 at 9:12 AM Bruce Schuchardt > wrote: > >> commit ec8db54ad7f342542762beb8f3e912dff44e3a53 (HEAD -> develop, >> origin/develop) >> >> Author: Bruce Schuchardt >> >> Date: Mon Apr 27 09:07:16 2020 -0700 >>

Re: Proposal to restore Pulse logging in support/1.12

+1 > On Apr 24, 2020, at 2:46 PM, Dale Emery wrote: > > During the cleanup of the gradle build and logging, the Pulse webapp lost its > slf4j implementation. As a result, Pulse stopped writing log files. > > I’ve restored Pulse logging in the develop branch. > > I would like to restore it in

Re: [VOTE] Using Github issues and wiki for geode-kafka-connector project

gt; Blake > > > On Thu, Apr 23, 2020 at 8:50 AM Anthony Baker wrote: > >> Naba, do you have any updates to share? I’m curious if you have found >> this useful compared to JIRA. >> >> Also, I noticed that geode-kafka-connector also has a GitHub wiki. How >&

Re: [VOTE] Using Github issues and wiki for geode-kafka-connector project

Naba, do you have any updates to share? I’m curious if you have found this useful compared to JIRA. Also, I noticed that geode-kafka-connector also has a GitHub wiki. How does that compare with centralizing our information in the ASF confluence wiki? Thanks, Anthony > On Mar 21, 2020, at

Re: Switching default branch in .net core repo

Please do, this will match our default approach to development (gitflow-ish). +1 Anthony > On Apr 23, 2020, at 7:35 AM, Blake Bender wrote: > > Good morning, > > We created a repo yesterday for the .net core client work, and the default > branch out of the gate is set to master. I'd like to

Re: About Geode rolling downgrade

Anil, let me see if I understand your perspective by stating it this way: If cases where 100% uptime is a requirement, users are almost always running a disaster recovery site. It could be active/active or active/standby but there are already at least 2 clusters with current copies of the data.

Re: Data ingestion with predefined buckets

Steve, Have you looked at grouping your putAll() requests into groups that align to Geode’s buckets? In your application code, you can determine the hash for each data item and self-partition the entries. This allows you to send the requests on separate threads in parallel while optimizing ne

Re: Reconfiguring our notifications and more

JIRA’s to PR’s) but at least it directs the notifications to the right ML. Anthony > On Apr 21, 2020, at 8:54 AM, Anthony Baker wrote: > > I’d like a quick round of feedback so we can stop the dev@ spamming [1]. > > ASF has implemented a cool way to give projects control of

Reconfiguring our notifications and more

I’d like a quick round of feedback so we can stop the dev@ spamming [1]. ASF has implemented a cool way to give projects control of lots of things [2]. In short, you provide a .asf.yml in each and every GitHub repo to control lots of interesting things. For us the most immediately relevant are

Re: GitHub notifications?

Filed https://issues.apache.org/jira/browse/INFRA-20156 <https://issues.apache.org/jira/browse/INFRA-20156>. This hit other projects as well. Anthony > On Apr 20, 2020, at 9:10 AM, Nicholas Vallely wrote: > > No, but it's annoying:) > > On Mon, Apr 20, 2020 at 7:

GitHub notifications?

Hmmm, it looks like GitHub notifications are coming to dev@ instead of notifications@. Did anyone request this change? Anthony

Re: [Discuss] Cache.close synchronous is not synchronous, but code still expects it to be....

Thanks Kirk, that’s a really helpful description. As far as expectations go, I agree with John. If a user: - creates a cache - closes the cache - checks the isClosed flag - and is unable to create a new cache in some cases That sounds like a bug. Preventing the early exit sounds like a promis

Re: Website refresh (was Re: [DISCUSS] Adding Google Analytics to our website)

Bob, Your ideas are welcome! I do like the idea of an aggregation point for Geode content. Our past experience with the Apache JRoller blog site was…not the best. We do have some content aggregated in the wiki [1] but it’s not a great content platform either. My main concerns are a) ensurin

Website refresh (was Re: [DISCUSS] Adding Google Analytics to our website)

Bob, I think a refresh of the Geode website is a great idea. I look forward to hearing more of your ideas. I’ve included a link below [1] to provide context on ASF policies around websites. Thanks, Anthony [1] https://www.apache.org/foundation/marks/pmcs#introduction

Re: JGroups vulnerabilty

Thanks for asking Mario. Note that if you want to discuss a security topic prior to public disclosure you can use priv...@geode.apache.org . Anthony > On Apr 7, 2020, at 12:04 PM, Mario Kevo wrote: > > Hi, > > > I was trying to understand whether Geode is

Re: Proposal to bring GEODE-7941 to support/1.12

+1 to backport > On Apr 6, 2020, at 8:54 AM, Owen Nichols wrote: > > Recently some Geode users have expressed concern that shiro-1.4.1.jar is > getting flagged for critical security vulnerability CVE-2020-1957. > > Analysis shows that Geode does not use Shiro in a manner that would expose > t

In progress RFC's?

I was reviewing the list of RFC’s stil under discussion and noticed that the following may need to be moved to a different status: Classloader Isolation [1] - Udo Logging to standard out [2] - Jake Replace singleton PoolManager with ClientCache scoped service [3] - Dan Certificate based authoriza

Re: [DISCUSS] Replace UDP messaging for membership with TCP

Echo’ing my comment here: When we move from a reliable UDP implementation to one based on TCP, we need to think about how to provide reliability on top of TCP. If you dig into TCP, you’ll find that it tries really hard (sometimes up to 15 minutes!!) but doesn’t guarantee message delivery. Doe

Re: Welcome!

More good news! Alexander Murmann and Mark Hanson have joined the Geode PMC. Welcome! Thanks for your contributions to the project and we're looking forward to even more :-) Anthony On Fri, Mar 20, 2020 at 5:21 PM Anthony Baker wrote: > > Over the last few months the Geode PMC

Re: [VOTE] Apache Geode 1.12.0.RC4

+1 Things I checked: - expected files present - hashes and signatures present and valid - geode, geode-benchmarks, and geode-examples build from source - no binaries present in source distributions - verified that geode source and binary distributions have the correct SHA's - able to create a clus

Re: [VOTE] Apache Geode 1.12.0.RC3

s/commit/d3cc0b70884eef7c82fec1a1a284b8250958aac2 > >> On Mar 26, 2020, at 5:14 PM, Anthony Baker wrote: >> >> Ernie, >> >> If you’re planning to spin a new RC can you send a [CANCEL] to let us know? >> I’m mid-way through my review of RC2 :-) >>

Re: [VOTE] Apache Geode 1.12.0.RC3

Ernie, If you’re planning to spin a new RC can you send a [CANCEL] to let us know? I’m mid-way through my review of RC2 :-) One problem I see is the inclusion of this jar file in a source distribution: 🔌 ⌛️ in geode/ › tar tvf 1.12.0.RC3/apache-geode-examples-1.12.0.tar.gz| grep jar -rw-r--

Re: [VOTE] Apache Geode 1.12.0.RC1

e [1]. > > [1] https://jenkins.spring.io/job/spring-data-geode/job/master-next/ > > > On Thu, Mar 26, 2020 at 10:28 AM Anthony Baker wrote: > >>> >>> iii) As long as we need to make an RC2 anyway, I personally feel that it >> would be nice to align geode-nati

Re: [VOTE] Apache Geode 1.12.0.RC1

> > iii) As long as we need to make an RC2 anyway, I personally feel that it > would be nice to align geode-native to its recent milestone > (build/v10.1.0-build.254 / commit hash 35fcb1a66). The current release > branch is about half-a-dozen fixes behind this milestone. I’m not seeing the mi

Re: [ANNOUNCE] Github Wiki and Issus are now activated on geode-kafka-connector

Please report back in a few weeks so we can all join you over there :-) Anthony > On Mar 24, 2020, at 2:07 PM, Jason Huynh wrote: > > Awesome, thanks for doing all the leg work! > > On Tue, Mar 24, 2020 at 1:42 PM Nabarun Nag wrote: > >> Hi, >> >> Issues are wiki pages are now active on t

Re: 2020 Apache Geode Summit - Call for Papers!

Bob asked me to share an updated link for submitting a talk. Please use this one instead: https://forms.gle/4C9t9VAsQLVuQuPF6 <https://forms.gle/4C9t9VAsQLVuQuPF6> Thanks, Anthony > On Mar 19, 2020, at 3:35 PM, Anthony Baker wrote: > > Thanks for sharing Bob! I highly e

Re: [VOTE] Using Github issues and wiki for geode-kafka-connector project

Check out [1] for a list of projects that are moving to GitHub issues. As long as the PMC approves, INFRA will support the switch. (Side note: kinda ironic that you have to file a JIRA to move to GitHub issues :-) +1 for experimenting with the geode-kafka-connector repo. Once we see how that

Welcome!

Over the last few months the Geode PMC has invited the following people as new committers and PMC members. We’ve been remiss in officially recognizing your new status, but welcome aboard! Thanks so much for your contributions to the project and we're looking forward to seeing more great things to

Re: 2020 Apache Geode Summit - Call for Papers!

Thanks for sharing Bob! I highly encourage you to submit a talk and/or plan on attending. We always see lots of users, expert practitioners, and project committers at this event. Related, the CFP for ApacheCon NA is also open [1]. Submit your talk there as well! Thanks, Anthony [1] https:

[CVE-2019-10091] Apache Geode SSL endpoint verification vulnerability

CVE-2019-10091 Apache Geode SSL endpoint verification vulnerability Severity: Medium Vendor: The Apache Software Foundation Versions Affected: Apache Geode 1.9.0 Description: When TLS is enabled with ssl-endpoint-identification-enabled set to true, Apache Geode fails to perform hostname verific

Re: [DISCUSS] RFC: Shipping Geode patch releases

Based on the consensus in this thread, we will move forward with this proposal. We can work out the exact mechanics after we release v1.12.0 and move that into a support mode. Thanks for all the feedback. Anthony On Fri, Feb 21, 2020 at 5:30 PM Anthony Baker wrote: > > Hi everyone, &

Re: Request access to JIRA

Welcome Jakov! You’re all set. Please let us know if you have questions, happy to help out! Anthony > On Mar 13, 2020, at 4:50 AM, Jakov wrote: > > Hi Geode Dev, > > Could you please give me access to JIRA, so I could assign to tickets? > My JIRA username is "jvarenina". > > BRs, > > Jak

Re: RFC - Client side configuration for a SNI proxy

w Udo asked >> for Friday (and Joris +1'd it), but since this is a small RFC, we'd like to >> try to close it by Wednesday, March 11, ok? >> >> On Mon, Mar 9, 2020 at 10:39 AM Jacob Barrett wrote: >> >>> I raised similar concerns as a comment in the RFC.

Re: RFC - Client side configuration for a SNI proxy

Given this new API: setPoolProxy(ProxyType type, String proxyAddress) The ProxyType enum seems to be a look ahead at supporting other kinds of proxies. What is your thinking about using the enum vs specific named API’s (e.g. setPoolProxyWithSNI). Currently the definition of the proxyA

Re: Let's Deprecate the SECURITY_UDP_DHALGO Configuration Property

I don’t think regressed is the right word. There was an effort to harden our udp p2p traffic using encryption based on a DH key exchange. I’m not clear on how much that approach actually improved the security of data in motion. And I don’t believe it saw much if any use in practice. Anthony

Re: [PROPOSAL] eliminate file count loophole in PR StressNewTest

What percentage of PR’s are currently subject to the 25 test file rule? How many would be subject to the concourse timeout? I’d like to understand the scope of the impact for this change. Anthony > On Mar 1, 2020, at 8:58 AM, Owen Nichols wrote: > > Impossible, no. Inconvenient, perhaps, bu

Re: Contributor Access Request

Welcome Derrick! Please shout out if you need any help. Anthony > On Feb 28, 2020, at 12:53 PM, Owen Nichols wrote: > > Welcome Derrick, you should have access to Geode Jira now > > https://issues.apache.org/jira/projects/GEODE/issues > > >> On Feb 26, 2020, at 8:41 AM, Derrick Anderson

Re: Discussions about concerns over User API changes

If I run the japi-compliance-checker [1] against the 1.12 release branch and develop this change pops up as a binary incompatibility. As Owen noted, this would require recompilation to avoid NoSuchMethod errors. One effect this could have is that a library built on top of Geode (e.g. Spring) w

Re: [DISCUSS] RFC: Shipping Geode patch releases

release-1-13-0-main" pipeline, we would >>>>> instead create "apache-release-1-13-main" >>>>> iii. Instead of cleaning up the pipeline and branch after 1.13.0 was >>>>> released, we could keep it around for 9 months and re-use it for >>&

Re: [DISCUSS] RFC: Shipping Geode patch releases

l/v1.9.1 tag), then clean up >>> afterwards so no unattended pipelines or branches linger. >>> >>> The rotating release manager role has been a hallmark of the Geode >>> community process, so I hope this proposal will not dissuade anyone >>> interested

[DISCUSS] RFC: Shipping Geode patch releases

Hi everyone, I'd like to propose shipping patch releases of Geode as a way to improve our engagement and support of our user community. Please review the details in the linked RFC [1] and kindly offer your thoughts in this thread. Thanks, Anthony [1] https://cwiki.apache.org/confluence/display

Re: privacy protection

If you want to encrypt values at the client, you might want to check out this talk: https://springoneplatform.io/2018/sessions/implementing-pii-encryption-with-pdx-serialization Anthony > On Jan 21, 2020, at 10:45 AM, Michael Oleske wrote: > > Something to consider is what scenarios do you wa

Re: enable-time-statistics

Read that as “As of geode 1.9.0 …”. Anthony > On Jan 10, 2020, at 1:19 PM, Jacob Barrett wrote: > > The biggest impact was in recording all the additional stats in the old > blocking stats implementation. As of 9.8 the stats internals are mostly > non-blocking. Enabling time stats has very li

Review #4537

I’m looking for a +1 (or other feedback) on https://github.com/apache/geode/pull/4537 if anyone has cycles today. Thanks! Anthony

Re: [VOTE] Apache Geode 1.11.0.RC4

+1 Checked: - Signatures are good - SHA’s are good - geode, geode-native builds from source - reviewed dependency changes Fix for next release: - Include the geode-benchmarks source code with the release artifacts. - Update geode-assembly/src/main/dist/LICENSE to remove obsolete references to:

Re: [DISCUSS] Proposal to require linear commit history on develop

Whether we are talking about the geode/ repository or the geode-native/ repository we are all one GEODE community. The idea of a native client team may matter in some contexts but in this space we are all GEODE contributors. Adopting a common approach across our repos will make it easier for ne

Re: [DISCUSS] Adding a couple user APIs dealing with RegionFactory.

Mark, Can you share how the API changes will help the user? Thanks, Anthony > On Dec 11, 2019, at 2:57 PM, Mark Hanson wrote: > > Hi All, > > There was a suggestion that since I am making a couple user visible API > changes that I might want to ask the dev list. > > Basically I was migra

Re: New geode-gfsh module

Did the class path in geode-dependencies.jar change? If so, that might also affect applications that relied on the those (spring) jars being available on the class path. Of course, they can fix that by explicitly injecting the applications dependencies into the class path as needed. Anthony

Re: [VOTE] Fix bad-merge of GEODE-7488

Clearly the right thing to do is fix it. VOTE not needed IMO. Anthony > On Nov 22, 2019, at 11:55 AM, Robert Houghton wrote: > > I was overzealous in a merge to Geode, and got us into a chicken-and-egg > issue for PRs and reverts. Calling a vote to override the GitHub merge > button restricti

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 a

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

Re: Update geode-native-build image as part of release process

Thanks Alberto! Maybe as a future enhancement we should consider extending the geode-native-build image from the geode image to make this simpler. Anthony > On Nov 11, 2019, at 2:42 AM, Alberto Bustamante Reyes > wrote: > > Done! I have updated the wiki adding the steps to update the Docker

Re: Jira permission to assign myself

Welcome Szu-Yu Lo! Please reach out if you have any questions :-) Anthony > On Oct 31, 2019, at 1:30 PM, Szu-Yu Lo wrote: > > Thank you so much > > On Thu, Oct 31, 2019 at 2:19 PM Dan Smith wrote: > >> Hi Szu-Yu Lo, >> >> You should have access now. Thanks for being interested in contribu

Re: Special certificates for multisite

Just checking, is anyone familiar enough with SSL to comment on the proposed change? Anthony > On Oct 29, 2019, at 2:44 AM, Mario Ivanac wrote: > > Hi, > > We are trying to find a solution for an situation we have. Below is the > explanation of the issue, as well as a proposed way forward.

Re: The 1.11.0 branch we be cut on November 4th, 2019.

Heads up, I’m planning to merge a bunch of dependency updates today. > On Oct 28, 2019, at 4:32 PM, Mark Hanson wrote: > > Please ensure that your changes are in November 3rd, 2019 at the latest. I > will pick the SHA of the first successful build on November 4th, 2019. > > > If you realize y

Re: [DISCUSS] Blocking merge button in PR

+1, very well said Anthony > On Oct 21, 2019, at 11:05 AM, Nabarun Nag wrote: > > > > *Reiterating the proposal:* > Github branch protection rule for : > - at least one review > - Passing build, unit and stress test. > > > In our opinion, no committer would want to check-in code with failin

Re: [DISCUSS] Support For LTS Version Of Geode

I think LTS implies a lot of things I’m not sure about yet. I suggest we keep the 1.9.x release line going to help “Spring Data for Apache Geode” on an as needed basis and see how it goes. Anthony > On Sep 30, 2019, at 6:32 PM, John Blum wrote: > > 1 more thing... > > I am also not saying

Re: Question about rolling back a Geode upgrade

ems to solve like how to do the switch between >> systems and how to assure the data consistency among them. >> >> I was thinking that in many cases it might be possible to support a >> rolling downgrade similar to the rolling upgrade given that the rolling >> upgrade alread

Re: How to post-process data from Geode backup

Hmmm, good question. If I’m reading the code right we skip exporting PDX types from an offline disk store (because the cache is closed). Since the export doesn’t contain any PDX type definitions, they won’t get recreated during an import. You could verify this by running “java org.apache.geo

Re: [DISCUSS] GEODE-7241 - make Jar not War?

at patch release is already discussed to backport GEODE-7121. > > --Udo > > On 9/25/19 10:53 AM, Anthony Baker wrote: >> Thanks for the reminder. If these files are required to start a geode >> member, I agree they should be published artifacts. Perhaps there’s a >>

Re: [DISCUSS] GEODE-7241 - make Jar not War?

Thanks for the reminder. If these files are required to start a geode member, I agree they should be published artifacts. Perhaps there’s a better way to pull them in…but this seems like the best option for now. Anthony > On Sep 25, 2019, at 10:22 AM, Udo Kohlmeyer wrote: > > @Anthony. Tic

Re: [PROPOSAL] adding java-jq to GEODE dependency for testing

Sounds good, thanks for the heads up. Anthony > On Sep 25, 2019, at 8:37 AM, Jinmei Liao wrote: > > Management rest api wants to add some default jq selector to the swagger > api docs so that the downstream client tool can use it as a starting point > to filter/format the json response to a mo

Re: [DISCUSS] GEODE-7241 - make Jar not War?

Udo, Can you update GEODE-7241 to help us understand the reason why we need to publish geode-web* WARs to maven? I get that we used to do this but I can’t recall why we choose that approach. There is one request for Pulse on maven (GEODE-6208). Anthony > On Sep 24, 2019, at 3:44 PM, Udo Ko

Re: New geode-log4j module

Great writeup, thanks for sharing Kirk! Anthony > On Sep 24, 2019, at 10:24 AM, Kirk Lund wrote: > > All classes that use *log4j-core* have now moved to the new module > *geode-log4j > *on develop. The default log4j2.xml configuration file for Geode Locators > and Servers has also moved to ge

Re: [VOTE] Apache Geode 1.10.0.RC2

It worked for me…? > On Sep 23, 2019, at 12:38 PM, Aaron Lindsey wrote: > > Does this happen for anyone else?

Re: [VOTE] Apache Geode 1.10.0.RC2

+1 Reviewed: - Signatures and hashes - LICENSE and NOTICE - No binaries in source distribution - Builds from source Quibbles: - Let’s include geode-benchmarks/ next release - It would be more awesome if geode-native extracts into a directory with a versioned name (e.g. apache-geode-native-1.

Re: Question about rolling back a Geode upgrade

Have you considered using a blue / green deployment approach? It provides more flexibility for these scenarios though the infrastructure cost is high. Anthony > On Sep 23, 2019, at 5:59 AM, Alberto Gomez wrote: > > Hi, > > Looking at the Geode documentation I have not found any reference to

Re: resource manager requirements & recommendations

n or critical > thresholds, with CMS, these percentages would be a % of "Tenured" heap size. > For G1GC, they would be a % of "Total" heap size, because as you may realize, > G1GC doesn't have a max Eden space or max Tenured space." > > > ___

Re: Propose including GEODE-7178 in 1.10

gt;> If there is consensus from the Geode community that your proposed change >>> satisfies the “critical fixes” rule, I will be happy to bring it to the >>> 1.10.0 release branch. >>> >>> Due to the complexity of this change, could please open a PR against >>>

Re: Propose including GEODE-7178 in 1.10

+1 yes please! > On Sep 12, 2019, at 10:11 AM, Michael Oleske wrote: > > Hi Geode Devs! > > I'd like to propose including the fix for GEODE-7178. This resolves an > issue that Ivan (https://markmail.org/message/dwwac42xmpo4xb2e) ran into in > 1.10 RC1. > > SHA: 91176d61df64bf1390cdba7b1cdc2b4

Re: Question about excluding serialized classes

I think the Decorator approach you outlined could have other impacts as well. Would I still be able to see specific function executions in statistics or would they all become “TImingFunction”? Anthony > On Sep 11, 2019, at 12:00 PM, Aaron Lindsey wrote: > > Thanks for your response, Dan. >

Re: resource manager requirements & recommendations

The challenge with designing a good approach for managing heap use in Java is that we *can’t* know how much of the current heap use is really garbage. That means that it can be really easy to evict too much or too little data. With the CMS engine there are tuning parameters like occupancy fract

Re: [VOTE] Apache Geode 1.10.0.RC1

un ./gradlew spotlessApply independently before the build. >> >> Regards >> Naba >> >> >> On Fri, Sep 6, 2019 at 8:53 AM Anthony Baker wrote: >> >>> This seems to be a simple change to catch IllegalStateException instead >> of >>>

Re: [VOTE] Apache Geode 1.10.0.RC1

g.ClassLoader.loadClass(ClassLoader.java:357) ... 112 more > On Sep 6, 2019, at 8:44 AM, Anthony Baker wrote: > > I ran into a problem while checking the release candidate. When I try to > build from source I get this error: > > A problem occurred evaluating projec

Re: [VOTE] Apache Geode 1.10.0.RC1

ct, but the gradle scripts that use the git plugin aren’t catch that exception like they used to do (works on 1.9.1). Since the source archive is the official release and I can’t build it, I”m voting -1. I would change my vote if we can fix this. Anthony > On Sep 6, 2019, at 8:19 AM, Antho

Re: [VOTE] Apache Geode 1.10.0.RC1

I think we should extend the vote in order to understand this issue better. Anthony > On Sep 6, 2019, at 12:41 AM, Ivan Godwin wrote: > > Hello, > > I don't know that this will be cause to hold anything up, but geode-native > has two integration tests failing when trying to perform Region::re

Re: [VOTE] Apache Geode 1.9.1.RC3

isfaction, would you > like to revise you vote before I record the final tally? > >> On Sep 3, 2019, at 3:38 PM, Anthony Baker wrote: >> >> Yep, I also see that apache-geode-native-1.9.1-src.tar.gz is empty. >> >> -1 until that is fixed. >> >>

Re: [VOTE] Apache Geode 1.9.1.RC3

Yep, I also see that apache-geode-native-1.9.1-src.tar.gz is empty. -1 until that is fixed. Anthony > On Sep 3, 2019, at 2:09 PM, Dan Smith wrote: > > It looks like the native source is missing from this RC? There is a tar > file, but it is emply if you try to unzip it. > > -Dan > > On Fri,

Reviewing a release

Friendly reminder: it’s really helpful when you vote for a release to briefly convey the things that you’ve checked. Here’s a good example: https://lists.apache.org/thread.html/de1417694245addeb18ff8559b1832face884ad45da7cba49b6d543c@%3Cdev.geode.apache.org%3E Anthony

Re: [VOTE] Apache Geode 1.9.1 RC1

I see there’s a VOTE thread for 1.9.1. Do you suggest to -1 that release candidate? Anthony > On Aug 29, 2019, at 8:53 AM, Bruce Schuchardt wrote: > > I also missed this vote email. Dan is right that creating the v1.9.1 Version > instance was unnecessary. I don't think it hurts anything

Re: [DISCUSS] what region types to support in the new management rest api

Just catching up on this thread so take it FWIW. The “new management API” is intended to become the one-and-only way to configure the system. That means that eventually cache.xml, gfsh, existing API’s, etc. will only be able to configure features supported by this new API. I think the implica

Re: Updating geode-native-build docker image

Done! > On Aug 27, 2019, at 10:20 AM, Ivan Godwin wrote: > > Anthony, > > I would like access to the geode docker account. My docker username is > igodwin. > > Ivan > > On Wed, Aug 7, 2019 at 3:54 PM Anthony Baker wrote: > >> Committers can reques

Re: [DISCUSS] Release Geode 1.9.1 with logging improvements

gt; decision to move forward with 1.9.1 is reached by 3pm PDT Wed Sep 4, I will > dismantle the current 1.9.1 branch, pipeline and nexus staging repo and > remove 1.9.1 from the release notes wiki. > > -Owen > > >> On Aug 18, 2019, at 7:52 AM, Anthony Baker wrote: >

Re: [DISCUSS] Release Geode 1.9.1 with logging improvements

Yep. Get a release manager, identify and cherry pick all the changes, then do the release. Anthony > On Aug 16, 2019, at 4:21 PM, Kirk Lund wrote: > > Does anyone know what the next step is? Do we need a release manager to > proceed? > >> On Tue, Aug 13, 2019 at 1:57 PM John Blum wrote: >>

Re: Propose fix for 1.10 release: Export offline data command failed with EntryDestroyedException

+1 from me. When you need to do an offline export, it’s usually important. Not being able to export *all* the data might lead to data loss. Anthony > On Aug 16, 2019, at 2:06 PM, Udo Kohlmeyer wrote: > > +1 to include > > > On 8/16/19 12:43 PM, Eric Shu wrote: >> Hi, >> >> I'd like to in

Re: Proposal to Include GEODE-7079 in 1.10.0

While we can’t fix *all known bugs*, I think where we do have a fix for an important issue we should think hard about the cost of not including that in a release. IMO, the fixed time approach to releases means that we *start* the release effort (including stabilization and bug fixing if needed)

Re: [DISCUSS] Geode dependency update process (review by 8/28/2019)

Usually there’s a bit of manual “art” to updating dependencies. You can’t always rely on stuff not breaking in minor releases. The best example is JUnitParams. Updating that breaks most of our tests since we use the test name for many things like region names and the new format is incompatibl

Re: Propose fix for 1.10 release: Prevent NPE in getLocalSize()

Given that we’re trying to stabilize the release branch and this fix seems to *help* that I’m in favor of merging it. Anthony > On Aug 13, 2019, at 5:32 PM, Udo Kohlmeyer wrote: > > @Aaron, is this an existing issue (i.e this was not introduced in a current > refactor)? > > If the answer is

Re: Draft of Apache Geode Quarterly Report (Aug 2019) for your review

I think you could call out a number of interesting discussions that happened on the dev list: - CFP process - Criteria for being a committer - etc Anthony > On Aug 12, 2019, at 4:26 PM, Dave Barnes wrote: > > Thanks, Aaron - good catch. > > On Mon, Aug 12, 2019 at 4:09 PM Aaron Lindsey wro

<    1   2   3   4   5   6   7   8   9   10   >