Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/154
+1
On Tue, Feb 20, 2018 at 5:17 PM, Dan Smith wrote:
> >
> > unregisterInterestForKeys(Iterable keys)
> >
>
> +1
>
--
-John
john.blum10101 (skype)
>
> unregisterInterestForKeys(Iterable keys)
>
+1
While doing this work, it looks like we have an equivalent
unregisterInterest(K key) that accepts a List of keys or a single key. To
keep things consistent with registeringInterest, I propose that we
deprecate the behavior for passing in a list as the key and we introduce:
unregisterInterestForKe
So long as we **never** remove the ability to start an "embedded"
*Locator/Manager* in an [application] *CacheServer *process*, *which is
highly valuable during "*development*".
For instance, I may want to spin up an application peer *CacheServer* instance
with an embedded *Locator/Manager*, like
---
Spring Data GemFire > Nightly-ApacheGeode > #834 was successful.
---
Scheduled
2333 tests in total.
https://build.spring.io/browse/SGF-NAG-834/
--
This
TL;DR I'd like to propose that we deprecate and ultimately remove the
ability to run a JMX manager on a non-locator member.
I'm not sure about the history for this capability and the original use
cases but I imagine it would have been driven, to a large part, by the
ability for member discovery wi
Dear Apache Enthusiast,
(You’re receiving this message because you’re subscribed to a user@ or
dev@ list of one or more Apache Software Foundation projects.)
We’re pleased to announce the upcoming ApacheCon [1] in Montréal,
September 24-27. This event is all about you — the Apache project com
Hi Community,
Any Comments on the below one.
Thanks,
Aravind Musigumpula
-Original Message-
From: Bruce Schuchardt [mailto:bschucha...@pivotal.io]
Sent: Thursday, January 18, 2018 11:58 PM
To: dev@geode.apache.org
Subject: Re: Monitor the neighbour JVM using neihbour's member-timeout
Hello team,
One of the most severe issues hitting our real time application is thread stuck
for multiple reasons, such as long lasting locks, deadlocks, threads which wait
for reply forever in case of packet drop issue etc...
Such kind of stuck are under Radar of the existing system health check
10 matches
Mail list logo
