Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/156

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

If you're talking about GFSH commands only... removing JMX manager options from "start server" then that's probably reasonable. But as John described better than me, I wouldn't make non-dedicated-locators unable to host certain services such as JMX manager or locator. For example, it wasn't easy

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

What you described is a consequence of its current design/implementation, a tightly coupled one at that. * Why does the "Configuration Service" have to be limited to *Locators*? * Likewise, why would a "Management Service" be limited to *Managers*? I think of the later (*Locators/Managers*) as "

你好 你好吗？

Failed: jinmeiliao/geode#233 (createRegion - debd6ab)

Build Update for jinmeiliao/geode - Build: #233 Status: Failed Duration: 21 minutes and 13 seconds Commit: debd6ab (createRegion) Author: Jinmei Liao Message: GEODE-4625: name collision check when create region through gfsh View the changeset: https://github.

Re: New PMC members - Lynn Gallinat, Lynn Hughes-Godfrey, and Dick Cavender

WELCOME! -- Mike Stolz On Wed, Feb 21, 2018 at 6:28 PM, Anthony Baker wrote: > Welcome all! > > > On Feb 21, 2018, at 1:50 PM, Dan Smith wrote: > > > > We recently added a few new members to the Geode PMC. These three have > all > > been working on geode since it became an apache project, but

Re: New PMC members - Lynn Gallinat, Lynn Hughes-Godfrey, and Dick Cavender

Welcome all! > On Feb 21, 2018, at 1:50 PM, Dan Smith wrote: > > We recently added a few new members to the Geode PMC. These three have all > been working on geode since it became an apache project, but through some > process oversight were never added to the PMC. Please join me in welcoming > t

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

One thing that prompted this initial proposal is that our (management and monitoring) service boundaries, (or one could say APIs), are not well defined. Case in point; we currently have a 'configuration service' which is used to persist configuration. This service is only available on locators. Th

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #835 was SUCCESSFUL (with 2331 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #835 was successful. --- Scheduled 2333 tests in total. https://build.spring.io/browse/SGF-NAG-835/ -- This

Re: [Proposal] Thread monitoring mechanism

I am assuming this would be for all thread/thread pools and not specific to Function threads. I wonder what the impact would be for put/get operations or are we going to target specific operations. On Tue, Feb 20, 2018 at 1:04 AM Gregory Vortman wrote: > Hello team, > One of the most severe i

New PMC members - Lynn Gallinat, Lynn Hughes-Godfrey, and Dick Cavender

We recently added a few new members to the Geode PMC. These three have all been working on geode since it became an apache project, but through some process oversight were never added to the PMC. Please join me in welcoming these three to the PMC now! Lynn Gallinat Lynn Hughes-Godfrey Dick Cavende

Re: [DISCUSS] changes to registerInterest API

The usual caveat, if we're changing public API's we can introduce the new ones and deprecate the old ones for removal in a subsequent major release. -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 Download the new GemFire book here.

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

Typo; Sorry! This.. > I may even launch and connect additional servers using Gfsh within my IDE (or using *Gfsh*) that are connected to my *Boot* server, particularly if that *Boot* server also embeds a *Locator*. should have read... > I may even launch and connect additional servers *within my

RE: [Proposal] Thread monitoring mechanism

That's the point exactly to have a single very thin and generic mechanism to cover all threads/threads pool. Nothing is specific in this solution. Regards -Original Message- From: Jason Huynh [jhu...@pivotal.io] Received: Wednesday, 21 Feb 2018, 20:54 To: dev@geode.apache.org [dev@geode.

Re: Logging in to concourse.apachegeode-ci.info

I just assumed that I was *supposed* to login to that pipeline. Sounds like I probably don't need to login(?), but that's really not very obvious when looking at the pipeline gui. Nevermind... I don't need to kill or modify anything. I'm just used to logging into any concourse pipeline in order to

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

Most of the geode developers are working to get rid of singleton calls (and next up static code) with the goal of being able to have multiple Cache instances in one JVM. This is to facilitate writing geode and geode application tests in one JVM. This fits in with what John is saying as well. Basic

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

Hi Jinmei- Plain and simple, "development purposes". I can easily debug such a server when I can launch it from my IDE and I can still inspect the server using *Gfsh*. I may even launch and connect additional servers using Gfsh within my IDE (or using *Gfsh*) that are connected to my *Boot* serv

Re: Logging in to concourse.apachegeode-ci.info

Any committer can ask for login privileges (just like on Jenkins). That only gives you the ability to retrigger a job or kill a job. Is that what you want? If you want to modify job definitions you can do that by committing changes to [1]. Anthony [1] https://github.com/apache/geode/tree/dev

Re: Logging in to concourse.apachegeode-ci.info

I don't think you can log in to that pipeline. What are you wanting to do to it? -Dan On Wed, Feb 21, 2018 at 9:15 AM, Kirk Lund wrote: > How are we supposed to login to > https://concourse.apachegeode-ci.info/teams/main/login? > > I'm trying to use the "login with GitHub" option (I think this

Re: Logging in to concourse.apachegeode-ci.info

Yes, I have no trouble logging into github.com and I'm logged in to it within the same browser while trying to login to concourse. It seems to only be concourse that's not working. On Wed, Feb 21, 2018 at 9:19 AM, Alexander Murmann wrote: > Kirk, is access to GitHub itself working for you as exp

Re: Logging in to concourse.apachegeode-ci.info

Kirk, is access to GitHub itself working for you as expected? Using GitHub for auth on the pipeline worked for me without any issues. On Wed, Feb 21, 2018 at 9:15 AM, Kirk Lund wrote: > How are we supposed to login to > https://concourse.apachegeode-ci.info/teams/main/login? > > I'm trying to us

FINAL REMINDER: CFP for Apache EU Roadshow Closes 25th February

Hello Apache Supporters and Enthusiasts This is your FINAL reminder that the Call for Papers (CFP) for the Apache EU Roadshow is closing soon. Our Apache EU Roadshow will focus on Cloud, IoT, Apache Tomcat, Apache Http and will run from 13-14 June 2018 in Berlin. Note that the CFP deadline has

Logging in to concourse.apachegeode-ci.info

How are we supposed to login to https://concourse.apachegeode-ci.info/teams/main/login? I'm trying to use the "login with GitHub" option (I think this worked for me before) but it keeps failing in a couple different ways... latest failure was "failed to verify token", previous one was "verificatio

Re: [PROPOSAL] Deprecate running JMX Manager on non-locator members

Hi, John, what's the intended usage of this jmx-manager on the cache-server when app developers started a cache-server that way in spring boot? Is that usually for pulse or other jmx client for monitoring purpose mostly? Or they would still want to connect using gfsh and execute bunch of commands