Travis CI reporting checks failures but no issues on my local machine

Hi, I am getting geode-core:spotlessJavaCheck errors on travis-ci. But When I ran ./gradlew clean build -Dskip.tests=true on my local machine everything is fine. https://travis-ci.org/apache/geode/builds/188749592 What I am missing here ? Thanks Avinash

[jira] [Commented] (GEODE-1887) Client PROXY region should delegate all operations to server

[ https://issues.apache.org/jira/browse/GEODE-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797197#comment-15797197 ] ASF GitHub Bot commented on GEODE-1887: --- GitHub user davinash opened a pull request:

[GitHub] geode pull request #329: [GEODE-1887] #comment Fix for Issue #1887

GitHub user davinash opened a pull request: https://github.com/apache/geode/pull/329 [GEODE-1887] #comment Fix for Issue #1887 Issue : Client PROXY region should delegate all operations to server 1. If client and data policy is empty then size API goes through ServerRegion

Re: New proposal for type definitons

I don't know that I would be concerned with optimization of unstructured data from the start. Given that the data is unstructured it means that it can be restructured at a later time. You could have a lazy task running on the server the restructures unstructured data to be more uniform and compact.

Re: New proposal for type definitons

Hi Hitesh, There are a few different ways to store self describing data. One way might be to just store the json string, or convert it to bson, and then enhance the query engine to handle those formats. Another way might be extend PDX to support self describing serialized values. We xould add a se

[jira] [Created] (GEODE-2265) Some entry operations using JTA do not start transaction in GEODE

Eric Shu created GEODE-2265: --- Summary: Some entry operations using JTA do not start transaction in GEODE Key: GEODE-2265 URL: https://issues.apache.org/jira/browse/GEODE-2265 Project: Geode Issue

Re: New proposal for type definitons

>>If we give people the option to store and query self describing values, then users with inconsistent json could just use that option and pay the extra storage cost. Dan, are you saying expose some interface to serialize/de and "query the some field in data - getFieldValue(fieldname)" dtata?  Som

Re: Review Request 55124: fix duplicate entries from list lucene index and search lucene index

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55124/#review160449 --- Fix it, then Ship it! geode-lucene/src/main/java/org/apache/ge

Re: The right way to remove a region's cache listener?

Yes, it does exist. I'm sure I'm deploying correctly because when I add the listeners programmatically, they write to the server.log file. On Tue, Jan 3, 2017 at 3:13 PM, Jinmei Liao wrote: > You probably did not deploy the jars correctly? See if that jar exist in > your server's dir. > > On Tu

Broken: apache/geode#1715 (develop - 8b8084f)

Build Update for apache/geode - Build: #1715 Status: Broken Duration: 10 minutes and 6 seconds Commit: 8b8084f (develop) Author: Bruce Schuchardt Message: GEODE-2253 Locator may fail to respond to a valid request This introduces a retry loop in the locator whe

Re: The right way to remove a region's cache listener?

You probably did not deploy the jars correctly? See if that jar exist in your server's dir. On Tue, Jan 3, 2017 at 2:51 PM, Kevin Duling wrote: > I must have some syntax wrong, because I'm not able to add a cache listener > from the gfsh command line out of the jar I deployed. > > ListenerTypeA

[jira] [Created] (GEODE-2264) Update Geode Javadocs (no longer "incubating")

Dave Barnes created GEODE-2264: -- Summary: Update Geode Javadocs (no longer "incubating") Key: GEODE-2264 URL: https://issues.apache.org/jira/browse/GEODE-2264 Project: Geode Issue Type: Bug

Re: integrating geode-examples repo with JIRA

I think you have to ask infra to enable that for the geode-examples repo. I think it makes sense to turn it on given we're already doing it for the man geode repo. -Dan On Tue, Jan 3, 2017 at 2:07 PM, Karen Miller wrote: > Can someone with the proper karma help or show me how to integrate > com

Review Request 55155: GEODE-2155 Auto-reconnect fails with NPE

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55155/ --- Review request for geode, Galen O'Sullivan, Hitesh Khamesra, and Udo Kohlmeyer.

[jira] [Assigned] (GEODE-2155) Auto-reconnect fails with NPE

[ https://issues.apache.org/jira/browse/GEODE-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-2155: --- Assignee: Bruce Schuchardt > Auto-reconnect fails with NPE >

[jira] [Resolved] (GEODE-2253) Locator may fail to respond to a valid request

[ https://issues.apache.org/jira/browse/GEODE-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2253. - Resolution: Fixed Fix Version/s: 1.1.0 > Locator may fail to respond to a valid req

Re: The right way to remove a region's cache listener?

I must have some syntax wrong, because I'm not able to add a cache listener from the gfsh command line out of the jar I deployed. ListenerTypeA and ListenerTypeB exist in the package 'geode' in my custard-1.0-SNAPSHOT.jar. I'm able to add those programmatically as I showed earlier. So that I cou

[jira] [Updated] (GEODE-2263) CliUtil.getRegionAssociatedMembers()'s returnAll parameter is not used

[ https://issues.apache.org/jira/browse/GEODE-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2263: - Description: And DataCommands has a same name method which did use returnAll parameter. I think th

[jira] [Created] (GEODE-2263) CliUtil.getRegionAssociatedMembers()

xiaojian zhou created GEODE-2263: Summary: CliUtil.getRegionAssociatedMembers() Key: GEODE-2263 URL: https://issues.apache.org/jira/browse/GEODE-2263 Project: Geode Issue Type: Bug

[jira] [Updated] (GEODE-2263) CliUtil.getRegionAssociatedMembers()'s returnAll parameter is not used

[ https://issues.apache.org/jira/browse/GEODE-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou updated GEODE-2263: - Summary: CliUtil.getRegionAssociatedMembers()'s returnAll parameter is not used (was: CliUtil.get

Re: The right way to remove a region's cache listener?

I think it would make sense to have a --remove_listener=ListenerTypeB. Gfsh is really about verbs not end-state I think. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Tue, Jan 3, 2017 at 1:52 PM, Kevin Duling wrote: > Is this an intuitive User Experience? > >

Re: Review Request 55124: fix duplicate entries from list lucene index and search lucene index

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55124/ --- (Updated Jan. 3, 2017, 10:45 p.m.) Review request for geode and Dan Smith. Ch

[jira] [Commented] (GEODE-2042) Add a RMI "Blackboard" into the DUnit framework for VM to communicate over

[ https://issues.apache.org/jira/browse/GEODE-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796423#comment-15796423 ] Bruce Schuchardt commented on GEODE-2042: - The blackboard was added in this commit

[jira] [Resolved] (GEODE-2042) Add a RMI "Blackboard" into the DUnit framework for VM to communicate over

[ https://issues.apache.org/jira/browse/GEODE-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2042. - Resolution: Fixed Fix Version/s: 1.1.0 > Add a RMI "Blackboard" into the DUnit fram

[jira] [Resolved] (GEODE-1580) ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock

[ https://issues.apache.org/jira/browse/GEODE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-1580. - Resolution: Fixed Fix Version/s: 1.1.0 > ci failure: GemFireDeadlockDetectorDUnitTe

[jira] [Updated] (GEODE-1580) ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock

[ https://issues.apache.org/jira/browse/GEODE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-1580: Labels: CI (was: CI Flaky) > ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDe

[jira] [Commented] (GEODE-2253) Locator may fail to respond to a valid request

[ https://issues.apache.org/jira/browse/GEODE-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796404#comment-15796404 ] ASF subversion and git services commented on GEODE-2253: Commit 8b

[jira] [Commented] (GEODE-1580) ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock

[ https://issues.apache.org/jira/browse/GEODE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796403#comment-15796403 ] ASF subversion and git services commented on GEODE-1580: Commit 43

Re: geode-examples vs geode/geode-examples

+1 to moving the existing examples from the module to the new repo and then editing/replacing them as appropriate. On Tue, Jan 3, 2017 at 2:02 PM Kirk Lund wrote: > What's the plan for the new geode-examples repo and the existing > geode-examples module of the geode repo? Are we planning to move

Re: geode-examples vs geode/geode-examples

Yes. I'm moving everything over now, and after moving will remove it from the geode repository. See https://issues.apache.org/jira/browse/GEODE-2260. On Tue, Jan 3, 2017 at 2:02 PM, Kirk Lund wrote: > What's the plan for the new geode-examples repo and the existing > geode-examples module of t

integrating geode-examples repo with JIRA

Can someone with the proper karma help or show me how to integrate commits to the new geode-examples repository with Geode JIRA tickets and this mailing list? Thanks.

geode-examples vs geode/geode-examples

What's the plan for the new geode-examples repo and the existing geode-examples module of the geode repo? Are we planning to move examples and then delete geode/geode-examples? -Kirk

Re: Review Request 55074: GEODE-2253 Locator may fail to respond to a valid request

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55074/#review160436 --- Ship it! Ship It! - Udo Kohlmeyer On Dec. 28, 2016, 5:15 p.m

Re: Review Request 55106: GEODE-1580 ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55106/#review160435 --- Ship it! Ship It! - Udo Kohlmeyer On Jan. 3, 2017, 6:03 p.m.

Re: Review Request 55106: GEODE-1580 ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55106/#review160434 --- Ship it! Ship It! - Hitesh Khamesra On Jan. 3, 2017, 6:03 p.

Fixed: apache/geode#1714 (develop - 3200447)

Build Update for apache/geode - Build: #1714 Status: Fixed Duration: 9 minutes and 8 seconds Commit: 3200447 (develop) Author: Jinmei Liao Message: spotless fix View the changeset: https://github.com/apache/geode/compare/30891423d83b...32004475460b View the

[jira] [Created] (GEODE-2262) Improve cluster config: do not allow mix of locators that has CC enabled and not enabled in one cluster.

Jinmei Liao created GEODE-2262: -- Summary: Improve cluster config: do not allow mix of locators that has CC enabled and not enabled in one cluster. Key: GEODE-2262 URL: https://issues.apache.org/jira/browse/GEODE-2262

[jira] [Resolved] (GEODE-2197) Refactor cluster config so that cluster.xml and properties don't need to be saved in the file system.

[ https://issues.apache.org/jira/browse/GEODE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-2197. Resolution: Fixed > Refactor cluster config so that cluster.xml and properties don't need to be > s

Broken: apache/geode#1713 (develop - 3089142)

Build Update for apache/geode - Build: #1713 Status: Broken Duration: 8 minutes and 26 seconds Commit: 3089142 (develop) Author: Jinmei Liao Message: GEODE-2197: refactor cluster config and fix the test failures View the changeset: https://github.com/apache/g

[jira] [Assigned] (GEODE-2261) refactor ClusterConfigWriter do not need to use remote call to change cluster config

[ https://issues.apache.org/jira/browse/GEODE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-2261: -- Assignee: Jinmei Liao > refactor ClusterConfigWriter do not need to use remote call to change c

[jira] [Commented] (GEODE-2197) Refactor cluster config so that cluster.xml and properties don't need to be saved in the file system.

[ https://issues.apache.org/jira/browse/GEODE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796171#comment-15796171 ] ASF subversion and git services commented on GEODE-2197: Commit 30

[jira] [Commented] (GEODE-2197) Refactor cluster config so that cluster.xml and properties don't need to be saved in the file system.

[ https://issues.apache.org/jira/browse/GEODE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796170#comment-15796170 ] ASF subversion and git services commented on GEODE-2197: Commit 07

[jira] [Updated] (GEODE-2261) refactor ClusterConfigWriter do not need to use remote call to change cluster config

[ https://issues.apache.org/jira/browse/GEODE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-2261: --- Summary: refactor ClusterConfigWriter do not need to use remote call to change cluster config (was: C

Re: Off-Heap Annotations

Oh yeah! We were hoping to get more feedback from users to find out what they want or need for migrating a region from heap to off-heap. Right now it doesn't support anything like that but it was definitely discussed. On Tue, Jan 3, 2017 at 12:27 PM, Hitesh Khamesra < hitesh...@yahoo.com.invalid>

Re: Cluster Config

+1 - Configuration should be consistent on the locators, specially cause we should consider them source of truth for "distributed configuration" anyway... On Tue, Jan 3, 2017 at 1:59 PM, Swapnil Bawaskar wrote: > I think we should not allow a mix of cc enabled or disabled across any > member in

Re: Off-Heap Annotations

I was considering the case when one want to change its "value" through rolling upgrade. In an ideal world, I would expect that every node will have the same heap/off configuration, but other can happen. From: Kirk Lund To: geode Sent: Tuesday, January 3, 2017 12:16 PM Subject: Re:

Re: Off-Heap Annotations

The region is required to be off-heap in every member in the cluster. Imagine memberA with 12 GB heap, 100 GB off-heap and memberB with 8 GB heap, 0 GB off-heap. What's the point of having replicated regionA be off-heap in memberA but on heap in memberB? The region will always be limited by the hea

Re: Cluster Config

I think we should not allow a mix of cc enabled or disabled across any member in the cluster (servers as well as locators) https://issues.apache.org/jira/browse/GEODE-1961. On Tue, Jan 3, 2017 at 11:25 AM, Jinmei Liao wrote: > yeah, the reason we have issue2 is because of issue1, if we fix issue

Re: The right way to remove a region's cache listener?

`describe region` will show the CacheListeners registered on a Region. On Tue, Jan 3, 2017 at 11:44 AM, Dave Barnes wrote: > What gfsh command (if any) lists the cache-listeners available on a given > region? Seems like if the intention is to support adding and deleting by > name, there should b

Re: Off-Heap Annotations

>>>The first cluster member to create the region wins and all the other members need to conform to the first one's configuration. Is there any technical reason to check this? Or we just want same configuration across cluster. From: Darrel Schneider To: dev@geode.apache.org Sent: Tuesda

Re: New proposal for type definitons

+1 to what Jacob said. On Tue, Jan 3, 2017 at 11:39 AM, Jacob Barrett wrote: > A little late to the game here but I want to go back to Dan's idea of > storing the JSON or other self describing objects as a first class object > in Geode. As it stands right now an entry can be a POJO, Java seriali

Re: The right way to remove a region's cache listener?

What gfsh command (if any) lists the cache-listeners available on a given region? Seems like if the intention is to support adding and deleting by name, there should be a way to list existing names. On Tue, Jan 3, 2017 at 11:29 AM, Jinmei Liao wrote: > +1 for remove by specifying only the ones y

Re: New proposal for type definitons

A little late to the game here but I want to go back to Dan's idea of storing the JSON or other self describing objects as a first class object in Geode. As it stands right now an entry can be a POJO, Java serialized object, or PDX, so why not other types? Seems perfectly reasonable to allow first

Re: Off-Heap Annotations

When a region is created you need to mark it as off-heap or on-heap. Once it is created you can not change it on that region. You can create and destroy regions on the fly. Also the region needs to be consistently configured on-heap or off-heap across the entire cluster. The first cluster member t

Re: The right way to remove a region's cache listener?

+1 for remove by specifying only the ones you want to keep: $ alter region --name=data --cache-listener="" will remove all the cache listeners On Tue, Jan 3, 2017 at 11:08 AM, Kirk Lund wrote: > +1 I'm for the approach you're proposing. As long as it's documented in > user docs (it's not curren

Re: Cluster Config

yeah, the reason we have issue2 is because of issue1, if we fix issue1, then local changes are definitely more welcome than remote calls. The whole idea of proposing change#2 is to get rid of some of the silliness of the implementation. Change #2 would get rid of 4or 5 remote functions class at lea

Re: The right way to remove a region's cache listener?

+1 I'm for the approach you're proposing. As long as it's documented in user docs (it's not currently) then this provides a straightforward use of the existing gfsh syntax without introducing too many new command options. Create the region with two cache listeners: $ create region --name=data --ca

Re: The right way to remove a region's cache listener?

Is this an intuitive User Experience? Given these two classes: public class ListenerTypeA extends CacheListenerAdapter implements Declarable and public class ListenerTypeB extends CacheListenerAdapter implements Declarable And they are programmatically added to a region: CacheListener listene

Re: Cluster Config

If you fix issue 1 do you really need to change 2? I agree it is silly that it remotes to another locator to execute the CC change but would it have any effect should all the locators be configured the same? On Tue, Jan 3, 2017 at 10:29 AM Jinmei Liao wrote: > Ok, currently we have 2 issues: >

[jira] [Reopened] (GEODE-2174) Provide more detailed reason when unregistering clients

[ https://issues.apache.org/jira/browse/GEODE-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby reopened GEODE-2174: -- > Provide more detailed reason when unregistering clients >

[jira] [Updated] (GEODE-2174) Provide more detailed reason when unregistering clients

[ https://issues.apache.org/jira/browse/GEODE-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby updated GEODE-2174: - Assignee: Hitesh Khamesra (was: Barry Oglesby) > Provide more detailed reason when unregistering

Re: Cluster Config

Ok, currently we have 2 issues: 1) a cluster might have a mix of locators with and without CC enabled. The change proposed is to reject locator that does not CC enabled to join a locator that has CC enabled (or vise versa). 2) commands that change CC does remote calls to a locator with CC to change

Re: Cluster Config

I am not a fan of complicated work arounds for things like this. Feels like a lot of moving parts to address something that was more likely a careless oversight than an intended use case. Why do you feel like we can't address the underlying issue? On Tue, Jan 3, 2017 at 10:05 AM Jinmei Liao wrot

[jira] [Created] (GEODE-2261) ClusterConfigWriter do not need to use remote call to change cluster config

Jinmei Liao created GEODE-2261: -- Summary: ClusterConfigWriter do not need to use remote call to change cluster config Key: GEODE-2261 URL: https://issues.apache.org/jira/browse/GEODE-2261 Project: Geode

Re: Cluster Config

Currently our API or gfsh commands allow you to create a cluster with a mix of locators with and without CC. Our DM maintains a list of locators and a separate list of locators with CC enabled. It is bad, I know. But I am not sure if we can change it. Assuming we have to live with cluster with mix

Re: Review Request 55106: GEODE-1580 ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55106/ --- (Updated Jan. 3, 2017, 6:03 p.m.) Review request for geode, Galen O'Sullivan, H

Re: Cluster Config

+1 I think that the configurations of all locators should be identical, or at least in terms of a few "critical" properties. One would also need to be able to amend some property changes at runtime, to allow for the changing of configuration without taking all the locators offline. "remote-lo

Re: Cluster Config

+1 for what Jake said - I think locators should refuse to join if their settings don't match. Having a mix of locators that do and don't support cluster configuration seems confusing. That means your system may or may not update cluster configuration, depending on which locators are actually runni

Re: Cluster Config

It seems questionable to me that you would have one locator with CC enabled and another with CC disabled. Usually you have extra locators for fault tolerance. What happens if the one with CC enabled dies? Will gfsh commands quit getting recorded in CC because we now only have a locator with CC disa

Re: Cluster Config

If we consider the locators as the directory service for the cluster then it makes no sense for them to be configured differently. I think locators should be force to adopt the configuration of the other locator in the cluster or refuse to join the cluster until their config is updated to match.

[jira] [Updated] (GEODE-2238) Member may fail to receive cluster configuration from locator

[ https://issues.apache.org/jira/browse/GEODE-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2238: Labels: (was: Flaky) > Member may fail to receive cluster configuration from locator > ---

[jira] [Commented] (GEODE-2138) gfsh 'start' reports 'GemFire Version'

[ https://issues.apache.org/jira/browse/GEODE-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795567#comment-15795567 ] ASF GitHub Bot commented on GEODE-2138: --- Github user davebarnes97 commented on the i

[GitHub] geode issue #328: [GEODE-2138] #comment Fix issues GEODE-2138

Github user davebarnes97 commented on the issue: https://github.com/apache/geode/pull/328 +1 Looks good to me. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wi

[jira] [Commented] (GEODE-2257) Client configured to use locator with addPoolServer fails to connect

[ https://issues.apache.org/jira/browse/GEODE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795539#comment-15795539 ] ASF subversion and git services commented on GEODE-2257: Commit 01

Cluster Config

Calling all the pros with knowledge on cluster configurations: This is regarding this current behavior of Cluster Config: Assuming a cluster has 2 locators, locator-A-with-CC (with cluster config enabled), and locator-B-without-CC (without cluster config enabled), currently any commands a user exe

Re: Off-Heap Annotations

Dor, I'd like to understand the reason you would like to have different semantics than what's in Geode with regard to off-heap. Can you expand a bit on what you are trying to achieve? On Tue, Jan 3, 2017 at 11:22 AM, Udo Kohlmeyer wrote: > Hi there Dor, > > I will allow someone with better kno

Re: Off-Heap Annotations

Hi there Dor, I will allow someone with better knowledge to answer this, but I think it would be safe to assume that you cannot change this at runtime. --Udo On 1/3/17 08:01, Dor Ben Dov wrote: Udo, This means it can't be changed on the fly in runtime ? Need to be flagged before? Dor -

[jira] [Commented] (GEODE-2257) Client configured to use locator with addPoolServer fails to connect

[ https://issues.apache.org/jira/browse/GEODE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795386#comment-15795386 ] ASF subversion and git services commented on GEODE-2257: Commit d2

RE: Off-Heap Annotations

Udo, This means it can't be changed on the fly in runtime ? Need to be flagged before? Dor -Original Message- From: Udo Kohlmeyer [mailto:u...@apache.org] Sent: יום ג 03 ינואר 2017 17:32 To: dev@geode.apache.org Subject: Re: Off-Heap Annotations Hi there Gal, That is not possible. A

Re: Build failed in Jenkins: Geode-nightly #705

A new test that I checked in last week is failing. I'm going to disable it while I look into the matter. Le 1/3/2017 à 7:56 AM, Apache Jenkins Server a écrit : See -- [...truncated 544 lines...] :geode-

Build failed in Jenkins: Geode-nightly #705

See -- [...truncated 544 lines...] :geode-cq:compileTestJavaNote: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked

[jira] [Resolved] (GEODE-1754) InternalLocator.startLocator needs to be cleaned up

[ https://issues.apache.org/jira/browse/GEODE-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-1754. - Resolution: Fixed Fix Version/s: 1.1.0 Thanks for the reminder Amey. Your changes

Re: Off-Heap Annotations

Hi there Gal, That is not possible. A region is either on-heap or off-heap. --Udo On 1/2/17 13:50, Gal Palmery wrote: Ok, So if I want to have just a certain part of the region off heap and the rest of it on heap - how do I do that? -Original Message- From: Dan Smith [mailto:dsm..

RE: Off-Heap Annotations

Ok, So if I want to have just a certain part of the region off heap and the rest of it on heap - how do I do that? -Original Message- From: Dan Smith [mailto:dsm...@pivotal.io] Sent: Monday, January 02, 2017 19:46 To: dev@geode.apache.org Subject: Re: Off-Heap Annotations Hi Gal, The

[jira] [Assigned] (GEODE-2049) unit of measure wrong in DistributionStats tcpFinalCheck statitistics

[ https://issues.apache.org/jira/browse/GEODE-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amey Barve reassigned GEODE-2049: - Assignee: Amey Barve > unit of measure wrong in DistributionStats tcpFinalCheck statitistics > --

[jira] [Assigned] (GEODE-1887) Client PROXY region should delegate all operations to server

[ https://issues.apache.org/jira/browse/GEODE-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avinash Dongre reassigned GEODE-1887: - Assignee: Avinash Dongre > Client PROXY region should delegate all operations to server >

[jira] [Commented] (GEODE-2138) gfsh 'start' reports 'GemFire Version'

[ https://issues.apache.org/jira/browse/GEODE-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15794478#comment-15794478 ] ASF GitHub Bot commented on GEODE-2138: --- GitHub user Nilkanthpatel04 opened a pull r

[GitHub] geode pull request #328: [GEODE-2138] #comment Fix issues GEODE-2138

GitHub user Nilkanthpatel04 opened a pull request: https://github.com/apache/geode/pull/328 [GEODE-2138] #comment Fix issues GEODE-2138 Replaced GemFire with Geode in a Launcher_ServiceStatus__Message. Added a test to verify the output. You can merge this pull request into a Gi