[jira] [Reopened] (GEODE-857) SystemFailure.stopWatchdog will always wait 1 second
[
https://issues.apache.org/jira/browse/GEODE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker reopened GEODE-857:
-
I ran into a failure with this unit test:
{code:java}
com.gemstone.gemfire.SystemFailureJUnitTest > testStopThreads FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
com.gemstone.gemfire.SystemFailureJUnitTest.testStopThreads(SystemFailureJUnitTest.java:51)
{code}
> SystemFailure.stopWatchdog will always wait 1 second
>
>
> Key: GEODE-857
> URL: https://issues.apache.org/jira/browse/GEODE-857
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M2
>
>
> This method is called during distributed system shutdown. It synchronizes on
> failureSync, and then calls Thread.join on the watchDog thread and waits one
> second.
> The watchDog thread can't wake up until it can get the failureSync, so the
> Thread.join call will always end up waiting.
> This adds a lot of time to our tests, because we often disconnect the
> distributed system.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-918) Add apache license headers to generated poms
[
https://issues.apache.org/jira/browse/GEODE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144000#comment-15144000
]
Anthony Baker commented on GEODE-918:
-
The generated pom now carries the ASF header:
{code:xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
org.apache.geode
...
{code}
> Add apache license headers to generated poms
>
>
> Key: GEODE-918
> URL: https://issues.apache.org/jira/browse/GEODE-918
> Project: Geode
> Issue Type: Sub-task
>Reporter: Dan Smith
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-918) Add apache license headers to generated poms
[ https://issues.apache.org/jira/browse/GEODE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-918. - Resolution: Fixed Fix Version/s: 1.0.0-incubating.M2 > Add apache license headers to generated poms > > > Key: GEODE-918 > URL: https://issues.apache.org/jira/browse/GEODE-918 > Project: Geode > Issue Type: Sub-task >Reporter: Dan Smith >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-26) Apache Geode 'build.gradle' inappropriately declares mavenLocal() in Repository declarations.
[
https://issues.apache.org/jira/browse/GEODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker resolved GEODE-26.
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M2
> Apache Geode 'build.gradle' inappropriately declares mavenLocal() in
> Repository declarations.
> -
>
> Key: GEODE-26
> URL: https://issues.apache.org/jira/browse/GEODE-26
> Project: Geode
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0-incubating
> Environment: Any Gradle capable env for building Apache Geode.
>Reporter: John Blum
>Assignee: Anthony Baker
>Priority: Critical
> Labels: ApacheGeode, Gradle, Repositories, build.gradle,
> mavenLocal()
> Fix For: 1.0.0-incubating.M2
>
>
> In the
> [build.gradle|https://github.com/apache/incubator-geode/blob/master/build.gradle#L9-10]
> file of the _Apache Geode_ project, the {{repositories}} declaration
> inappropriately contains {{mavenLocal()}}.
> The problem with this is, if developers contributing patches to the _Apache
> Geode_ codebase inadvertently include a "local" dependency to the
> dependencies defined in Geode's {{build.gradle}} file(s), then Geode will
> build locally but not when the patch is submitted and Geode's build
> infrastructure runs the same build with the code changes dependent on the
> (possibly) non-existent, non-resolvable dependency, because, it only exists
> in the developers "local" Maven (env) repository ({{~/.m2/repository}}).
> There are other preferred ways in which users can specify the use of
> {{mavenLocal()}} to affect their work _Apache Geode_ codebase/build without
> modifying the actual _Apache Geode_ {{build.gradle}} file.
> For instance, a developer can created a {{~/.gradle/init.gradle}} script to
> tweak "available" Repositories, like so...
> {code:xml}
> allprojects {
> repositories {
> mavenLocal()
> maven { url "http://maven.domain.com/path/to/another/maven/repo"}
>// etc...
> }
> }
> {code}
> See the [Gradle documentation on
> init.scripts|https://docs.gradle.org/current/userguide/init_scripts.html] for
> more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-918) Add apache license headers to generated poms
[ https://issues.apache.org/jira/browse/GEODE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker reassigned GEODE-918: --- Assignee: Anthony Baker > Add apache license headers to generated poms > > > Key: GEODE-918 > URL: https://issues.apache.org/jira/browse/GEODE-918 > Project: Geode > Issue Type: Sub-task >Reporter: Dan Smith >Assignee: Anthony Baker > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-26) Apache Geode 'build.gradle' inappropriately declares mavenLocal() in Repository declarations.
[
https://issues.apache.org/jira/browse/GEODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker reassigned GEODE-26:
--
Assignee: Anthony Baker (was: Mark Bretl)
> Apache Geode 'build.gradle' inappropriately declares mavenLocal() in
> Repository declarations.
> -
>
> Key: GEODE-26
> URL: https://issues.apache.org/jira/browse/GEODE-26
> Project: Geode
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0-incubating
> Environment: Any Gradle capable env for building Apache Geode.
>Reporter: John Blum
>Assignee: Anthony Baker
>Priority: Critical
> Labels: ApacheGeode, Gradle, Repositories, build.gradle,
> mavenLocal()
>
> In the
> [build.gradle|https://github.com/apache/incubator-geode/blob/master/build.gradle#L9-10]
> file of the _Apache Geode_ project, the {{repositories}} declaration
> inappropriately contains {{mavenLocal()}}.
> The problem with this is, if developers contributing patches to the _Apache
> Geode_ codebase inadvertently include a "local" dependency to the
> dependencies defined in Geode's {{build.gradle}} file(s), then Geode will
> build locally but not when the patch is submitted and Geode's build
> infrastructure runs the same build with the code changes dependent on the
> (possibly) non-existent, non-resolvable dependency, because, it only exists
> in the developers "local" Maven (env) repository ({{~/.m2/repository}}).
> There are other preferred ways in which users can specify the use of
> {{mavenLocal()}} to affect their work _Apache Geode_ codebase/build without
> modifying the actual _Apache Geode_ {{build.gradle}} file.
> For instance, a developer can created a {{~/.gradle/init.gradle}} script to
> tweak "available" Repositories, like so...
> {code:xml}
> allprojects {
> repositories {
> mavenLocal()
> maven { url "http://maven.domain.com/path/to/another/maven/repo"}
>// etc...
> }
> }
> {code}
> See the [Gradle documentation on
> init.scripts|https://docs.gradle.org/current/userguide/init_scripts.html] for
> more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-26) Apache Geode 'build.gradle' inappropriately declares mavenLocal() in Repository declarations.
[
https://issues.apache.org/jira/browse/GEODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143990#comment-15143990
]
ASF subversion and git services commented on GEODE-26:
--
Commit ee7b041adb7be0debc16e631ca4024b8d8652d53 in incubator-geode's branch
refs/heads/develop from [~amb]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=ee7b041 ]
GEODE-26: Remove mavenLocal from repositories
> Apache Geode 'build.gradle' inappropriately declares mavenLocal() in
> Repository declarations.
> -
>
> Key: GEODE-26
> URL: https://issues.apache.org/jira/browse/GEODE-26
> Project: Geode
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0-incubating
> Environment: Any Gradle capable env for building Apache Geode.
>Reporter: John Blum
>Assignee: Mark Bretl
>Priority: Critical
> Labels: ApacheGeode, Gradle, Repositories, build.gradle,
> mavenLocal()
>
> In the
> [build.gradle|https://github.com/apache/incubator-geode/blob/master/build.gradle#L9-10]
> file of the _Apache Geode_ project, the {{repositories}} declaration
> inappropriately contains {{mavenLocal()}}.
> The problem with this is, if developers contributing patches to the _Apache
> Geode_ codebase inadvertently include a "local" dependency to the
> dependencies defined in Geode's {{build.gradle}} file(s), then Geode will
> build locally but not when the patch is submitted and Geode's build
> infrastructure runs the same build with the code changes dependent on the
> (possibly) non-existent, non-resolvable dependency, because, it only exists
> in the developers "local" Maven (env) repository ({{~/.m2/repository}}).
> There are other preferred ways in which users can specify the use of
> {{mavenLocal()}} to affect their work _Apache Geode_ codebase/build without
> modifying the actual _Apache Geode_ {{build.gradle}} file.
> For instance, a developer can created a {{~/.gradle/init.gradle}} script to
> tweak "available" Repositories, like so...
> {code:xml}
> allprojects {
> repositories {
> mavenLocal()
> maven { url "http://maven.domain.com/path/to/another/maven/repo"}
>// etc...
> }
> }
> {code}
> See the [Gradle documentation on
> init.scripts|https://docs.gradle.org/current/userguide/init_scripts.html] for
> more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-918) Add apache license headers to generated poms
[ https://issues.apache.org/jira/browse/GEODE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143991#comment-15143991 ] ASF subversion and git services commented on GEODE-918: --- Commit a928ea7a76e887d5514ad98739d87e6ee2bb2278 in incubator-geode's branch refs/heads/develop from [~amb] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=a928ea7 ] GEODE-918: Add ASF header to generate pom files > Add apache license headers to generated poms > > > Key: GEODE-918 > URL: https://issues.apache.org/jira/browse/GEODE-918 > Project: Geode > Issue Type: Sub-task >Reporter: Dan Smith > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-913) Refactor DistributionConfig to ease the addition of new configuration
[ https://issues.apache.org/jira/browse/GEODE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143920#comment-15143920 ] ASF subversion and git services commented on GEODE-913: --- Commit 700599052b74072115b4b17b25de23dcd78cd8c2 in incubator-geode's branch refs/heads/develop from [~jinmeiliao] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=7005990 ] GEODE-913: refactor AbstractDistributionConfig * use annotations to annotate the config attributes and its setters/getters/checkers * delete multiple huge if/else statements to use annoations * delete unnecessary checks use annotated checkers. * delete all isXXModifiers to use attribute lists to denote if the attribute is modifiable or not. > Refactor DistributionConfig to ease the addition of new configuration > - > > Key: GEODE-913 > URL: https://issues.apache.org/jira/browse/GEODE-913 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Assignee: Jinmei Liao > > Current DistributionConfigImpl has numerous > getter/setting/checkModifiable/isModifiable for every attribute. This make > adding new attribute hard to follow. Explore ways to refactor this and add > unit tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-657) Two backups occurring simultaneously can cause the BackupLock to be obtained but not released
[
https://issues.apache.org/jira/browse/GEODE-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143863#comment-15143863
]
ASF subversion and git services commented on GEODE-657:
---
Commit 2b2e619e35a44c6e5f1f9881b5fba46d884a3934 in incubator-geode's branch
refs/heads/develop from [~barry.oglesby]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=2b2e619 ]
GEODE-657: Prevent two backups from happening at the same time
Adding a dlock to prevent two backups from occuring at the same time.
> Two backups occurring simultaneously can cause the BackupLock to be obtained
> but not released
> -
>
> Key: GEODE-657
> URL: https://issues.apache.org/jira/browse/GEODE-657
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Barry Oglesby
>Assignee: Dan Smith
>
> Backup is done in three phases, namely {{FlushToDiskRequest}},
> {{PrepareBackupRequest}} and {{FinishBackupRequest}}.
> Here is some debugging in the locator showing the backup phases:
> {noformat}
> [warning 2015/12/01 14:37:38.783 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers STARTED
> [warning 2015/12/01 14:37:38.794 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send FlushToDiskRequest
> [warning 2015/12/01 14:37:38.977 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to FlushToDiskRequest
> [warning 2015/12/01 14:37:38.977 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send PrepareBackupRequest
> [warning 2015/12/01 14:37:38.984 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to PrepareBackupRequest
> [warning 2015/12/01 14:37:38.985 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send FinishBackupRequest
> [warning 2015/12/01 14:37:51.184 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to FinishBackupRequest
> [warning 2015/12/01 14:37:51.184 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers COMPLETED
> {noformat}
> Here is some debugging in one of the members. The others are similar.
> {noformat}
> [warning 2015/12/01 14:37:38.795 PST tid=0x66]
> FlushToDiskRequest createResponse received FlushToDiskRequest
> [warning 2015/12/01 14:37:38.974 PST tid=0x66]
> FlushToDiskRequest createResponse sending FlushToDiskResponse
> [warning 2015/12/01 14:37:38.978 PST tid=0x66]
> PrepareBackupRequest createResponse received PrepareBackupRequest
> [warning 2015/12/01 14:37:38.978 PST tid=0x66]
> PrepareBackupResponse createResponse: About to start backup
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> PrepareBackupResponse createResponse: About to prepare backup
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> BackupLock lockForBackup invoked
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> PrepareBackupRequest createResponse sending PrepareBackupResponse
> [warning 2015/12/01 14:37:38.986 PST tid=0x66]
> FinishBackupRequest createResponse received FinishBackupRequest
> [warning 2015/12/01 14:37:39.970 PST tid=0x66]
> BackupLock unlockForBackup invoked
> [warning 2015/12/01 14:37:49.885 PST tid=0x66]
> FinishBackupRequest createResponse sending FinishBackupResponse
> {noformat}
> Processing the {{PrepareBackupRequest}} is where the {{BackupLock}} is taken
> (in {{BackupLock lockForBackup}}). Processing the {{FinishBackupRequest}} is
> where it is released (in {{BackupLock unlockForBackup}}).
> All members operate independently. If one completes its backup before the
> others, the issue can happen. That member is available to start a new backup,
> but the others aren't.
> In this case, the member successfully processes the {{PrepareBackupRequest}}
> and takes the {{BackupLock}}.
> The other members do not successfully process the {{PrepareBackupRequest}}
> and do not take the {{BackupLock}}:
> {noformat}
> [warning 2015/12/01 14:46:02.447 PST tid=0xd7]
> PrepareBackupRequest createResponse received PrepareBackupRequest
> [warning 2015/12/01 14:46:02.448 PST tid=0xd7]
> PrepareBackupResponse createResponse: About to start backup
> [error 2015/12/01 14:46:02.448 PST tid=0xd7]
> Error processing request class
> com.gemstone.gemfire.admin.internal.PrepareBackupRequest.
> java.io.IOException: Backup already in progress
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.startBackup(GemFireCacheImpl.
[jira] [Commented] (GEODE-657) Two backups occurring simultaneously can cause the BackupLock to be obtained but not released
[
https://issues.apache.org/jira/browse/GEODE-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143864#comment-15143864
]
ASF subversion and git services commented on GEODE-657:
---
Commit 3adb0b8e17436af555e1acbe2bf729bf72365305 in incubator-geode's branch
refs/heads/develop from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3adb0b8 ]
GEODE-657: Add an abort flag to the FinishBackupMessage
If the prepare phase of a backup fails, it can leave the backup in a
prepared state on several nodes. The FinishBackupMessage should always
be sent to cleanup the backup. Adding an abort flag to
FinishBackupMessage and always sending that message regardless of
failures during the prepare.
> Two backups occurring simultaneously can cause the BackupLock to be obtained
> but not released
> -
>
> Key: GEODE-657
> URL: https://issues.apache.org/jira/browse/GEODE-657
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Barry Oglesby
>Assignee: Dan Smith
>
> Backup is done in three phases, namely {{FlushToDiskRequest}},
> {{PrepareBackupRequest}} and {{FinishBackupRequest}}.
> Here is some debugging in the locator showing the backup phases:
> {noformat}
> [warning 2015/12/01 14:37:38.783 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers STARTED
> [warning 2015/12/01 14:37:38.794 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send FlushToDiskRequest
> [warning 2015/12/01 14:37:38.977 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to FlushToDiskRequest
> [warning 2015/12/01 14:37:38.977 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send PrepareBackupRequest
> [warning 2015/12/01 14:37:38.984 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to PrepareBackupRequest
> [warning 2015/12/01 14:37:38.985 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send FinishBackupRequest
> [warning 2015/12/01 14:37:51.184 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to FinishBackupRequest
> [warning 2015/12/01 14:37:51.184 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers COMPLETED
> {noformat}
> Here is some debugging in one of the members. The others are similar.
> {noformat}
> [warning 2015/12/01 14:37:38.795 PST tid=0x66]
> FlushToDiskRequest createResponse received FlushToDiskRequest
> [warning 2015/12/01 14:37:38.974 PST tid=0x66]
> FlushToDiskRequest createResponse sending FlushToDiskResponse
> [warning 2015/12/01 14:37:38.978 PST tid=0x66]
> PrepareBackupRequest createResponse received PrepareBackupRequest
> [warning 2015/12/01 14:37:38.978 PST tid=0x66]
> PrepareBackupResponse createResponse: About to start backup
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> PrepareBackupResponse createResponse: About to prepare backup
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> BackupLock lockForBackup invoked
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> PrepareBackupRequest createResponse sending PrepareBackupResponse
> [warning 2015/12/01 14:37:38.986 PST tid=0x66]
> FinishBackupRequest createResponse received FinishBackupRequest
> [warning 2015/12/01 14:37:39.970 PST tid=0x66]
> BackupLock unlockForBackup invoked
> [warning 2015/12/01 14:37:49.885 PST tid=0x66]
> FinishBackupRequest createResponse sending FinishBackupResponse
> {noformat}
> Processing the {{PrepareBackupRequest}} is where the {{BackupLock}} is taken
> (in {{BackupLock lockForBackup}}). Processing the {{FinishBackupRequest}} is
> where it is released (in {{BackupLock unlockForBackup}}).
> All members operate independently. If one completes its backup before the
> others, the issue can happen. That member is available to start a new backup,
> but the others aren't.
> In this case, the member successfully processes the {{PrepareBackupRequest}}
> and takes the {{BackupLock}}.
> The other members do not successfully process the {{PrepareBackupRequest}}
> and do not take the {{BackupLock}}:
> {noformat}
> [warning 2015/12/01 14:46:02.447 PST tid=0xd7]
> PrepareBackupRequest createResponse received PrepareBackupRequest
> [warning 2015/12/01 14:46:02.448 PST tid=0xd7]
> PrepareBackupResponse createResponse: About to start backup
> [error 2015/12/01 14:46:02.448 PST tid=0xd7]
> Error processing reques
[jira] [Resolved] (GEODE-657) Two backups occurring simultaneously can cause the BackupLock to be obtained but not released
[
https://issues.apache.org/jira/browse/GEODE-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-657.
-
Resolution: Fixed
> Two backups occurring simultaneously can cause the BackupLock to be obtained
> but not released
> -
>
> Key: GEODE-657
> URL: https://issues.apache.org/jira/browse/GEODE-657
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Barry Oglesby
>Assignee: Dan Smith
>
> Backup is done in three phases, namely {{FlushToDiskRequest}},
> {{PrepareBackupRequest}} and {{FinishBackupRequest}}.
> Here is some debugging in the locator showing the backup phases:
> {noformat}
> [warning 2015/12/01 14:37:38.783 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers STARTED
> [warning 2015/12/01 14:37:38.794 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send FlushToDiskRequest
> [warning 2015/12/01 14:37:38.977 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to FlushToDiskRequest
> [warning 2015/12/01 14:37:38.977 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send PrepareBackupRequest
> [warning 2015/12/01 14:37:38.984 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to PrepareBackupRequest
> [warning 2015/12/01 14:37:38.985 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers about to send FinishBackupRequest
> [warning 2015/12/01 14:37:51.184 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers received all responses to FinishBackupRequest
> [warning 2015/12/01 14:37:51.184 PST locator Connection(3)-192.168.2.11> tid=0x99] AdminDistributedSystemImpl
> backupAllMembers COMPLETED
> {noformat}
> Here is some debugging in one of the members. The others are similar.
> {noformat}
> [warning 2015/12/01 14:37:38.795 PST tid=0x66]
> FlushToDiskRequest createResponse received FlushToDiskRequest
> [warning 2015/12/01 14:37:38.974 PST tid=0x66]
> FlushToDiskRequest createResponse sending FlushToDiskResponse
> [warning 2015/12/01 14:37:38.978 PST tid=0x66]
> PrepareBackupRequest createResponse received PrepareBackupRequest
> [warning 2015/12/01 14:37:38.978 PST tid=0x66]
> PrepareBackupResponse createResponse: About to start backup
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> PrepareBackupResponse createResponse: About to prepare backup
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> BackupLock lockForBackup invoked
> [warning 2015/12/01 14:37:38.980 PST tid=0x66]
> PrepareBackupRequest createResponse sending PrepareBackupResponse
> [warning 2015/12/01 14:37:38.986 PST tid=0x66]
> FinishBackupRequest createResponse received FinishBackupRequest
> [warning 2015/12/01 14:37:39.970 PST tid=0x66]
> BackupLock unlockForBackup invoked
> [warning 2015/12/01 14:37:49.885 PST tid=0x66]
> FinishBackupRequest createResponse sending FinishBackupResponse
> {noformat}
> Processing the {{PrepareBackupRequest}} is where the {{BackupLock}} is taken
> (in {{BackupLock lockForBackup}}). Processing the {{FinishBackupRequest}} is
> where it is released (in {{BackupLock unlockForBackup}}).
> All members operate independently. If one completes its backup before the
> others, the issue can happen. That member is available to start a new backup,
> but the others aren't.
> In this case, the member successfully processes the {{PrepareBackupRequest}}
> and takes the {{BackupLock}}.
> The other members do not successfully process the {{PrepareBackupRequest}}
> and do not take the {{BackupLock}}:
> {noformat}
> [warning 2015/12/01 14:46:02.447 PST tid=0xd7]
> PrepareBackupRequest createResponse received PrepareBackupRequest
> [warning 2015/12/01 14:46:02.448 PST tid=0xd7]
> PrepareBackupResponse createResponse: About to start backup
> [error 2015/12/01 14:46:02.448 PST tid=0xd7]
> Error processing request class
> com.gemstone.gemfire.admin.internal.PrepareBackupRequest.
> java.io.IOException: Backup already in progress
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.startBackup(GemFireCacheImpl.java:4315)
> at
> com.gemstone.gemfire.admin.internal.PrepareBackupRequest.createResponse(PrepareBackupRequest.java:87)
> at
> com.gemstone.gemfire.internal.admin.remote.CliLegacyMessage.process(CliLegacyMessage.java:28)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:386)
> at
> com.gemstone.gemfire.distributed.inter
[jira] [Resolved] (GEODE-550) CI failure: FixedPRSinglehopDUnitTest.test_MetadataContents
[ https://issues.apache.org/jira/browse/GEODE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-550. Resolution: Fixed closing this ticket. Reopen and update the exception trace if it fails again. > CI failure: FixedPRSinglehopDUnitTest.test_MetadataContents > --- > > Key: GEODE-550 > URL: https://issues.apache.org/jira/browse/GEODE-550 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Hitesh Khamesra >Assignee: Bruce Schuchardt > Labels: CI > > junit.framework.AssertionFailedError: Event never occurred after 6 ms: > expected no metadata to be refreshed > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.TestCase.fail(TestCase.java:227) > at > dunit.DistributedTestCase.waitForCriterion(DistributedTestCase.java:1171) > at > com.gemstone.gemfire.internal.cache.FixedPRSinglehopDUnitTest.verifyMetadata(FixedPRSinglehopDUnitTest.java:877) > at > com.gemstone.gemfire.internal.cache.FixedPRSinglehopDUnitTest.test_MetadataContents(FixedPRSinglehopDUnitTest.java:264) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54) > at > org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-906) Clean up source header / modification text
[ https://issues.apache.org/jira/browse/GEODE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-906: --- Sprint: 1.0.0-incubating.M2 > Clean up source header / modification text > -- > > Key: GEODE-906 > URL: https://issues.apache.org/jira/browse/GEODE-906 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker > > IdentityArrayList and HashIndexSet should use the standard Apache source > header with a separate modification statement for clarity [1]. > [1] http://www.apache.org/dev/licensing-howto.html#mod-notice > May be required to add to source NOTICE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-904) Update LICENSE for BSD/MIT dependencies
[
https://issues.apache.org/jira/browse/GEODE-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-904:
---
Sprint: 1.0.0-incubating.M2
> Update LICENSE for BSD/MIT dependencies
> ---
>
> Key: GEODE-904
> URL: https://issues.apache.org/jira/browse/GEODE-904
> Project: Geode
> Issue Type: Bug
>Reporter: Anthony Baker
>
> The following files need to be listed in the LICENSE:
> {noformat}
> - ANSIBuffer (BSD) [1]
> - font awesome (front are SIL and css is MIT) [2]
> - normalise.css (MIT) [3]
> - bootstrap (MIT) [3]
> - boot flat (MIT) [4]
> - headjs (MIT) [5]
> - iCheck (MIT) [6]
> - html5shiv (MIT) [7]
> - respond (MIT) [8]
> - polyfill (MIT/BSD) [8]
> - InternalDataSerializer.java [9] contains code from BSD license protobuf
> that should be in license
> 1.
> ./gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/jline/ANSIBuffer.java
> 2. ./gemfire-site/website/content/font/*
> 3. ./gemfire-site/website/content/bootstrap/bootstrap.min.css
> 4. ./gemfire-site/website/content/css/bootflat*
> 5. ./gemfire-site/website/content/js/head.js
> 6. ./gemfire-site/website/content/js/jquery.icheck.js
> 7. ./gemfire-site/website/content/js/html5shiv.js
> 8. ./gemfire-site/website/content/js/respond.min.js
> 9
> ./gemfire-core/src/main/java/com/gemstone/gemfire/internal/InternalDataSerializer.java
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-905) HLL classes should preserve original source header
[ https://issues.apache.org/jira/browse/GEODE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-905: --- Sprint: 1.0.0-incubating.M2 > HLL classes should preserve original source header > -- > > Key: GEODE-905 > URL: https://issues.apache.org/jira/browse/GEODE-905 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker > > Classes in the > gemfire-core/src/main/java/com/gemstone/gemfire/internal/redis/executor/hll/*.java > package have 2 source headers. We should preserve the original header and > remove the extra. We should also explore if we need to add anything to the > LICENSE or NOTICE for this bundled source dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-12) Merge Pulse Source Code
[ https://issues.apache.org/jira/browse/GEODE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-12: -- Sprint: 1.0.0-incubating.M2 > Merge Pulse Source Code > --- > > Key: GEODE-12 > URL: https://issues.apache.org/jira/browse/GEODE-12 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Dan Smith >Assignee: Jinmei Liao > Labels: starter > > Pulse is a web application for monitoring a Geode cluster. Pivotal would like > to contribute pulse to the Geode project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-26) Apache Geode 'build.gradle' inappropriately declares mavenLocal() in Repository declarations.
[
https://issues.apache.org/jira/browse/GEODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-26:
--
Sprint: 1.0.0-incubating.M2
> Apache Geode 'build.gradle' inappropriately declares mavenLocal() in
> Repository declarations.
> -
>
> Key: GEODE-26
> URL: https://issues.apache.org/jira/browse/GEODE-26
> Project: Geode
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0-incubating
> Environment: Any Gradle capable env for building Apache Geode.
>Reporter: John Blum
>Assignee: Mark Bretl
>Priority: Critical
> Labels: ApacheGeode, Gradle, Repositories, build.gradle,
> mavenLocal()
>
> In the
> [build.gradle|https://github.com/apache/incubator-geode/blob/master/build.gradle#L9-10]
> file of the _Apache Geode_ project, the {{repositories}} declaration
> inappropriately contains {{mavenLocal()}}.
> The problem with this is, if developers contributing patches to the _Apache
> Geode_ codebase inadvertently include a "local" dependency to the
> dependencies defined in Geode's {{build.gradle}} file(s), then Geode will
> build locally but not when the patch is submitted and Geode's build
> infrastructure runs the same build with the code changes dependent on the
> (possibly) non-existent, non-resolvable dependency, because, it only exists
> in the developers "local" Maven (env) repository ({{~/.m2/repository}}).
> There are other preferred ways in which users can specify the use of
> {{mavenLocal()}} to affect their work _Apache Geode_ codebase/build without
> modifying the actual _Apache Geode_ {{build.gradle}} file.
> For instance, a developer can created a {{~/.gradle/init.gradle}} script to
> tweak "available" Repositories, like so...
> {code:xml}
> allprojects {
> repositories {
> mavenLocal()
> maven { url "http://maven.domain.com/path/to/another/maven/repo"}
>// etc...
> }
> }
> {code}
> See the [Gradle documentation on
> init.scripts|https://docs.gradle.org/current/userguide/init_scripts.html] for
> more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-876) Add a README file to the binary distribution
[ https://issues.apache.org/jira/browse/GEODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-876: --- Sprint: 1.0.0-incubating.M2 > Add a README file to the binary distribution > > > Key: GEODE-876 > URL: https://issues.apache.org/jira/browse/GEODE-876 > Project: Geode > Issue Type: Bug >Reporter: Swapnil Bawaskar > > The binary distribution is missing README and RUNNING.txt files which are > present in src distribution. > These files should be added to the binary distribution to provide a starting > point for the users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-874) v1.0.0-incubating.M1.RC2: Text file errors in the source distribution
[ https://issues.apache.org/jira/browse/GEODE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-874: --- Sprint: 1.0.0-incubating.M2 > v1.0.0-incubating.M1.RC2: Text file errors in the source distribution > - > > Key: GEODE-874 > URL: https://issues.apache.org/jira/browse/GEODE-874 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Kenneth Howe > > gradlew script is not included in the Geode release packages, but it is > called out in command examples in the following text files in the release > source distribution: > COMPILING.txt > RUNNING.txt > docker/Dockerfile > gemfire-spark-connector/doc/1_building.md > The easy fix is to change "gradlew" to "gradle" in affected files and include > a requirement for the user to install gradle from gradle.org. > There was a similar issue with README.md that was fixed for RC2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-884) Update README.md to include steps to build without running all tests.
[ https://issues.apache.org/jira/browse/GEODE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-884: --- Sprint: 1.0.0-incubating.M2 > Update README.md to include steps to build without running all tests. > - > > Key: GEODE-884 > URL: https://issues.apache.org/jira/browse/GEODE-884 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Udo Kohlmeyer > > Add the steps to the README.md to build GEODE without having to run all tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-52) Remove @author tags from Java source
[ https://issues.apache.org/jira/browse/GEODE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-52: -- Sprint: 1.0.0-incubating.M2 > Remove @author tags from Java source > > > Key: GEODE-52 > URL: https://issues.apache.org/jira/browse/GEODE-52 > Project: Geode > Issue Type: Bug >Reporter: Jakob Homan > > Apache generally frowns on @author tags (as they imply ownership of the code > by a single individual, see > https://blogs.oracle.com/ahe/entry/coding_conventions_and_attribution [best > asf link is not working, annoyingly] and > https://cwiki.apache.org/confluence/display/AVRO/How+To+Contribute as an > example) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-562) Upgrade commons collections to v3.2.2
[ https://issues.apache.org/jira/browse/GEODE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-562: --- Sprint: 1.0.0-incubating.M2 > Upgrade commons collections to v3.2.2 > - > > Key: GEODE-562 > URL: https://issues.apache.org/jira/browse/GEODE-562 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker > > The commons-collections jar v3.2.1 is present on the classpath as part of the > hdfs integration (see GEODE-10). We need to upgrade to version 3.2.2 due to > COLLECTIONS-580. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-903) Update copyright year in website footer
[ https://issues.apache.org/jira/browse/GEODE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-903: --- Sprint: 1.0.0-incubating.M2 > Update copyright year in website footer > --- > > Key: GEODE-903 > URL: https://issues.apache.org/jira/browse/GEODE-903 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker > > The publication year in the copyright notice should be updated to 2016: > gemfire-site/website/layouts/footer.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-901) Remove invalid source headers
[
https://issues.apache.org/jira/browse/GEODE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-901:
---
Sprint: 1.0.0-incubating.M2
> Remove invalid source headers
> -
>
> Key: GEODE-901
> URL: https://issues.apache.org/jira/browse/GEODE-901
> Project: Geode
> Issue Type: Bug
>Reporter: Anthony Baker
>
> ResultsBagJUnitTest contains an invalid header that should be removed.
> {code}
> //
> // ResultsBagJUnitTest.java
> // gemfire
> //
> // Created by Eric Zoerner on 2/13/08.
> // Copyright 2008 __MyCompanyName__. All rights reserved.
> //
> {code}
> Also, QueryFromClauseCanonicalizationJUnitTest.java has this comment which
> should be removed:
> {code}
> /*
>*
>* Copyright (C) GemStone Systems, Inc. 2000-2004. All Rights Reserved.
>*
>*
>*/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-914) Review NOTICE (again)
[ https://issues.apache.org/jira/browse/GEODE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-914: --- Sprint: 1.0.0-incubating.M2 > Review NOTICE (again) > - > > Key: GEODE-914 > URL: https://issues.apache.org/jira/browse/GEODE-914 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker > > Thanks to great feedback from IPMC on the general@ list we have a better idea > of how to construct the NOTICE file. Please review the following threads and > linked docs: > http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c7ac725d7-ecec-45ff-95ae-bd77d1b18...@pivotal.io%3e > http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3cCADY20s5nLc9zLKoNYf_8W8vf+Q6ri=-utanuaxzgorbysxw...@mail.gmail.com%3e > https://nifi.apache.org/licensing-guide.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-944) ServerLauncherJUnitTest fails when ISP redirects DNS failures
[
https://issues.apache.org/jira/browse/GEODE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-944:
---
Sprint: 1.0.0-incubating.M2
> ServerLauncherJUnitTest fails when ISP redirects DNS failures
> -
>
> Key: GEODE-944
> URL: https://issues.apache.org/jira/browse/GEODE-944
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>
> This test fails when using a DNS server that redirects DNS lookup failures to
> an ISP's search page.
> {noformat}
> om.gemstone.gemfire.distributed.LocatorLauncherJUnitTest >
> testSetBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> com.gemstone.gemfire.distributed.ServerLauncherJUnitTest >
> testSetServerBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> {noformat}
> The test is expecting to see an UnknownHostException, but because the ISP
> returns a real IP address rather than the expected DNS lookup failure, the
> test doesn't see the exception.
> We could probably just Use junit's Assume to cause these tests to get skipped
> in this environment.
> See this email thread for more details:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3CCAOqetn_FTeV9ee4R8mkg4Y%3D8a%3DjedgfdOSjDxcnj2N7W02maCw%40mail.gmail.com%3E
> A little more information on DNS hijacking:
> http://www.dnsknowledge.com/whatis/nxdomain-non-existent-domain-2/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-945) Javadoc references to javax.transaction classes are causing build warnings
[
https://issues.apache.org/jira/browse/GEODE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-945:
---
Sprint: 1.0.0-incubating.M2
> Javadoc references to javax.transaction classes are causing build warnings
> --
>
> Key: GEODE-945
> URL: https://issues.apache.org/jira/browse/GEODE-945
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Kirk Lund
>Assignee: Dan Smith
>
> Javadoc references to javax.transaction classes are causing build warnings.
> {noformat}
> :pivotalgf-assembly:docsC:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found:
> javax.transaction.UserTransaction#setRollbackOnly
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found:
> javax.transaction.Transaction#registerSynchronization
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found: javax.transaction.Status
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\SynchronizationCommitConflictException.java:27:
> warning - Tag @see: reference not found:
> javax.transaction.UserTransaction#commit
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-946) Source and javadoc artifacts from modules have inconsistent locations
[
https://issues.apache.org/jira/browse/GEODE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-946:
---
Sprint: 1.0.0-incubating.M2
> Source and javadoc artifacts from modules have inconsistent locations
> -
>
> Key: GEODE-946
> URL: https://issues.apache.org/jira/browse/GEODE-946
> Project: Geode
> Issue Type: Bug
> Components: extensions
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>
> The current build process for the modules create artifacts as:
> {noformat}
> extensions> find gemfire-modules/build/libs/
> gemfire-modules/build/libs/
> gemfire-modules/build/libs/gemfire-modules-1.0.0-incubating-SNAPSHOT.jar
> gemfire-modules/build/libs/extensions
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-sources.jar
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-javadoc.jar
> {noformat}
> Both the sources and javadoc jars should be placed directly in {{libs/}} and
> not in {{libs/extensions}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-907) Remove JSON code from pulse
[ https://issues.apache.org/jira/browse/GEODE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-907: --- Sprint: 1.0.0-incubating.M2 > Remove JSON code from pulse > --- > > Key: GEODE-907 > URL: https://issues.apache.org/jira/browse/GEODE-907 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Anthony Baker > > The com.vmware.gemfire.tools.pulse.internal.json package contains the JSON > parser source. We should remove this code in favor of a binary dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-954) When GemFire hostname-for-clients property is set it needs to be displayed on Pulse.
Jinmei Liao created GEODE-954: - Summary: When GemFire hostname-for-clients property is set it needs to be displayed on Pulse. Key: GEODE-954 URL: https://issues.apache.org/jira/browse/GEODE-954 Project: Geode Issue Type: New Feature Components: management Reporter: Jinmei Liao Customer StateFarm is in the process of migrating existing data fabrics from GemFire 664 to GemFire 8.1. State Farm GemFire consumers are used to GFMon in 6.6.4, which has HostName of GemFire clients. Currently, Pulse can't provide that in 8.1/8.2, So it is kind of usability issue for their consumers. We understand new feature can only be delivered to Gemfire 9. But the issue is almost 6 months old. if we can give any estimate of Gemfire 9 or can give the fix in Gemfire 8.X customer will be happy. Also currently, the ticket is own by "Rishitesh Mishra" I think he is not in Gemfire team anymore." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-841) ClientMembershipDUnitTest.testGetNotifiedClients failed
[
https://issues.apache.org/jira/browse/GEODE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-841.
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M2
fixed by the above commit
> ClientMembershipDUnitTest.testGetNotifiedClients failed
> ---
>
> Key: GEODE-841
> URL: https://issues.apache.org/jira/browse/GEODE-841
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: xiaojian zhou
>Assignee: Bruce Schuchardt
> Labels: CI
> Fix For: 1.0.0-incubating.M2
>
>
> Revision: c55a9e462a5ac9a4b023a1ef61acd65f3eab5380
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache30.ClientMembershipDUnitTest$21.run in VM 1 running
> on Host latvia.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:372)
> at dunit.VM.invoke(VM.java:315)
> at dunit.VM.invoke(VM.java:269)
> at
> com.gemstone.gemfire.cache30.ClientMembershipDUnitTest.testGetNotifiedClients(ClientMembershipDUnitTest.java:1570)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor210.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: junit.framework.AssertionFailedError:
> expected::47917:78c26867> but
> was:<10.118.32.95(26397:loner):47917:78c26867>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> com.gemstone.gemfire.cac
[jira] [Updated] (GEODE-917) Rename gradle modules and artifacts to geode, not gemfire
[ https://issues.apache.org/jira/browse/GEODE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-917: --- Component/s: build > Rename gradle modules and artifacts to geode, not gemfire > - > > Key: GEODE-917 > URL: https://issues.apache.org/jira/browse/GEODE-917 > Project: Geode > Issue Type: Sub-task > Components: build >Reporter: Dan Smith > > The gradle modules are currently called gemfire-XXX. They should be > geode-XXX. > The maven artifacts should also not have gemfire in the name - ie > geode-core-1.0.0. This may happen automatically after renaming the gradle > modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-786) Update bundled Spring Data GemFire to 1.7.2 (or 1.8 if available)
[ https://issues.apache.org/jira/browse/GEODE-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-786: --- Component/s: extensions > Update bundled Spring Data GemFire to 1.7.2 (or 1.8 if available) > - > > Key: GEODE-786 > URL: https://issues.apache.org/jira/browse/GEODE-786 > Project: Geode > Issue Type: Bug > Components: extensions >Reporter: Jens Deppe > > Currently we are at SDG 1.5.1. > SDG 1.8 (Hopper) is currently at M1. If it reaches GA by the time this ticket > is worked on, then that version should be included. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-907) Remove JSON code from pulse
[ https://issues.apache.org/jira/browse/GEODE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-907: --- Component/s: management > Remove JSON code from pulse > --- > > Key: GEODE-907 > URL: https://issues.apache.org/jira/browse/GEODE-907 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Anthony Baker > > The com.vmware.gemfire.tools.pulse.internal.json package contains the JSON > parser source. We should remove this code in favor of a binary dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-824) Failure from JGroupsMessengerJUnitTest.testMulticastTest
[
https://issues.apache.org/jira/browse/GEODE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-824:
---
Sprint: 1.0.0-incubating.M2
> Failure from JGroupsMessengerJUnitTest.testMulticastTest
>
>
> Key: GEODE-824
> URL: https://issues.apache.org/jira/browse/GEODE-824
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
> Labels: ci
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails consistently on my ubuntu 15.10 machine. It looks like this
> was introduced in b826b4b0077dc159cbcee68775cc197b025d5586
> I'm running with 27f9c0e8775d50981241a67d792abb3e94adb939.
> {noformat}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-45) Provide a YCSB driver for Geode
[ https://issues.apache.org/jira/browse/GEODE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar resolved GEODE-45. --- Resolution: Fixed > Provide a YCSB driver for Geode > --- > > Key: GEODE-45 > URL: https://issues.apache.org/jira/browse/GEODE-45 > Project: Geode > Issue Type: Task >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > Labels: starter > > YCSB is Yahoo's Cloud serving benchmark: > https://github.com/brianfrankcooper/YCSB. > It already has drivers for a number of projects like cassandra, hbase, > mongoDB, redis, gemfire etc. The GemFire driver needs to be converted so that > it now uses Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-45) Provide a YCSB driver for Geode
[ https://issues.apache.org/jira/browse/GEODE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143302#comment-15143302 ] Swapnil Bawaskar commented on GEODE-45: --- The pull request for geode driver (https://github.com/brianfrankcooper/YCSB/pull/620) has been merged to YCSB. > Provide a YCSB driver for Geode > --- > > Key: GEODE-45 > URL: https://issues.apache.org/jira/browse/GEODE-45 > Project: Geode > Issue Type: Task >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > Labels: starter > > YCSB is Yahoo's Cloud serving benchmark: > https://github.com/brianfrankcooper/YCSB. > It already has drivers for a number of projects like cassandra, hbase, > mongoDB, redis, gemfire etc. The GemFire driver needs to be converted so that > it now uses Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (GEODE-45) Provide a YCSB driver for Geode
[ https://issues.apache.org/jira/browse/GEODE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar closed GEODE-45. - > Provide a YCSB driver for Geode > --- > > Key: GEODE-45 > URL: https://issues.apache.org/jira/browse/GEODE-45 > Project: Geode > Issue Type: Task >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > Labels: starter > > YCSB is Yahoo's Cloud serving benchmark: > https://github.com/brianfrankcooper/YCSB. > It already has drivers for a number of projects like cassandra, hbase, > mongoDB, redis, gemfire etc. The GemFire driver needs to be converted so that > it now uses Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-245) QueryMonitor cancellation is being ignored by query using CompactRangeIndex
[ https://issues.apache.org/jira/browse/GEODE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-245. --- Resolution: Fixed > QueryMonitor cancellation is being ignored by query using CompactRangeIndex > --- > > Key: GEODE-245 > URL: https://issues.apache.org/jira/browse/GEODE-245 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh > > Currently the compact range index does not make a call to > QueryMonitor.isQueryCancelled. This allows queries to continue to run even > after they have surpassed the max query execution time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-886) Passing ENUMs in an IN query possibly returns no results
[ https://issues.apache.org/jira/browse/GEODE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-886. --- Resolution: Fixed > Passing ENUMs in an IN query possibly returns no results > > > Key: GEODE-886 > URL: https://issues.apache.org/jira/browse/GEODE-886 > Project: Geode > Issue Type: Bug >Reporter: Jason Huynh >Assignee: Jason Huynh > > Comparing Pdx serialized enums with enums does not occur properly in the > query engine. A change to type utils to convert an enum into a pdx enum > instance will fix this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-953) SerializableExternalResource and SerializableRuleChain should extend rather than borrow JUnit code
[
https://issues.apache.org/jira/browse/GEODE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-953:
---
Assignee: Kirk Lund
> SerializableExternalResource and SerializableRuleChain should extend rather
> than borrow JUnit code
> --
>
> Key: GEODE-953
> URL: https://issues.apache.org/jira/browse/GEODE-953
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> The override hooks that JUnit Rules provide allows a "before()" method to
> throw any Throwable (including checked exceptions), but does not allow an
> "after()" method to throw checked exceptions. See below:
> {noformat}
> protected void before() throws Throwable {
> protected void after() {
> {noformat}
> The currently committed versions of SerializableExternalResource and
> SerializableRuleChain borrow code from JUnit instead of extending JUnit
> classes to allow changing the after() to have a throws clause:
> {noformat}
> protected void after() {
> {noformat}
> If we choose to follow the JUnit best practice of having after() not perform
> any verifications (or otherwise be a very safe call that cannot throw checked
> exceptions), then we can change these classes to extend the JUnit classes
> instead of borrowing any code from JUnit.
> The Transaction and Off-Heap dunit tests should be changed to NOT perform any
> assertions during tearDown()/after(). There may be additional DUnit and JUnit
> tests that also need to change to bring them into line with the best practice
> Checked exceptions can also be wrapped in an Error or RuntimeException so
> this "limitation" could theoretically be worked around if necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-886) Passing ENUMs in an IN query possibly returns no results
[ https://issues.apache.org/jira/browse/GEODE-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142879#comment-15142879 ] ASF subversion and git services commented on GEODE-886: --- Commit 21d92298ae9ba062d33faae379a8f005a6248ad0 in incubator-geode's branch refs/heads/feature/GEODE-17 from [~huynhja] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=21d9229 ] GEODE-886: Passing ENUMs in an IN query possibly returns no results > Passing ENUMs in an IN query possibly returns no results > > > Key: GEODE-886 > URL: https://issues.apache.org/jira/browse/GEODE-886 > Project: Geode > Issue Type: Bug >Reporter: Jason Huynh >Assignee: Jason Huynh > > Comparing Pdx serialized enums with enums does not occur properly in the > query engine. A change to type utils to convert an enum into a pdx enum > instance will fix this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-268) Remove deprecated OperationContext.isClientUpdate(OperationContext)
[ https://issues.apache.org/jira/browse/GEODE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142886#comment-15142886 ] ASF subversion and git services commented on GEODE-268: --- Commit 99e4aaf450ef8f9e25f5755d03dc73d73085200c in incubator-geode's branch refs/heads/feature/GEODE-17 from [~dbarnes97] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=99e4aaf ] GEODE-268: Adding explanation to OperationContext.isClientUpdate() This closes #43 > Remove deprecated OperationContext.isClientUpdate(OperationContext) > --- > > Key: GEODE-268 > URL: https://issues.apache.org/jira/browse/GEODE-268 > Project: Geode > Issue Type: Sub-task >Reporter: Darrel Schneider > Original Estimate: 1h > Remaining Estimate: 1h > > The method OperationContext.isClientUpdate(OperationContext) is deprecated > and completely unused. It should be easy to remove. > Also take a stab at writing meaningful javadocs for > OperationContext.isClientUpdate(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-730) Optimize single filter join queries
[ https://issues.apache.org/jira/browse/GEODE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142880#comment-15142880 ] ASF subversion and git services commented on GEODE-730: --- Commit d232e25947a8e223f35feb1feffe3150875dc5f5 in incubator-geode's branch refs/heads/feature/GEODE-17 from [~huynhja] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=d232e25 ] GEODE-730: Optimize single filter join queries When executing a join query with additional filters on a single region, we now detect this scenario and instead of creating a CompositeGroupJunction, we create a regular GroupJunction. When we being cutdown and expansion, we then create new compiled comparisons so that we can do an index lookup. For example "select * from /region1 a, /region2 b where a.name = "joe" and a.id = b.id" We will now execute the a.name first assuming an index is present on a.name During cutdown and expand, we determine that the comparison a.id = b.id can create a new compiled comparison because the alias a from a.id matches our original filter a.name. We can evaluate a.id at this point, say id evaluated to 8. So we create a compiled comparison of b.id = 8. We can now do a lookup using the index on b.id. We retrieve these results and place them into a map. This map will be used to continue to derive additional joins if they exist. Such as b.id = c.id, etc... We can continue with the iteration but instead of iterating the entire b region, we can now go over derived results. This also includes a fix to not unlock an index lock when reevaluating an inner query. > Optimize single filter join queries > --- > > Key: GEODE-730 > URL: https://issues.apache.org/jira/browse/GEODE-730 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh > > Currently single filter join queries create a lot of garbage and do the join > before pruning from the filter. We can optimize this for specific cases to > prune prior to joining and only join values that have already passed the > filters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-909) CI failure: MemoryThresholdsOffHeapDUnitTest.testDisabledThresholds
[
https://issues.apache.org/jira/browse/GEODE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142881#comment-15142881
]
ASF subversion and git services commented on GEODE-909:
---
Commit 8db793d9dc55eb73022980deda2626e04c83868c in incubator-geode's branch
refs/heads/feature/GEODE-17 from [~sboorlagadda]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8db793d ]
GEODE-909: fix port issue in MemoryThresholdsOffHeapDUnitTest
* Set cacheserver port to 'zero' in-order for system to pick-up random port
instead of using AvailablePortHelper.
> CI failure: MemoryThresholdsOffHeapDUnitTest.testDisabledThresholds
> ---
>
> Key: GEODE-909
> URL: https://issues.apache.org/jira/browse/GEODE-909
> Project: Geode
> Issue Type: Bug
> Components: offheap
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
> Labels: CI
>
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest$44.call
> in VM 1 running on Host latvia.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest$44.call
> in VM 1 running on Host latvia.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:370)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:313)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:281)
> at
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest.startCacheServer(MemoryThresholdsOffHeapDUnitTest.java:1606)
> at
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest.testDisabledThresholds(MemoryThresholdsOffHeapDUnitTest.java:248)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor118.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>
[jira] [Commented] (GEODE-948) gemfire-modules-assembly should not publish a jar artifact.
[ https://issues.apache.org/jira/browse/GEODE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142884#comment-15142884 ] ASF subversion and git services commented on GEODE-948: --- Commit 8af2858470bc7c7b866a865195a4ff95d43189d2 in incubator-geode's branch refs/heads/feature/GEODE-17 from [~jens.deppe] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8af2858 ] GEODE-948: gemfire-modules-assembly should not publish a jar artifact > gemfire-modules-assembly should not publish a jar artifact. > --- > > Key: GEODE-948 > URL: https://issues.apache.org/jira/browse/GEODE-948 > Project: Geode > Issue Type: Bug > Components: extensions >Reporter: Jens Deppe >Assignee: Jens Deppe > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-17) Provide Integrated Security
[ https://issues.apache.org/jira/browse/GEODE-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142887#comment-15142887 ] ASF subversion and git services commented on GEODE-17: -- Commit c39f8a5f103f0243325e59cd7cdca18c5ea04324 in incubator-geode's branch refs/heads/feature/GEODE-17 from [~jens.deppe] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=c39f8a5 ] Merge branch 'develop' into feature/GEODE-17 > Provide Integrated Security > --- > > Key: GEODE-17 > URL: https://issues.apache.org/jira/browse/GEODE-17 > Project: Geode > Issue Type: New Feature > Components: client/server, docs, management >Reporter: Tushar Khairnar >Assignee: Jens Deppe > Labels: security > > Integrated Security: Purpose of integrated security feature is to provide > uniform authentication and authorization capabilities for all Geode clients. > Geode distributed systems has different clients, some perform cache/region > operations, some perform management operations. In order to authenticate and > authorize these actions we need single consistent framework or interface. > Such interface should allow configuration of access levels from single place > and/or repository. > The key requirements being met here are > - Authentication of all clients from single plugin > - Authorization of cache/data operations (through cache-client and REST) and > managements (GFSH/JMX) operations from single plugin > - Extend existing Client-Server security framework -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-12) Merge Pulse Source Code
[ https://issues.apache.org/jira/browse/GEODE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142885#comment-15142885 ] ASF subversion and git services commented on GEODE-12: -- Commit 28f5391aa7c2a0b2035451843db257de10aa5862 in incubator-geode's branch refs/heads/feature/GEODE-17 from [~jens.deppe] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=28f5391 ] GEODE-12: Minor updates for publishing module artifacts > Merge Pulse Source Code > --- > > Key: GEODE-12 > URL: https://issues.apache.org/jira/browse/GEODE-12 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Dan Smith >Assignee: Jinmei Liao > Labels: starter > > Pulse is a web application for monitoring a Geode cluster. Pivotal would like > to contribute pulse to the Geode project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-946) Source and javadoc artifacts from modules have inconsistent locations
[
https://issues.apache.org/jira/browse/GEODE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142883#comment-15142883
]
ASF subversion and git services commented on GEODE-946:
---
Commit 9fff1ebdee253017a935f6c46285dc02a9697cb9 in incubator-geode's branch
refs/heads/feature/GEODE-17 from [~jens.deppe]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=9fff1eb ]
GEODE-946: Source and javadoc artifacts from modules have inconsistent locations
> Source and javadoc artifacts from modules have inconsistent locations
> -
>
> Key: GEODE-946
> URL: https://issues.apache.org/jira/browse/GEODE-946
> Project: Geode
> Issue Type: Bug
> Components: extensions
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>
> The current build process for the modules create artifacts as:
> {noformat}
> extensions> find gemfire-modules/build/libs/
> gemfire-modules/build/libs/
> gemfire-modules/build/libs/gemfire-modules-1.0.0-incubating-SNAPSHOT.jar
> gemfire-modules/build/libs/extensions
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-sources.jar
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-javadoc.jar
> {noformat}
> Both the sources and javadoc jars should be placed directly in {{libs/}} and
> not in {{libs/extensions}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-557) CI Failure: MemoryThresholdsOffHeapDUnitTest.testDistributedRegionRemotePutRejectionCacheClose port bind issue
[ https://issues.apache.org/jira/browse/GEODE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142882#comment-15142882 ] ASF subversion and git services commented on GEODE-557: --- Commit 466432538391a22942ab9f464354f6365b598a77 in incubator-geode's branch refs/heads/feature/GEODE-17 from [~sboorlagadda] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=4664325 ] GEODE-557: change test to use port zero * Set cacheserver port to 'zero' in-order for system to pick-up random port instead of using AvailablePortHelper. This closes #92 > CI Failure: > MemoryThresholdsOffHeapDUnitTest.testDistributedRegionRemotePutRejectionCacheClose > port bind issue > -- > > Key: GEODE-557 > URL: https://issues.apache.org/jira/browse/GEODE-557 > Project: Geode > Issue Type: Bug > Components: offheap >Reporter: Hitesh Khamesra >Assignee: Sai Boorlagadda > Labels: ci > > dunit.RMIException: While invoking > com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest$44.call > in VM 1 running on Host cc1-co.gemstone.com with 4 VMs > at dunit.VM.invoke(VM.java:369) > at dunit.VM.invoke(VM.java:312) > at dunit.VM.invoke(VM.java:280) > at > com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest.startCacheServer(MemoryThresholdsOffHeapDUnitTest.java:1617) > at > com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest.doDistributedRegionRemotePutRejection(MemoryThresholdsOffHeapDUnitTest.java:446) > at > com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest.testDistributedRegionRemotePutRejectionCacheClose(MemoryThresholdsOffHeapDUnitTest.java:402) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) > at >
