Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/190
I haven't encountered a customer using a persistent region on a client in
many years. Maybe that entire construct should be deprecated on a
ClientCache.
--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771
On Mar 9, 2018 3:39 PM, "Kirk Lund" wrote:
> And I can't invok
Hi Patrick,
Permission granted.
Happy Editing!
--Mark
On Fri, Mar 9, 2018 at 3:08 PM, Patrick Rhomberg
wrote:
> Hello all!
>
> I wanted to propose adding a public cluster configuration API, and I think
> that conversation would greatly benefit from the formatting that email too
> critically l
And I can't invoke createRegionFactory(RegionShortcut.REPLICATE_PERSISTENT)
because ClientCache throws UnsupportedOperationException for it...
/**
* @since GemFire 6.5
*/
@Override
public RegionFactory createRegionFactory(RegionShortcut
shortcut) {
if (isClient()) {
throw ne
I keep running into things that the dunit tests are doing in a client cache
that cannot be done with non-deprecated APIs.
Is there a non-deprecated way to create a PERSISTENT_REPLICATE region in a
client cache?
AttributesFactory factory = new AttributesFactory();
factory.setDataPolicy
Hello all!
I wanted to propose adding a public cluster configuration API, and I think
that conversation would greatly benefit from the formatting that email too
critically lacks. My username is prhomberg
Imagination is Change.
~Patrick
---
Spring Data GemFire > Nightly-ApacheGeode > #851 was successful.
---
Scheduled with changes by John Blum.
2381 tests in total.
https://build.spring.io/browse
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/266
Build Update for jinmeiliao/geode
-
Build: #259
Status: Errored
Duration: 5 minutes and 37 seconds
Commit: 2c21167 (cliUtil2)
Author: Jinmei Liao
Message: MockExtensionCommands should not use non public GfshCommand
View the changeset:
https://github.com/jinme
Swapnil,
Interesting points, here are my thoughts:
> Given that there is already support for parallel rebalancing among regions,
> I do not see the value in supporting parallel rebalancing of buckets.
I think there are some advantages to parallel rebalance of a region over
rebalancing regions in
Build Update for apache/geode
-
Build: #6683
Status: Broken
Duration: 20 minutes and 49 seconds
Commit: e09c409 (develop)
Author: Udo
Message: GEODE-4791: backing out upgrade to 4.5.1 due to an incompatibility
with dockerized-test library, which only supports
It would be interesting to have a way to model the behavior of the current
algorithm and compare it to the proposal under various conditions like
membership changes, data imbalance, etc. That would let us understand the
optimality of the change in a concrete way.
Anthony
> On Mar 9, 2018, at
Given that there is already support for parallel rebalancing among regions,
I do not see the value in supporting parallel rebalancing of buckets.
If we end up doing this anyway, I would suggest to not rely on "parameters"
for throttling, as these parameters would have to be configured in advance
w
13 matches
Mail list logo