[jira] [Commented] (GEODE-5194) Relax Gfsh version checking on connect, allow connecting to different patch versions
[
https://issues.apache.org/jira/browse/GEODE-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470409#comment-16470409
]
ASF subversion and git services commented on GEODE-5194:
Commit 5367fa520b4542b1f681dd6220e7625b68a82607 in geode's branch
refs/heads/develop from [~khowe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5367fa5 ]
GEODE-5194: Relax Gfsh connection version check to exclude patch version (#1942)
> Relax Gfsh version checking on connect, allow connecting to different patch
> versions
>
>
> Key: GEODE-5194
> URL: https://issues.apache.org/jira/browse/GEODE-5194
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently Gfsh, {{connect}} command will only connect to locator with the
> same exact version. Patch versions should not add or change functionality of
> commands, so for Gfsh version {{x.y.z}} connection to locator with same major
> and minor, {{x.y}}, version with a different patch, {{.z}}, should be allowed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5199) Unable to deploy Scala JARs
[
https://issues.apache.org/jira/browse/GEODE-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5199:
--
Labels: pull-request-available (was: )
> Unable to deploy Scala JARs
> ---
>
> Key: GEODE-5199
> URL: https://issues.apache.org/jira/browse/GEODE-5199
> Project: Geode
> Issue Type: Bug
>Reporter: Bradford D. Boyle
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> Using the gfsh (Geode 1.6.0) command to deploy a JAR containing the Scala
> library results in the following error:
> {code:java}
> [error 2018/05/09 21:00:21.201 PDT server1
> tid=0x4f] Could not deploy JAR file java.lang.IllegalArgumentException: A
> class and its auxiliary class have different superclasses: class extends
> scala.runtime.AbstractFunction1 scala.collection.convert.Wrappers$JPropertiesWrapper> implements
> scala.Serializable ; class extends
> scala.collection.mutable.AbstractMap
> implements scala.Product, scala.Serializable
> java.lang.RuntimeException: java.lang.IllegalArgumentException: A class and
> its auxiliary class have different superclasses: class extends
> scala.runtime.AbstractFunction1 scala.collection.convert.Wrappers$JPropertiesWrapper> implements
> scala.Serializable ; class extends
> scala.collection.mutable.AbstractMap
> implements scala.Product, scala.Serializable
> at
> io.github.lukehutch.fastclasspathscanner.FastClasspathScanner.scan(FastClasspathScanner.java:1513)
> at
> io.github.lukehutch.fastclasspathscanner.FastClasspathScanner.scan(FastClasspathScanner.java:1544)
> at
> io.github.lukehutch.fastclasspathscanner.FastClasspathScanner.scan(FastClasspathScanner.java:1567)
> at
> org.apache.geode.management.internal.deployment.FunctionScanner.findFunctionsInJar(FunctionScanner.java:38)
> at
> org.apache.geode.internal.DeployedJar.findFunctionsInThisJar(DeployedJar.java:338)
> at
> org.apache.geode.internal.DeployedJar.registerFunctions(DeployedJar.java:157)
> at
> org.apache.geode.internal.JarDeployer.registerNewVersions(JarDeployer.java:373)
> at org.apache.geode.internal.JarDeployer.deploy(JarDeployer.java:413)
> at
> org.apache.geode.management.internal.cli.functions.DeployFunction.execute(DeployFunction.java:79)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:193)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:378)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:444)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1121)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$9$1.run(ClusterDistributionManager.java:990)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: A class and its auxiliary
> class have different superclasses: class extends
> scala.runtime.AbstractFunction1 scala.collection.convert.Wrappers$JPropertiesWrapper> implements
> scala.Serializable ; class extends
> scala.collection.mutable.AbstractMap
> implements scala.Product, scala.Serializable
> at
> io.github.lukehutch.fastclasspathscanner.typesignature.ClassTypeSignature.merge(ClassTypeSignature.java:177)
> at
> io.github.lukehutch.fastclasspathscanner.scanner.ClassInfo.addTypeDescriptor(ClassInfo.java:691)
> at
> io.github.lukehutch.fastclasspathscanner.scanner.ClassInfoUnlinked.link(ClassInfoUnlinked.java:208)
> at
> io.github.lukehutch.fastclasspathscanner.scanner.Scanner.call(Scanner.java:443)
> at
> io.github.lukehutch.fastclasspathscanner.scanner.Scanner.call(Scanner.java:56)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ... 1 more
> {code}
> Here is a minimal reproduction
> {code:java}
> # download Scala 2.11.12
> curl -O
> [http://central.maven.org/maven2/org/scala-lang/scala-library/2.11.12/scala-library-2.11.12.jar]
> # or Scala 2.12.6
> curl -O
> [http://central.maven.org/maven2/org/scala-lang/scala-library/2.11.12/scala-library-2.11.12.jar]
> gfsh \
> -e "start locator --name=locator1" \
> -e "st
[jira] [Commented] (GEODE-5183) require toData/fromData methods for backward-compatibility to correspond to a known version
[ https://issues.apache.org/jira/browse/GEODE-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470606#comment-16470606 ] ASF subversion and git services commented on GEODE-5183: Commit 9f6eca31659560a9b34f952b5465ee844c8a66a3 in geode's branch refs/heads/develop from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9f6eca3 ] GEODE-5183 require toData/fromData methods to correspond to a known version Methods beginning with toData or fromData in DataSerializable classes must now correspond to a valid Version or AnalyzeSerializablesJUnitTest will reject them. I've renamed a few methods and adjusted sanctionedDataSerializables.txt to remove them (fromDataProblem, fromData662) This closes #1928 > require toData/fromData methods for backward-compatibility to correspond to a > known version > --- > > Key: GEODE-5183 > URL: https://issues.apache.org/jira/browse/GEODE-5183 > Project: Geode > Issue Type: Task > Components: serialization >Affects Versions: 1.7.0 >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Developers currently have no way of knowing if they correctly named their > toDataPre_ and fromDataPre_ methods. We need to at least have the > AnalyzeSerializables tests check to ensure that the toDataPre/fromDataPre > methods found in DataSerializables correspond to real Version instances. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5182) add 1.6.0 to geode-old-versions/build.gradle and roll version to 1.7.0
[ https://issues.apache.org/jira/browse/GEODE-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470683#comment-16470683 ] ASF subversion and git services commented on GEODE-5182: Commit ffe4b0299a7961a8a594cd44a574475872da2ada in geode's branch refs/heads/develop from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ffe4b02 ] GEODE-5182: add 1.6.0 as a backward-compatibility test version > add 1.6.0 to geode-old-versions/build.gradle and roll version to 1.7.0 > -- > > Key: GEODE-5182 > URL: https://issues.apache.org/jira/browse/GEODE-5182 > Project: Geode > Issue Type: Task >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2709) modify backward-compatibility support to work better with geode
[ https://issues.apache.org/jira/browse/GEODE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2709. - Resolution: Won't Fix Fix Version/s: 1.7.0 > modify backward-compatibility support to work better with geode > --- > > Key: GEODE-2709 > URL: https://issues.apache.org/jira/browse/GEODE-2709 > Project: Geode > Issue Type: Improvement > Components: serialization >Reporter: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Backward-compatibility support currently pays attention to a version's > Product name and its compareTo method pays attention to the major/minor/etc > numerals. This is an artifact of the GemFireXD effort at Pivotal a few years > ago and should be removed. The Product name is no longer needed at all and > compareTo should just compare the version ordinals. > All places that compare versions should be scrutinized to make sure this > change doesn't break anything. > All methods with names beginning with toDataPre_ or fromDataPre_ need to be > changed to remove the product name and the sanctionedDataSerializables.txt > database needs to be updated to have these new method names and fingerprints > (generated by the AnalyzeSerializablesJUnitTest). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5183) require toData/fromData methods for backward-compatibility to correspond to a known version
[ https://issues.apache.org/jira/browse/GEODE-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-5183. - Resolution: Fixed Fix Version/s: 1.7.0 > require toData/fromData methods for backward-compatibility to correspond to a > known version > --- > > Key: GEODE-5183 > URL: https://issues.apache.org/jira/browse/GEODE-5183 > Project: Geode > Issue Type: Task > Components: serialization >Affects Versions: 1.7.0 >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Developers currently have no way of knowing if they correctly named their > toDataPre_ and fromDataPre_ methods. We need to at least have the > AnalyzeSerializables tests check to ensure that the toDataPre/fromDataPre > methods found in DataSerializables correspond to real Version instances. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5182) add 1.6.0 to geode-old-versions/build.gradle and roll version to 1.7.0
[ https://issues.apache.org/jira/browse/GEODE-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-5182. - Resolution: Fixed Fix Version/s: 1.7.0 > add 1.6.0 to geode-old-versions/build.gradle and roll version to 1.7.0 > -- > > Key: GEODE-5182 > URL: https://issues.apache.org/jira/browse/GEODE-5182 > Project: Geode > Issue Type: Task >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4858) refactor internal commands to use the public ClusterConfigService
[ https://issues.apache.org/jira/browse/GEODE-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470689#comment-16470689 ] ASF subversion and git services commented on GEODE-4858: Commit 112cd71de3e0e498b7243022d34fad3083bef317 in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=112cd71 ] GEODE-4858 refactor jdbc describe & list commands to use result model (#1939) > refactor internal commands to use the public ClusterConfigService > - > > Key: GEODE-4858 > URL: https://issues.apache.org/jira/browse/GEODE-4858 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 12h > Remaining Estimate: 0h > > # except the ones that would need to access the internal cluster > configuration regions, like importClusterConfigCommand, > exportClusterConfigCommand or deploy > # use the configuration object as much as possible to pass parameters to the > functions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5166) NPE thrown from HARegionQueue.updateHAEventWrapper
[
https://issues.apache.org/jira/browse/GEODE-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey resolved GEODE-5166.
Resolution: Fixed
Fix Version/s: 1.7.0
Fixed on develop:
{noformat}
commit 1dfbffa71a377aa276729c80c35f0c25a2886b25
Author: Lynn Hughes-Godfrey
Date: Tue May 1 16:35:28 2018 -0700
GEODE-5166: NPE thrown while processing InitialImage of subscription region
* Fix NPE in updateHAEventWrapper
* Clean up code (renaming variables) in putEventInHARegion
* Removing old/commented out code
{noformat}
> NPE thrown from HARegionQueue.updateHAEventWrapper
> --
>
> Key: GEODE-5166
> URL: https://issues.apache.org/jira/browse/GEODE-5166
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> NPE thrown when processing the InitialImage for an HARegionQueue
> {noformat}
> ERROR util.TestException:
> /var/vcap/data/vad/eventValidation_FullListFailOver-0430-070117/bridgegemfire4_19378/system.log
> contains java.lang.NullPointerException
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.internal.cache.ha.HARegionQueue.updateHAEventWrapper(HARegionQueue.java:2128)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.internal.cache.HARegion.updateHAEventWrapper(HARegion.java:481)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.internal.cache.AbstractRegionMap.initialImagePut(AbstractRegionMap.java:825)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:977)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1307)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:209)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2786)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:193)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:186)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:378)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:444)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1121)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028'
> in
> org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:832)
> at Remote Member
> 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:
[jira] [Updated] (GEODE-2668) Add gfsh command to destroy gateway receiver
[
https://issues.apache.org/jira/browse/GEODE-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn updated GEODE-2668:
--
Fix Version/s: 1.7.0
> Add gfsh command to destroy gateway receiver
>
>
> Key: GEODE-2668
> URL: https://issues.apache.org/jira/browse/GEODE-2668
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Currently, there is a {{create gateway-receiver}} command, but no
> corresponding destroy command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-2668) Add gfsh command to destroy gateway receiver
[
https://issues.apache.org/jira/browse/GEODE-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-2668.
---
Resolution: Fixed
> Add gfsh command to destroy gateway receiver
>
>
> Key: GEODE-2668
> URL: https://issues.apache.org/jira/browse/GEODE-2668
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Currently, there is a {{create gateway-receiver}} command, but no
> corresponding destroy command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5184) Add tests for PersistentInitialImageAdvisor
[ https://issues.apache.org/jira/browse/GEODE-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470768#comment-16470768 ] ASF subversion and git services commented on GEODE-5184: Commit 3827332f19acc355621426880084de741972dcda in geode's branch refs/heads/develop from [~demery] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3827332 ] GEODE-5184 Add unit tests for PersistenceInitialImageAdvisor (#1934) > Add tests for PersistentInitialImageAdvisor > --- > > Key: GEODE-5184 > URL: https://issues.apache.org/jira/browse/GEODE-5184 > Project: Geode > Issue Type: Test > Components: persistence >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Minor > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > h2. Test Cases > *Condition*: replicates && disk image && at least one equal > *Result*: return advice with empty replicates (load from disk) > *Condition*: replicates && disk image && none equal > *Results*: > * clear equal members > * return advice with all replicates (attempt GII) > *Condition*: replicates && no disk image > *Results*: return advice with all replicates (attempt GII) > *Condition*: no replicates && non-persistent > *Result*: update membership view from non-persistent > *Condition*: no replicates && previous replicates > *Results*: > * clear previous advice > * fetch new advice from cache distribution advisor (which will have > replicates) > * react to new advice > *Condition*: no replicates && no previous replicates && members to wait for > *Result*: return advice from cache distribution advisor > *Additional test scenarios TBD*: > * no replicates && no previous replicates && members to wait for -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470856#comment-16470856 ] ASF subversion and git services commented on GEODE-4728: Commit 282aa3ee2eea090ae121eb62e302b74520dc42f1 in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=282aa3e ] GEODE-4728: Docs - Configuration (WIP) > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3845) As a user, I want to be able to do a distributed destroy action from a local region
[
https://issues.apache.org/jira/browse/GEODE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Addison updated GEODE-3845:
---
Summary: As a user, I want to be able to do a distributed destroy action
from a local region (was: local-destroy setting of eviction breaks the
consistency of the partition region)
> As a user, I want to be able to do a distributed destroy action from a local
> region
> ---
>
> Key: GEODE-3845
> URL: https://issues.apache.org/jira/browse/GEODE-3845
> Project: Geode
> Issue Type: New Feature
> Components: docs, eviction
>Reporter: Masaki Yamakawa
>Priority: Major
> Labels: geode-150
>
> I use entry-idle-time and eviction together in a partition region that holds
> one redundant copy.
> Details of setting are as follows:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
> {code}
> In this setting, the data held by the cache server is different. Then,
> inconsistent results are returned depending on the server to be connected.
> Eviction of the partition region can only select local-destroy or
> overflow-to-disk. On the other hand, it is written that the expire chapter of
> the document can not use local-destroy, local-invalidate in the partition
> region. Likewise, I think that data inconsistency will occur even with the
> settings like this time.
> Below is the test code:
> https://github.com/masaki-yamakawa/geode/blob/bug-partition-local-destroy/geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/BugExpireAndEvictionDUnitTest.java
> I think that it is necessary to add a check at the time of region creation or
> write it in the document.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4363) Add new distributed destroy action configuration
[ https://issues.apache.org/jira/browse/GEODE-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone updated GEODE-4363: -- Description: Currently eviction-action currently must be either 'local-destroy' or 'overflow-to-disk' ex: This story is to add the additional option "distributed-destroy" as an action setting for expiration-attributes. This will enable a local destroy action to be distributed across the cluster (currently this does not exist) Acceptance: can set this on region configuration via cache.xml, API or gfsh gfsh help and docs have been updated was: Should add action="distributed-destroy" eviction-action currently must be either 'local-destroy' or 'overflow-to-disk' Acceptance: can set this on region configuration via cache.xml, API or gfsh gfsh help and docs have been updated > Add new distributed destroy action configuration > > > Key: GEODE-4363 > URL: https://issues.apache.org/jira/browse/GEODE-4363 > Project: Geode > Issue Type: Sub-task >Reporter: Fred Krone >Priority: Major > > > Currently eviction-action currently must be either 'local-destroy' or > 'overflow-to-disk' > ex: > This story is to add the additional option "distributed-destroy" as an action > setting for expiration-attributes. > This will enable a local destroy action to be distributed across the cluster > (currently this does not exist) > > Acceptance: can set this on region configuration via cache.xml, API or gfsh > gfsh help and docs have been updated > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4363) Add new distributed destroy action configuration
[ https://issues.apache.org/jira/browse/GEODE-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone updated GEODE-4363: -- Description: Problem: currently eviction-action currently must be either 'local-destroy' or 'overflow-to-disk' ex: Solution: This story is to add the additional option "distributed-destroy" as an action setting for expiration-attributes. This will enable a local destroy action to be distributed across the cluster (currently this does not exist) Acceptance: can set this on region configuration via cache.xml, API or gfsh gfsh help and docs have been updated was: Currently eviction-action currently must be either 'local-destroy' or 'overflow-to-disk' ex: This story is to add the additional option "distributed-destroy" as an action setting for expiration-attributes. This will enable a local destroy action to be distributed across the cluster (currently this does not exist) Acceptance: can set this on region configuration via cache.xml, API or gfsh gfsh help and docs have been updated > Add new distributed destroy action configuration > > > Key: GEODE-4363 > URL: https://issues.apache.org/jira/browse/GEODE-4363 > Project: Geode > Issue Type: Sub-task >Reporter: Fred Krone >Priority: Major > > > Problem: currently eviction-action currently must be either 'local-destroy' > or 'overflow-to-disk' > ex: > Solution: This story is to add the additional option "distributed-destroy" as > an action setting for expiration-attributes. > This will enable a local destroy action to be distributed across the cluster > (currently this does not exist) > > Acceptance: can set this on region configuration via cache.xml, API or gfsh > gfsh help and docs have been updated > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4447) Write unit tests for AbstractRegionMap.basicPut
[ https://issues.apache.org/jira/browse/GEODE-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4447: - Labels: AbstractRegionMap (was: ) > Write unit tests for AbstractRegionMap.basicPut > --- > > Key: GEODE-4447 > URL: https://issues.apache.org/jira/browse/GEODE-4447 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Priority: Major > Labels: AbstractRegionMap > > Write unit tests for AbstractRegionMap.basicPut -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4574) Rename arguments of RegionMapDestroy.destroy
[ https://issues.apache.org/jira/browse/GEODE-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4574: - Labels: AbstractRegionMap (was: ) > Rename arguments of RegionMapDestroy.destroy > > > Key: GEODE-4574 > URL: https://issues.apache.org/jira/browse/GEODE-4574 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Priority: Trivial > Labels: AbstractRegionMap > > Rename arguments of RegionMapDestroy.destroy. These args were temporarily > renamed to facilitate refactoring. The args can be restored to the pre-*Arg > names. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4357) Cleanup AbstractRegionMap and its subclasses
[ https://issues.apache.org/jira/browse/GEODE-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4357: - Labels: AbstractRegionMap (was: ) > Cleanup AbstractRegionMap and its subclasses > > > Key: GEODE-4357 > URL: https://issues.apache.org/jira/browse/GEODE-4357 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Priority: Major > Labels: AbstractRegionMap > > This carries on with what we started in GEODE-4333. The initial focus is to > improve code coverage so that we can start to refactor AbstractRegionMap and > ultimately add new behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4445) Move all RegionMap classes to org.apache.geode.internal.cache.map package
[ https://issues.apache.org/jira/browse/GEODE-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4445: - Labels: AbstractRegionMap (was: ) > Move all RegionMap classes to org.apache.geode.internal.cache.map package > - > > Key: GEODE-4445 > URL: https://issues.apache.org/jira/browse/GEODE-4445 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Priority: Major > Labels: AbstractRegionMap > > Move all RegionMap classes to org.apache.geode.internal.cache.map package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4446) Extract many methods from BasicPut basicPut
[ https://issues.apache.org/jira/browse/GEODE-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4446: - Labels: AbstractRegionMap (was: ) > Extract many methods from BasicPut basicPut > --- > > Key: GEODE-4446 > URL: https://issues.apache.org/jira/browse/GEODE-4446 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Priority: Major > Labels: AbstractRegionMap > > Extract many methods from BasicPut basicPut. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4364) Extract destroy operation to its own class
[ https://issues.apache.org/jira/browse/GEODE-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4364: - Labels: AbstractRegionMap pull-request-available (was: pull-request-available) > Extract destroy operation to its own class > -- > > Key: GEODE-4364 > URL: https://issues.apache.org/jira/browse/GEODE-4364 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: AbstractRegionMap, pull-request-available > Fix For: 1.5.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Extract body of AbstractRegionMap.destroy method to new RegionMapDestroy > class in org.apache.geode.internal.cache.map package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4398) Replace use of AbstractRegionMap subclasses with mocks in RegionMapDestroyTest
[ https://issues.apache.org/jira/browse/GEODE-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4398: - Labels: AbstractRegionMap (was: ) > Replace use of AbstractRegionMap subclasses with mocks in RegionMapDestroyTest > -- > > Key: GEODE-4398 > URL: https://issues.apache.org/jira/browse/GEODE-4398 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Priority: Major > Labels: AbstractRegionMap > > Replace use of AbstractRegionMap subclasses with mocks in > RegionMapDestroyTest. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4444) Extract basicPut operation to its own class
[ https://issues.apache.org/jira/browse/GEODE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-: - Labels: AbstractRegionMap (was: ) > Extract basicPut operation to its own class > --- > > Key: GEODE- > URL: https://issues.apache.org/jira/browse/GEODE- > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Priority: Major > Labels: AbstractRegionMap > > Extract body of AbstractRegionMap.basicPut method to new BasicPut class in > org.apache.geode.internal.cache.map package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4397) Extract many methods from RegionMapDestroy destroy
[ https://issues.apache.org/jira/browse/GEODE-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4397: - Labels: AbstractRegionMap pull-request-available (was: pull-request-available) > Extract many methods from RegionMapDestroy destroy > -- > > Key: GEODE-4397 > URL: https://issues.apache.org/jira/browse/GEODE-4397 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: AbstractRegionMap, pull-request-available > Fix For: 1.5.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Extract many methods from RegionMapDestroy destroy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5143) rename ClusterConfigurationService
[ https://issues.apache.org/jira/browse/GEODE-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-5143: --- Component/s: (was: docs) > rename ClusterConfigurationService > -- > > Key: GEODE-5143 > URL: https://issues.apache.org/jira/browse/GEODE-5143 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The term ClusterConfigurationService is ambiguous. People have grand ideas > about what it should do which is way outside of the current scope of making a > public API for retrieving and persisting cluster configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5144) CI failure: org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > testReplicatedSerialPropagationWithFilter
[
https://issues.apache.org/jira/browse/GEODE-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaojian zhou reassigned GEODE-5144:
Assignee: xiaojian zhou
> CI failure:
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest
> > testReplicatedSerialPropagationWithFilter
>
>
> Key: GEODE-5144
> URL: https://issues.apache.org/jira/browse/GEODE-5144
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.6.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: xiaojian zhou
>Priority: Major
>
> This failure occurred during CI:
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/12
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest
> > testReplicatedSerialPropagationWithFilter FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 3199
> [error 2018/04/26 03:50:06.755 UTC 172.17.0.5(414):32774 shared ordered uid=20 port=60094> tid=309]
> Exception occurred in CacheListener
> java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@471694c6
> rejected from java.util.concurrent.ThreadPoolExecutor@c955b3b[Shutting down,
> pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1778]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:611)
> at
> org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91)
> at
> org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:151)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8468)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:6969)
> at
> org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6778)
> at
> org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2381)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:170)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6717)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:409)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:238)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:149)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1093)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6504)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6478)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:56)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6430)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1599)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1279)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2186)
> at
> org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:964)
> at
> org.apache.geode.internal.cache.wan.serial.BatchDestroyOperation$DestroyMessage.operateOnRegion(BatchDestroyOperation.java:120)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1191)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1091)
> at
> org.a
[jira] [Updated] (GEODE-5144) CI failure: org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > testReplicatedSerialPropagationWithFilter
[
https://issues.apache.org/jira/browse/GEODE-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5144:
--
Labels: pull-request-available (was: )
> CI failure:
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest
> > testReplicatedSerialPropagationWithFilter
>
>
> Key: GEODE-5144
> URL: https://issues.apache.org/jira/browse/GEODE-5144
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.6.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
>
> This failure occurred during CI:
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/12
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest
> > testReplicatedSerialPropagationWithFilter FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 3199
> [error 2018/04/26 03:50:06.755 UTC 172.17.0.5(414):32774 shared ordered uid=20 port=60094> tid=309]
> Exception occurred in CacheListener
> java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@471694c6
> rejected from java.util.concurrent.ThreadPoolExecutor@c955b3b[Shutting down,
> pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1778]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:611)
> at
> org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91)
> at
> org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:151)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8468)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:6969)
> at
> org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6778)
> at
> org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2381)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:170)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6717)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:409)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:238)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:149)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1093)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6504)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6478)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:56)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6430)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1599)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1279)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2186)
> at
> org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:964)
> at
> org.apache.geode.internal.cache.wan.serial.BatchDestroyOperation$DestroyMessage.operateOnRegion(BatchDestroyOperation.java:120)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1191)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process
[jira] [Commented] (GEODE-5144) CI failure: org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > testReplicatedSerialPropagationWithFilter
[
https://issues.apache.org/jira/browse/GEODE-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471284#comment-16471284
]
ASF subversion and git services commented on GEODE-5144:
Commit 5f538fdf517fa8c01e2c5a755ac0a4db0b539e1a in geode's branch
refs/heads/feature/GEODE-5144 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5f538fd ]
GEODE-5144: remove the test only method
> CI failure:
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest
> > testReplicatedSerialPropagationWithFilter
>
>
> Key: GEODE-5144
> URL: https://issues.apache.org/jira/browse/GEODE-5144
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.6.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This failure occurred during CI:
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/12
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest
> > testReplicatedSerialPropagationWithFilter FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 3199
> [error 2018/04/26 03:50:06.755 UTC 172.17.0.5(414):32774 shared ordered uid=20 port=60094> tid=309]
> Exception occurred in CacheListener
> java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@471694c6
> rejected from java.util.concurrent.ThreadPoolExecutor@c955b3b[Shutting down,
> pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1778]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:611)
> at
> org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91)
> at
> org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:151)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8468)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:6969)
> at
> org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6778)
> at
> org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2381)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:170)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6717)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:409)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:238)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:149)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1093)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6504)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6478)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:56)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6430)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1599)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1279)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2186)
> at
> org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:964)
> at
> org.apache.geode.internal.cache.wan.serial.BatchDestroyOper
[jira] [Commented] (GEODE-5144) CI failure: org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > testReplicatedSerialPropagationWithFilter
[
https://issues.apache.org/jira/browse/GEODE-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471285#comment-16471285
]
ASF subversion and git services commented on GEODE-5144:
Commit aa299bd34641bb8415cca21d29e121bee3ce1b9d in geode's branch
refs/heads/feature/GEODE-5144 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=aa299bd ]
GEODE-5144: The test should wait for secondary queue to drain
remove the test only method
> CI failure:
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest
> > testReplicatedSerialPropagationWithFilter
>
>
> Key: GEODE-5144
> URL: https://issues.apache.org/jira/browse/GEODE-5144
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.6.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This failure occurred during CI:
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/12
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest
> > testReplicatedSerialPropagationWithFilter FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 3199
> [error 2018/04/26 03:50:06.755 UTC 172.17.0.5(414):32774 shared ordered uid=20 port=60094> tid=309]
> Exception occurred in CacheListener
> java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@471694c6
> rejected from java.util.concurrent.ThreadPoolExecutor@c955b3b[Shutting down,
> pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1778]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:611)
> at
> org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91)
> at
> org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:151)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8468)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:6969)
> at
> org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6778)
> at
> org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2381)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:170)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6717)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:409)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:238)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:149)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1093)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6504)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6478)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:56)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6430)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1599)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1279)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2186)
> at
> org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:964)
> at
[jira] [Created] (GEODE-5200) Correct docs for use-cluster-configuration property
Karen Smoler Miller created GEODE-5200: -- Summary: Correct docs for use-cluster-configuration property Key: GEODE-5200 URL: https://issues.apache.org/jira/browse/GEODE-5200 Project: Geode Issue Type: Bug Components: docs Reporter: Karen Smoler Miller In the section titled gemfire.properties and gfsecurity.properties (Geode Properties), it says that the "use-cluster-configuration" property is only applicable for data members (non-client and non-locator) in "Definition" column. That does not match with what is in the 3rd column, which says which components are affected. Instead of "L," the column should say "S." File affected is reference/topics/gemfire_properties.html This is a 1-character change to fix the docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5187) clients can miss events when servers recycled, possibly due to null eventId in ClientUpdateMessageImpl
[ https://issues.apache.org/jira/browse/GEODE-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471317#comment-16471317 ] ASF subversion and git services commented on GEODE-5187: Commit 39965b198b2d71f3e157cebf46c54d2d5aecac0c in geode's branch refs/heads/feature/GEODE-5187 from [~lhughesgodfrey] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=39965b1 ] GEODE-5187: clients can miss events when servers recycled * When draining events from the giiQueue, the msg field of HAEventWrapper may be null. Update the HAEventWrapper to point to the message in the HAContainer vs. calling putEventInHARegion with the original HAContainer message (a ClientUpdateMessageImpl). This is necessary as the ClientUpdateMessageImpl does not have the eventId (this is not serialized/deserialized in toData/fromData). The HAEventWrapper is required on the remote side to reconstruct the event. * Updated log messages to include the HARegionQueue.regionName * Added corresponding IntegrationTest > clients can miss events when servers recycled, possibly due to null eventId > in ClientUpdateMessageImpl > -- > > Key: GEODE-5187 > URL: https://issues.apache.org/jira/browse/GEODE-5187 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > > HARegionQueues may have an issue where messages are lost due to the eventId > (threadId and sequenceId) being null ... which prevents them from being > dispatched to the client. > This may be due to the ClientUpdateMessageImpl no longer including the > eventId when serialized over the wire between servers. Now the receiving > side must use eventId from the HAEventWrapper to re-populate this field in > the ClientUpdateMessage. > If the null eventId is detected by HARegionQueue.putGIIDataInRegion, the > corresponding event is silently dropped. This occurs when processing the > InitialImage of the HARegionQueue from another server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5173) Transactional get from a client on a REPLICATE_HEAP_LRU region throws NotSerializableException
[
https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471329#comment-16471329
]
ASF subversion and git services commented on GEODE-5173:
Commit 5f3cb338d510e6a8cdd2db5260500d3fdec1 in geode's branch
refs/heads/feature/GEODE-5173-1 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5f3cb33 ]
Revert "Revert "GEODE-5173: Transaction will fault in value from disk if value
is Tok… (#1925)""
This reverts commit eb6055e9db64d008cdee0c0d96e8aed90ccd1faf.
> Transactional get from a client on a REPLICATE_HEAP_LRU region throws
> NotSerializableException
> --
>
> Key: GEODE-5173
> URL: https://issues.apache.org/jira/browse/GEODE-5173
> Project: Geode
> Issue Type: Bug
> Components: persistence, transactions
>Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0, 1.6.0
>Reporter: Dan Smith
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Doing a get from a client within a transaction on a region with persistence
> and overflow results in the below exception.
> It looks like this issue has to do with some code returning a
> Token.NOT_AVAILABLE rather than reading the value from disk if the get is
> performed within a transaction. Without using transactions, this same use
> case works:
>
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote
> server on 10.1.10.126(15995:loner):34188:40be7322:
> org.apache.geode.SerializationException: failed serializing object
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:384)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:231)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:140)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
> at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
> at
> org.apache.geode.internal.cache.tx.ClientTXRegionStub.findObject(ClientTXRegionStub.java:72)
> at
> org.apache.geode.internal.cache.TXStateStub.findObject(TXStateStub.java:472)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.findObject(TXStateProxyImpl.java:536)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1400)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1334)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1319)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:408)
> at
> org.apache.geode.internal.cache.ClientPersistentTransactionDUnitTest.lambda$test$2c6907a2$1(ClientPersistentTransactionDUnitTest.java:75)
> 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:498)
> at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> at
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> 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:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.ja
[jira] [Commented] (GEODE-5011) Refactor Commands to use *ResultModel
[ https://issues.apache.org/jira/browse/GEODE-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471500#comment-16471500 ] ASF subversion and git services commented on GEODE-5011: Commit f1c6b560442f2f23aa9240b3550d9d664e094c7c in geode's branch refs/heads/develop from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f1c6b56 ] GEODE-5011: Convert 'Data' commands to ResultModel (#1945) > Refactor Commands to use *ResultModel > - > > Key: GEODE-5011 > URL: https://issues.apache.org/jira/browse/GEODE-5011 > Project: Geode > Issue Type: Sub-task > Components: gfsh >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
