Re: [DISCUSS] Adding CODEOWNERS to Apache Geode

2020-11-18 Thread Owen Nichols
+1 This will greatly improve the experience for contributors. Instead of an intimidating empty list of reviewers when you submit a PR (and no ability to add reviewers, if you’re not a committer), it will be great to already have at least two reviewers automagically assigned. I have a small

Fixed: apache/geode-native#2803 (develop - 9fdb183)

2020-11-18 Thread Travis CI
Build Update for apache/geode-native - Build: #2803 Status: Fixed Duration: 1 hr, 27 mins, and 46 secs Commit: 9fdb183 (develop) Author: Jacob Barrett Message: GEODE-2484: Removes ACE_DLL (#591) Replaces with boost::dll. View the changeset:

Re: [PROPOSAL] Change the default value of conserve-sockets to false

2020-11-18 Thread John Blum
The downside of conserve-sockets = false is that you are (essentially) back to a Thread|Socket / Request model (though Geode limits this system resource consumption to a degree by the use of Thread Pools in p2p distribution layer) and thus, you can run out of file descriptors (per newly opened

Re: [PROPOSAL] Change the default value of conserve-sockets to false

2020-11-18 Thread Nabarun Nag
+1 * As nearly all of the production use-cases need "conserve-sockets" to be set to false, I think we can aim for changing the default value to false for 1.14.0 release. * We can highlight this change in the release notes and emails. Regards, Nabarun

Re: [PROPOSAL] Change the default value of conserve-sockets to false

2020-11-18 Thread Owen Nichols
I’m not familiar with the inner workings, but your writeup is excellent and makes a compelling case. It sounds like you are saying that the original motivation for conserve-sockets=true was to improve performance, but in fact it makes performance worse. Do you have some numbers to quantify

Re: [PROPOSAL] Change the default value of conserve-sockets to false

2020-11-18 Thread Udo Kohlmeyer
Hi there Donal, Thank you for raising this. It is not an uncommon request to change the default value of this field. This has been discussed many times in the past. I would LOVE to approve this change, but this would mean that users that don’t set this property might suddenly have this

Fixed: apache/geode-native#2802 (support/1.13 - ba85630)

2020-11-18 Thread Travis CI
Build Update for apache/geode-native - Build: #2802 Status: Fixed Duration: 1 hr, 19 mins, and 31 secs Commit: ba85630 (support/1.13) Author: Mario Salazar de Torres Message: GEODE-8724: Fix compilation using docker image (#696) - As latest tag for ubuntu

[PROPOSAL] Change the default value of conserve-sockets to false

2020-11-18 Thread Donal Evans
Hi Geode dev, First, from the docs[1], a brief explanation of the purpose of the conserve-sockets property: "The conserve-sockets setting indicates whether application threads share sockets with other threads or use their own sockets for member communication. This setting has no effect on

[DISCUSS] Adding CODEOWNERS to Apache Geode

2020-11-18 Thread Robert Houghton
Hello Devs. I would like to improve the quality of the pull-request reviews we see for critical parts of the Apache Geode project. In discussions with other committers, a (not the) big hurdle to that is getting the right eyes to look at a given PR. To that end, I propose the adoption of GitHub's

Failed: apache/geode-examples#496 (non-overlapping-changes - f503c91)

2020-11-18 Thread Travis CI
Build Update for apache/geode-examples - Build: #496 Status: Failed Duration: 1 min and 51 secs Commit: f503c91 (non-overlapping-changes) Author: Owen Nichols Message: disparate ownership areas View the changeset:

Canceled: apache/geode-examples#492 (test-2-codeowners - 722f7ca)

2020-11-18 Thread Travis CI
Build Update for apache/geode-examples - Build: #492 Status: Canceled Duration: ? Commit: 722f7ca (test-2-codeowners) Author: Owen Nichols Message: disparate ownership areas View the changeset:

Re: needs permission to push code to geode example repo

2020-11-18 Thread John Hutchison
Hi Anish- I believe you would need to create a pull request to have your changes merged into the main repo. I’m not sure about the Jira issue. -John From: aashish choudhary Date: Wednesday, November 18, 2020 at 1:55 PM To: dev@geode.apache.org Subject: needs permission to push code to geode

Re: Request for Jira Permissions

2020-11-18 Thread John Hutchison
thx From: Dan Smith Date: Wednesday, November 18, 2020 at 2:08 PM To: dev@geode.apache.org Subject: Re: Request for Jira Permissions Done. You should have access now. -Dan From: John Hutchison Sent: Wednesday, November 18, 2020 11:00 AM To:

Re: Request for Jira Permissions

2020-11-18 Thread Dan Smith
Done. You should have access now. -Dan From: John Hutchison Sent: Wednesday, November 18, 2020 11:00 AM To: dev@geode.apache.org Subject: Request for Jira Permissions Hi, I’d like to request permission to assign jira tickets to myself and also to reopen

Re: needs permission to push code to geode example repo

2020-11-18 Thread Anthony Baker
Hi Ashish! The best way to contribute is to open a PR via GitHub. LMK if you need help with that. What’s your JIRA username? Anthony > On Nov 18, 2020, at 10:54 AM, aashish choudhary > wrote: > > Hi Team, > > I am trying to add an example for geode rest api.I have the changes in my >

Request for Jira Permissions

2020-11-18 Thread John Hutchison
Hi, I’d like to request permission to assign jira tickets to myself and also to reopen tickets that have been resolved. Thanks, John

needs permission to push code to geode example repo

2020-11-18 Thread aashish choudhary
Hi Team, I am trying to add an example for geode rest api.I have the changes in my branch but not sure what is the process to push changes to this repo.Could someone help with this? Also it seems my permission to raise Jira issue is also revoked. Please help with that too. With Best Regards,

[ANNOUNCE] Apache Geode 1.13.1

2020-11-18 Thread Dick Cavender
The Apache Geode community is pleased to announce the availability of Apache Geode 1.13.1. 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