Build failed in Jenkins: Geode-nightly #960

2017-09-20 Thread Apache Jenkins Server
See Changes: [github] GEODE-2818 Document gfsh aliases (#775) [dschneider] GEODE-3626: Fix relative path support for snapshots [gosullivan] GEODE-3548 Add logging to new protocol code [github] GEODE-3609 Small Acc

Build failed in Jenkins: Geode-nightly-flaky #127

2017-09-20 Thread Apache Jenkins Server
See -- [...truncated 116.08 KB...] Download https://repo1.maven.org/maven2/io/springfox/springfox-swagger-ui/2.6.1/springfox-swagger-ui-2.6.1.pom Download https://repo1.maven.org/mave

Re: [DISCUSS] Addition of isValid API to Index interface

2017-09-20 Thread Nabarun Nag
The PR #768 has been created for this issue and also GEODE-3520 has been changed to reflect this requirement. Regards Nabarun On Thu, Sep 14, 2017 at 5:29 PM Nabarun Nag wrote: > Thanks you guys for the review. I will revert the GEODE-3520 ticket to > reflect that invalidate should happen for b

[RESULT][VOTE] Apache Geode release - v1.2.1 RC4

2017-09-20 Thread Anthony Baker
The vote passes with 4 +1 votes (3 binding). +1 Dan Smith (binding) +1 William Markito Oliveira (binding) +1 Karen Miller (binding) +1 Dick Cavender Vote thread: http://mail-archives.apache.org/mod_mbox/geode-dev/201709.mbox/%3ccaewge-ft0erojncomtzvrzl8fnxreuhdryunblwt5cft8xq...@mail.gmail.com%3e

Passed: apache/geode#3918 (rel/v1.2.1 - 0b881b5)

2017-09-20 Thread Travis CI
Build Update for apache/geode - Build: #3918 Status: Passed Duration: 9 minutes and 14 seconds Commit: 0b881b5 (rel/v1.2.1) Author: Bruce Schuchardt Message: GEODE-3249 Validate internal client/server messages This change leaves the security hole in place but

Errored: apache/geode-examples#65 (rel/v1.2.1 - 5d034de)

2017-09-20 Thread Travis CI
Build Update for apache/geode-examples - Build: #65 Status: Errored Duration: 1 minute and 0 seconds Commit: 5d034de (rel/v1.2.1) Author: Dan Smith Message: GEODE-3199: Make signing with a gpg key optional Make it optional to sign the archives with a gpg key,

Re: [DISCUSS] Addition of isValid API to Index interface

2017-09-20 Thread Swapnil Bawaskar
Sorry for not reading this thread earlier, but I was wondering what is the point of just invalidating the index and having it lie around if it is not going to be used? Can we just drop the index instead, and log a warning message to that effect? This will free up the memory used by the index and wi

Re: [DISCUSS] Addition of isValid API to Index interface

2017-09-20 Thread Anilkumar Gingade
Agree, invalid index should not be kept...For PRs its tricky, each bucket-region has its own index, if an index is invalidated on a bucket region, do we need to remove that index from all the bucket regions (local and remote)? I guess, yes... -Anil. On Wed, Sep 20, 2017 at 2:58 PM, Swapnil Bawas

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

2017-09-20 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #684 was successful. --- Scheduled 2044 tests in total. https://build.spring.io/browse/SGF-NAG-684/ -- This

Re: [DISCUSS] Addition of isValid API to Index interface

2017-09-20 Thread Nabarun Nag
Hi Swapnil, There were few factors we considered before going with just invalidating the index rather than destroying the index. 1. Debugging reasons : If the indexes were destroyed and logs roll over, and suddenly we see that indexes have disappeared, it will be tough to differentiate between whet

Re: [DISCUSS] Addition of isValid API to Index interface

2017-09-20 Thread Swapnil Bawaskar
Thanks for the explanation Naba, please find my reply below: 1. Debugging: If we log a warning, that should get noticed immediately, so I don't think we need to worry about logs rolling. 2. Performance for a single put: We can always schedule an async task to drop the index. On Wed, Sep 20, 2017 a