Build failed in Jenkins: Geode-nightly #924

See Changes: [sjewll] GEODE-3423: Provide support for running parallel docker builds in [jdeppe] GEODE-3423: Use openjdk:8 as the base [dbarnes] GEODE-3395 Variable-ize product version and name in user guide -

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user kohlmu-pivotal commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133353995 --- Diff: geode-core/src/main/java/org/apache/geode/internal/tcp/ConnectionTable.java --- @@ -929,10 +929,6 @@ protected void

Re: Permission to assign and close JIRA tickets

done > On Aug 15, 2017, at 9:39 AM, Alexander Murmann wrote: > > amurmann > > Thanks! > > On Tue, Aug 15, 2017 at 9:05 AM, Anthony Baker wrote: > >> What’s your JIRA username? >> >>> On Aug 15, 2017, at 8:40 AM, Alexander Murmann

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user bschuchardt commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133325744 --- Diff: geode-core/src/main/java/org/apache/geode/internal/net/SocketCloser.java --- @@ -96,46 +99,55 @@ public int getMaxThreads() { return

Re: Review Request 61676: Release the lock held when beforeCompletion failed with CommitConflictException

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61676/#review183009 --- Ship it! Ship It! - Nick Reich On Aug. 15, 2017, 10:47

Review Request 61676: Release the lock held when beforeCompletion failed with CommitConflictException

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61676/ --- Review request for geode, anilkumar gingade, Darrel Schneider, Lynn Gallinat,

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

--- Spring Data GemFire > Nightly-ApacheGeode > #648 was successful. --- Scheduled 2029 tests in total. https://build.spring.io/browse/SGF-NAG-648/ -- This

Re: continuous query internal mechanism questions

In Geode, high availability for subscription events are achieved by having redundant event-queues (HAQueues) on multiple severs; this is configured using redundancy-level with client connection. Based on the redundancy level, the client register CQs on multiple servers. During the subscription

Re: Review Request 61563: GEODE-3383: Refactor deploy tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61563/#review183006 --- Ship it! Ship It! - Kirk Lund On Aug. 11, 2017, 9:52 p.m.,

Re: Review Request 61627: GEODE-3437: Fix list and describe region tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61627/#review183007 --- Ship it! Ship It! - Kirk Lund On Aug. 14, 2017, 10:40 p.m.,

Re: Review Request 61671: GEODE-3328: fix testAddGemFirePropertyFileToCommandLineNew on Windows

> On Aug. 15, 2017, 9:38 p.m., Ken Howe wrote: > > geode-core/src/test/java/org/apache/geode/management/internal/cli/commands/GfshCommandJUnitTest.java > > Line 411 (original), 411 (patched) > > > > > > Why was this

Re: Review Request 61671: GEODE-3328: fix testAddGemFirePropertyFileToCommandLineNew on Windows

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61671/#review182999 --- Ship it!

Re: Review Request 61411: GEODE-3286 Failing to cleanup connections from ConnectionTable receiver table (corrected "stopped" check in previous fix)

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61411/#review182998 --- Ship it! Ship It! - Udo Kohlmeyer On Aug. 3, 2017, 11:01

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

Hi Jared, Short answer: No, Longer answer: Ask Infra ;) We are generally running on VMs with multiple Jenkins executors, which means we could be sharing the box with other jobs. We have been piggybacking on other project's systems so far, trying to find 'available' systems. I have a feeling this

Re: Review Request 61672: GEODE-3249: internal messages should require credentials

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61672/#review182997 --- Ship it! Ship It! - Udo Kohlmeyer On Aug. 15, 2017, 8:46

Review Request 61672: GEODE-3249: internal messages should require credentials

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

[GitHub] geode pull request #714: GEODE-3412: adding files missing from last commit

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/714 --- 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 wishes so, or if the feature is

Passed: apache/geode#3570 (GEODE-3328 - 27475ea)

Build Update for apache/geode - Build: #3570 Status: Passed Duration: 20 minutes and 45 seconds Commit: 27475ea (GEODE-3328) Author: Kirk Lund Message: GEODE-3328: fix testAddGemFirePropertyFileToCommandLineNew on Windows Modification of ca4b81 committed by

Review Request 61671: GEODE-3328: fix testAddGemFirePropertyFileToCommandLineNew on Windows

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61671/ --- Review request for geode, Jinmei Liao, Jared Stewart, and Ken Howe. Bugs:

[GitHub] geode pull request #714: GEODE-3412: adding files missing from last commit

GitHub user WireBaron opened a pull request: https://github.com/apache/geode/pull/714 GEODE-3412: adding files missing from last commit This is adding some files which should have been in the last commit for this feature. Thank you for submitting a contribution to Apache

[GitHub] geode pull request #713: Feature/geode 3412

Github user WireBaron closed the pull request at: https://github.com/apache/geode/pull/713 --- 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 wishes so, or if the feature is

[GitHub] geode pull request #713: Feature/geode 3412

GitHub user WireBaron opened a pull request: https://github.com/apache/geode/pull/713 Feature/geode 3412 This is adding some files which should have been in the last commit for this feature. Thank you for submitting a contribution to Apache Geode. In order to

[GitHub] geode pull request #712: GEODE-3434: Allow the modules to be interoperable w...

Github user jhuynh1 commented on a diff in the pull request: https://github.com/apache/geode/pull/712#discussion_r133270585 --- Diff: geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/LuceneEventListener.java --- @@ -34,7 +34,6 @@ import

[GitHub] geode pull request #712: GEODE-3434: Allow the modules to be interoperable w...

Github user DivineEnder commented on a diff in the pull request: https://github.com/apache/geode/pull/712#discussion_r133268501 --- Diff: geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/LuceneEventListener.java --- @@ -34,7 +34,6 @@ import

Re: continuous query internal mechanism questions

I am not quite sure how native client registers cqs. From my understanding: with the java api, I believe there is only one message (ExecuteCQ message) that is executed on the server side and then replicated to the other nodes through the profile (OperationMessage). It seems the extra ExecuteCQ

[GitHub] geode pull request #712: GEODE-3434: Allow the modules to be interoperable w...

Github user DivineEnder commented on a diff in the pull request: https://github.com/apache/geode/pull/712#discussion_r133256792 --- Diff: geode-assembly/src/test/java/org/apache/geode/session/tests/ContainerInstall.java --- @@ -18,6 +18,7 @@ import java.io.FileInputStream;

[GitHub] geode pull request #707: GEODE-3412: Add simple authentication flow to proto...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/707 --- 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 wishes so, or if the feature is

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user kohlmu-pivotal commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133255222 --- Diff: geode-core/src/main/java/org/apache/geode/internal/net/SocketCloser.java --- @@ -96,46 +99,55 @@ public int getMaxThreads() {

Re: continuous query - high availability and assurance

Hi there Roi, If you have turned on Durable Client-Server messaging then the cluster should deal with the failure of a client. All client bound messages would have a "at-least-once"

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user hiteshk25 commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133251379 --- Diff: geode-core/src/main/java/org/apache/geode/internal/net/SocketCloser.java --- @@ -96,46 +99,55 @@ public int getMaxThreads() { return

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user hiteshk25 commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133249141 --- Diff: geode-core/src/main/java/org/apache/geode/internal/tcp/ConnectionTable.java --- @@ -929,10 +929,6 @@ protected void

Re: continuous query - high availability and assurance

+ user On Tue, Aug 15, 2017 at 10:17 AM, Roi Apelker wrote: > Hi, > > I have been working on an issue related to continuous query mechanism, and > I would like to know if this mechanism, with High availability, assures > 100% data integrity? > > For example, if I have 2

[GitHub] geode pull request #707: GEODE-3412: Add simple authentication flow to proto...

Github user pivotal-amurmann commented on a diff in the pull request: https://github.com/apache/geode/pull/707#discussion_r133246611 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/ServerConnectionFactory.java --- @@ -22,59 +22,89 @@

continuous query - high availability and assurance

Hi, I have been working on an issue related to continuous query mechanism, and I would like to know if this mechanism, with High availability, assures 100% data integrity? For example, if I have 2 nodes where a client registered to CQ, and one node fails, is there any scenario, in which a

[GitHub] geode pull request #683: GEODE-3314 - additional refactoring for developer Q...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/683 --- 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 wishes so, or if the feature is

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user kohlmu-pivotal commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133238599 --- Diff: geode-core/src/main/java/org/apache/geode/internal/net/SocketCloser.java --- @@ -96,46 +99,55 @@ public int getMaxThreads() {

Re: Permission to assign and close JIRA tickets

amurmann Thanks! On Tue, Aug 15, 2017 at 9:05 AM, Anthony Baker wrote: > What’s your JIRA username? > > > On Aug 15, 2017, at 8:40 AM, Alexander Murmann > wrote: > > > > Good morning, > > > > Can I please get permission to assign JIRA tickets to myself

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user kohlmu-pivotal commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133238417 --- Diff: geode-core/src/main/java/org/apache/geode/internal/net/SocketCloser.java --- @@ -144,35 +156,22 @@ private boolean isClosed() { *

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user WireBaron commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133230687 --- Diff: geode-core/src/main/java/org/apache/geode/internal/net/SocketCloser.java --- @@ -144,35 +156,22 @@ private boolean isClosed() { * called

[GitHub] geode pull request #702: GEODE-3416: Reduce synchronization blockages in Soc...

Github user WireBaron commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133230527 --- Diff: geode-core/src/main/java/org/apache/geode/internal/net/SocketCloser.java --- @@ -96,46 +99,55 @@ public int getMaxThreads() { return

[GitHub] geode issue #649: GEODE-2997: Change new protocol GetAllResponse.

Github user kohlmu-pivotal commented on the issue: https://github.com/apache/geode/pull/649 @galen-pivotal is this PR active anymore? --- 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

Re: Permission to assign and close JIRA tickets

What’s your JIRA username? > On Aug 15, 2017, at 8:40 AM, Alexander Murmann wrote: > > Good morning, > > Can I please get permission to assign JIRA tickets to myself as well as > close them? > > Thank you!

[GitHub] geode pull request #700: GEODE-3386 - Make KeyedErrorResponse & ErrorRespons...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/700 --- 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 wishes so, or if the feature is

Permission to assign and close JIRA tickets

Good morning, Can I please get permission to assign JIRA tickets to myself as well as close them? Thank you!

continuous query internal mechanism questions

Hi, I have been examining the continuous query registration mechanism for quite some time This is related to an issue that I have, where sometimes a node crashes (1 node out of 2), and the other one does not send CQ events. The CQ is registered on a partitioned region which resides on these 2