Re: [VOTE] Apache Geode 1.10.0.RC2
+1 Still think it is ok to ship but found another annoying issue. When running Geode Native C++ integration tests (new framework) an indented disabled test will execute and fail. The test was not properly disabled. On the develop branch this test is fixed and is no longer disabled. If there is another RC we could easily port the fix or properly disable the test. -Jake > On Sep 23, 2019, at 2:36 PM, Jacob Barrett wrote: > > +1 > > Only tested geode-native on MacOS. Unit and integration tests based. > > One issues worth mentioning, while we don’t explicitly state support for > specific platforms, MacOs with the latest Xcode will have some troubles > getting off the ground. The updated Clang compiler in Xcode is less forgiving > and has some new warnings/errors. This same issue will likely exist in other > platforms where newer versions of Clang are in use. Adding a few warning > exclusions on your CMake configuration command will get you past the errors. > > cmake ... -DCMAKE_CXX_FLAGS="-Wno-defaulted-function-deleted > -Wno-c++2a-compat" > > -Jake > > >
Fwd: Migration of Jira to LDAP
Forwarding this from ASF INFRA, in case people have not seen it. -- Forwarded message - From: John Andrunas Date: Wed, Sep 18, 2019 at 11:44 AM Subject: Migration of Jira to LDAP To: , Users , < operati...@apache.org> Jira will be upgraded to the latest release on Wednesday 25th September starting at 2100UTC. Backups will be taken. We will also be enabling LDAP on the service. Should you not have your Jira username match your asf id then get an infra jira in quick. Downtime should be around 2 hours. Thanks John ASF Infra
Re: [VOTE] Apache Geode 1.10.0.RC2
+1 Only tested geode-native on MacOS. Unit and integration tests based. One issues worth mentioning, while we don’t explicitly state support for specific platforms, MacOs with the latest Xcode will have some troubles getting off the ground. The updated Clang compiler in Xcode is less forgiving and has some new warnings/errors. This same issue will likely exist in other platforms where newer versions of Clang are in use. Adding a few warning exclusions on your CMake configuration command will get you past the errors. cmake ... -DCMAKE_CXX_FLAGS="-Wno-defaulted-function-deleted -Wno-c++2a-compat" -Jake
Re: [VOTE] Apache Geode 1.10.0.RC2
+1 verified the management v2 apis are available. On Mon, Sep 23, 2019 at 12:58 PM Anthony Baker wrote: > +1 > > > Reviewed: > > - Signatures and hashes > - LICENSE and NOTICE > - No binaries in source distribution > - Builds from source > > > Quibbles: > > - Let’s include geode-benchmarks/ next release > - It would be more awesome if geode-native extracts into a directory with > a versioned name (e.g. apache-geode-native-1.10.0/) > - geode-examples is the only distribution that provides a zip format…is > that needed? > > Anthony > > > > On Sep 20, 2019, at 9:26 AM, Dick Cavender wrote: > > > > Hello Geode dev community, > > > > This is a release candidate for Apache Geode, version 1.10.0.RC2. > > Thanks to all the community members for their contributions to this > release! > > > > Please do a review and give your feedback including the checks performed. > > The voting deadline is *3PM PST Wed, September 25 2019*. > > > > This candidate has passed RC Qualification checks (NEW) which can be > found > > at: > > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-10-0-rc > > > > Release notes can be found at: > > > https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.10.0 > > > > Please note that we are voting upon the source tags: *rel/v1.10.0.RC2* > > > > Apache Geode: > > https://github.com/apache/geode/tree/rel/v1.10.0.RC2 > > Apache Geode examples: > > https://github.com/apache/geode-examples/tree/rel/v1.10.0.RC2 > > Apache Geode native: > > https://github.com/apache/geode-native/tree/rel/v1.10.0.RC2 > > > > Source and binary files: > > https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC2/ > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachegeode-1059 > > > > Geode's KEYS file containing PGP keys we use to sign the release: > > https://github.com/apache/geode/blob/develop/KEYS > > > > PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl= > > https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC2 > > -PgeodeRepositoryUrl= > > https://repository.apache.org/content/repositories/orgapachegeode-1059 > > build runAll > > > > Regards > > Dick Cavender > > -- Cheers Jinmei
Re: [VOTE] Apache Geode 1.10.0.RC2
It worked for me…? > On Sep 23, 2019, at 12:38 PM, Aaron Lindsey wrote: > > Does this happen for anyone else?
Re: [VOTE] Apache Geode 1.10.0.RC2
+1 Reviewed: - Signatures and hashes - LICENSE and NOTICE - No binaries in source distribution - Builds from source Quibbles: - Let’s include geode-benchmarks/ next release - It would be more awesome if geode-native extracts into a directory with a versioned name (e.g. apache-geode-native-1.10.0/) - geode-examples is the only distribution that provides a zip format…is that needed? Anthony > On Sep 20, 2019, at 9:26 AM, Dick Cavender wrote: > > Hello Geode dev community, > > This is a release candidate for Apache Geode, version 1.10.0.RC2. > Thanks to all the community members for their contributions to this release! > > Please do a review and give your feedback including the checks performed. > The voting deadline is *3PM PST Wed, September 25 2019*. > > This candidate has passed RC Qualification checks (NEW) which can be found > at: > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-10-0-rc > > Release notes can be found at: > https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.10.0 > > Please note that we are voting upon the source tags: *rel/v1.10.0.RC2* > > Apache Geode: > https://github.com/apache/geode/tree/rel/v1.10.0.RC2 > Apache Geode examples: > https://github.com/apache/geode-examples/tree/rel/v1.10.0.RC2 > Apache Geode native: > https://github.com/apache/geode-native/tree/rel/v1.10.0.RC2 > > Source and binary files: > https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC2/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachegeode-1059 > > Geode's KEYS file containing PGP keys we use to sign the release: > https://github.com/apache/geode/blob/develop/KEYS > > PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl= > https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC2 > -PgeodeRepositoryUrl= > https://repository.apache.org/content/repositories/orgapachegeode-1059 > build runAll > > Regards > Dick Cavender
Re: [VOTE] Apache Geode 1.10.0.RC2
The luceneSpatial project in geode-examples fails for me when running: ./gradlew -PgeodeReleaseUrl= https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC2 -PgeodeRepositoryUrl= https://repository.apache.org/content/repositories/orgapachegeode-1059 :luceneSpatial:build :luceneSpatial:runAll In the server logs, I see the following fatal message: [fatal 2019/09/23 12:34:38.673 PDT :41000 shared unordered uid=1 port=57924> tid=0x24] Error deserializing message org.apache.geode.SerializationException: Could not create an instance of org.apache.geode.internal.cache.MemberFunctionStreamingMessage . at org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2389) at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:997) at org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2516) at org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2528) at org.apache.geode.internal.tcp.Connection.readMessage(Connection.java:3111) at org.apache.geode.internal.tcp.Connection.processInputBuffer(Connection.java:2920) at org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1745) at org.apache.geode.internal.tcp.Connection.run(Connection.java:1577) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.InvalidClassException: org.apache.geode.cache.configuration.CacheElement; local class incompatible: stream classdesc serialVersionUID = -320845719772712775, local class serialVersionUID = 3127544615832500564 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:699) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1885) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1885) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2287) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2211) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2069) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431) at org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2846) at org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2790) at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2968) at org.apache.geode.internal.cache.MemberFunctionStreamingMessage.fromData(MemberFunctionStreamingMessage.java:288) at org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2372) ... 8 more Does this happen for anyone else? - Aaron On Fri, Sep 20, 2019 at 1:06 PM Dave Barnes wrote: > +1 > I downloaded the 1.10.0 RC2 Apache Geode release candidate, and also the > Geode Native Client source bundle. > Successfully built the user guides and API docs in both repos and > spot-checked the contents for correct version strings and paths. > > On Fri, Sep 20, 2019 at 9:26 AM Dick Cavender > wrote: > > > Hello Geode dev community, > > > > This is a release candidate for Apache Geode, version 1.10.0.RC2. > > Thanks to all the community members for their contributions to this > > release! > > > > Please do a review and give your feedback including the checks performed. > > The voting deadline is *3PM PST Wed, September 25 2019*. > > > > This candidate has passed RC Qualification checks (NEW) which can be > found > > at: > > > > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-10-0-rc > > > > Release notes can be found at: > > > > > https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.10.0 > > > > Please note that we are voting upon the source tags: *rel/v1.10.0.RC2* > > > > Apache Geode: > > https://github.com/apache/geode/tree/rel/v1.10.0.RC2 > > Apache Geode examples: > > https://github.com/apache/geode-examples/tree/rel/v1.10.0.RC2 > > Apache Geode native: > > https://github.com/apache/geode-native/tree/rel/v1.10.0.RC2 > > > > Source and binary files: > > https://dist.apache.org/repos/dist/dev/geode/1.10.0.RC2/ > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachegeode-1059 > > > > Geode's KEYS file containing PGP keys we use to sign the release: > > https://github.com/apache/geode/blob/develop/KEYS > > > > PS: Command to run geode-examples: ./gradlew -PgeodeReleaseUrl= > >
Re: Question about rolling back a Geode upgrade
Hi Anthony, That's an option but, as you say, the cost in infrastructure is high and there are also other problems to solve like how to do the switch between systems and how to assure the data consistency among them. I was thinking that in many cases it might be possible to support a rolling downgrade similar to the rolling upgrade given that the rolling upgrade already allows the coexistence of old and new members in a cluster. -Alberto On 23/9/19 15:55, Anthony Baker wrote: > Have you considered using a blue / green deployment approach? It provides > more flexibility for these scenarios though the infrastructure cost is high. > > Anthony > > >> On Sep 23, 2019, at 5:59 AM, Alberto Gomez wrote: >> >> Hi, >> >> Looking at the Geode documentation I have not found any reference to >> rolling back a Geode upgrade. >> >> Running some tests, I have observed that once a Geode System has been >> upgraded to a later version, it is not possible to rollback the upgrade >> even if no data modifications have been done after the upgrade. >> >> The system protects itself in several places: gfsh does not allow you to >> connect to a newer version of Geode, the Oplog files store the version >> of the server which prevents an older server to start from a file from a >> newer server, the cluster also does not allow older members to join a >> cluster with newer members and there are probably other protections I >> did not hit. >> >> Even if you tamper with some of those protections, you can run into >> trouble due to compatibility issues. I ran into one when I lifted up the >> requirement to have the same gfsh versions using versions 1.8 and 1.10 >> because it seems there is some configuration exchanged in Json format >> whose format has changed between those two versions. >> >> My question is that if it has ever been considered to support rollback >> of Geode upgrades (preferably in rolling mode), at least between systems >> under the same major version. In our experience customers often require >> the rollback of upgrades. >> >> Thanks in advance for your help, >> >> -Alberto G. >>
Re: Question about rolling back a Geode upgrade
Have you considered using a blue / green deployment approach? It provides more flexibility for these scenarios though the infrastructure cost is high. Anthony > On Sep 23, 2019, at 5:59 AM, Alberto Gomez wrote: > > Hi, > > Looking at the Geode documentation I have not found any reference to > rolling back a Geode upgrade. > > Running some tests, I have observed that once a Geode System has been > upgraded to a later version, it is not possible to rollback the upgrade > even if no data modifications have been done after the upgrade. > > The system protects itself in several places: gfsh does not allow you to > connect to a newer version of Geode, the Oplog files store the version > of the server which prevents an older server to start from a file from a > newer server, the cluster also does not allow older members to join a > cluster with newer members and there are probably other protections I > did not hit. > > Even if you tamper with some of those protections, you can run into > trouble due to compatibility issues. I ran into one when I lifted up the > requirement to have the same gfsh versions using versions 1.8 and 1.10 > because it seems there is some configuration exchanged in Json format > whose format has changed between those two versions. > > My question is that if it has ever been considered to support rollback > of Geode upgrades (preferably in rolling mode), at least between systems > under the same major version. In our experience customers often require > the rollback of upgrades. > > Thanks in advance for your help, > > -Alberto G. >
Reviewers for PR #3888
Hi, Could I please get some extra reviewers for https://github.com/apache/geode/pull/3888? This PR is about GEODE-7049: Add timeout parameter to Java client Execution::execute() methods (https://jira.apache.org/jira/browse/GEODE-7049). Thanks, -Alberto G.
Question about rolling back a Geode upgrade
Hi, Looking at the Geode documentation I have not found any reference to rolling back a Geode upgrade. Running some tests, I have observed that once a Geode System has been upgraded to a later version, it is not possible to rollback the upgrade even if no data modifications have been done after the upgrade. The system protects itself in several places: gfsh does not allow you to connect to a newer version of Geode, the Oplog files store the version of the server which prevents an older server to start from a file from a newer server, the cluster also does not allow older members to join a cluster with newer members and there are probably other protections I did not hit. Even if you tamper with some of those protections, you can run into trouble due to compatibility issues. I ran into one when I lifted up the requirement to have the same gfsh versions using versions 1.8 and 1.10 because it seems there is some configuration exchanged in Json format whose format has changed between those two versions. My question is that if it has ever been considered to support rollback of Geode upgrades (preferably in rolling mode), at least between systems under the same major version. In our experience customers often require the rollback of upgrades. Thanks in advance for your help, -Alberto G.
