[jira] [Commented] (GEODE-4881) handle concurrent lucene indexing (after region created) with rebalance
[
https://issues.apache.org/jira/browse/GEODE-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405660#comment-16405660
]
ASF subversion and git services commented on GEODE-4881:
Commit 0aef84de2d35dd93e0b4cd1e9bad044df9ed74a2 in geode's branch
refs/heads/feature/GEODE-4881 from [~lhughesgodfrey]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0aef84d ]
GEODE-4881: Support lucene reindexing (of existing data) with rebalance
* LuceneServiceImpl changes to support AEQ addition to existing region (after
index initialized)
* Testing with and without redundancy
> handle concurrent lucene indexing (after region created) with rebalance
> ---
>
> Key: GEODE-4881
> URL: https://issues.apache.org/jira/browse/GEODE-4881
> Project: Geode
> Issue Type: New Feature
> Components: lucene
>Reporter: Shelley Lynn Hughes-Godfrey
>Priority: Major
>
> {noformat}
> While adding a Lucene index to a region with data, if a rebalance is
> triggered during re-indexing, the index should complete successfully and
> match the region data.
> If I add a Lucene index while a rebalance is in progress, the index should
> successfully complete and match the region data. (*)
> (*) Note: It may be acceptable to detect a rebalance in progress before
> starting and wait for it to finish before adding the Lucene index.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4893) import cluster configuration command shuts down the existing servers
[ https://issues.apache.org/jira/browse/GEODE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-4893: --- Affects Version/s: 1.4.0 > import cluster configuration command shuts down the existing servers > > > Key: GEODE-4893 > URL: https://issues.apache.org/jira/browse/GEODE-4893 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Affects Versions: 1.4.0 >Reporter: Jinmei Liao >Priority: Major > > `import cluster-configuration --zip-file-name=...` in a cluster which has > locator and servers (Server has no application regions defined yet). the > server is shutdown without any message in the logs as to why the server was > shutdown. Gfsh says import was successful. > On manual restart of the server I can see that the config was actually > imported successfully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4891) Update metrics script to account for API change
[ https://issues.apache.org/jira/browse/GEODE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4891: -- Labels: pull-request-available (was: ) > Update metrics script to account for API change > --- > > Key: GEODE-4891 > URL: https://issues.apache.org/jira/browse/GEODE-4891 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > Concourse changed their API, fix our metrics script to account for it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4891) Update metrics script to account for API change
[ https://issues.apache.org/jira/browse/GEODE-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405295#comment-16405295 ] ASF subversion and git services commented on GEODE-4891: Commit 8444bd072e0c379baa9ce2ef7b40d7b0ada61ba5 in geode's branch refs/heads/develop from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8444bd0 ] [GEODE-4891] Fixes for concourse API changes. * Generate concourse job URL because the url field was removed in Concourse 3.9.2. > Update metrics script to account for API change > --- > > Key: GEODE-4891 > URL: https://issues.apache.org/jira/browse/GEODE-4891 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Concourse changed their API, fix our metrics script to account for it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database
[ https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405328#comment-16405328 ] ASF subversion and git services commented on GEODE-4833: Commit b4ad610f1bd20b7b87e9679b4637893e2bf3c5b8 in geode's branch refs/heads/develop from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b4ad610 ] GEODE-4833: JdbcWriter and JdbcAsyncWriter may fail to write null fields to database (#1636) Null values are now supported. Meta-data read from the database is now used to determine the column type and used to call setNull. * Renamed TableKeyColumnManager to TableMetaDataManager * registerPdxMetaData will now throw an exception if the instance is not serialized with PDX > JdbcWriter and JdbcAsyncWriter may fail to write null fields to database > > > Key: GEODE-4833 > URL: https://issues.apache.org/jira/browse/GEODE-4833 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.4.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Both JdbcWriter and JdbcAsyncWriter end up calling the JDBC method > PreparedStatement.setObject with a value of "null" if the pdx field contains > "null". > This will work with jdbc drivers that support sending "non-typed Null" to the > backend database. > But some drivers do not support this and these puts will fail with a > SQLException. > For portability the jdbc connector should be changed to not pass "null" to > setObject without a type. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4888) Document security-udp-dhalgo property
[ https://issues.apache.org/jira/browse/GEODE-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4888: -- Labels: pull-request-available (was: ) > Document security-udp-dhalgo property > - > > Key: GEODE-4888 > URL: https://issues.apache.org/jira/browse/GEODE-4888 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > > Document the security-udp-dhalgo property. It is a string that defines the > name of a valid symmetric key cipher supported by the JDK. When defined, the > cipher will be used for server to server UDP communications. > Also update the ssl-enabled-components property definition to recommend to > users that when ssl-enabled-components is defined, they should also set > security-udp-dhalgo to secure cluster communications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4892) CI failure: geode-wan distributedTest hung in org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended
[ https://issues.apache.org/jira/browse/GEODE-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-4892: --- Affects Version/s: 1.6.0 > CI failure: geode-wan distributedTest hung in > org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest > testGatewaySenderStatus_OnMember Ended > --- > > Key: GEODE-4892 > URL: https://issues.apache.org/jira/browse/GEODE-4892 > Project: Geode > Issue Type: Bug > Components: distributed lock service, gfsh >Affects Versions: 1.6.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > geode-wan distributed tests hung after 8 hours (usually takes 5-6 hours) > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/207 > The progress files show this DistributedTest run starting ~4 am ... but it > also shows this test completing at 9:05 ... which is only 5 hours. Are we > somehow stuck in cache close for 3 hours before the hang is declared while > trying to shut down the DUnit VM. > dunit-hangs.txt > ``` > Started @ 2018-03-17 03:57:50.567 + > Ended @ 2018-03-17 03:59:28.268 + > Started @ 2018-03-17 04:00:05.872 + > Ended @ 2018-03-17 04:52:41.879 + > Started @ 2018-03-17 04:53:00.358 + > Ended @ 2018-03-17 04:55:07.622 + > Started @ 2018-03-17 04:55:33.550 + > Ended @ 2018-03-17 07:34:11.639 + > Started @ 2018-03-17 07:34:51.022 + > Ended @ 2018-03-17 08:08:34.849 + > Started @ 2018-03-17 08:09:33.853 + > Ended @ 2018-03-17 08:31:43.646 + > Started @ 2018-03-17 08:31:54.175 + > Ended @ 2018-03-17 08:32:02.523 + > Started @ 2018-03-17 08:32:13.946 + > Ended @ 2018-03-17 08:32:34.626 + > Started @ 2018-03-17 08:33:20.100 + > 2018-03-17 08:56:15.914 + > org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest > testGatewaySenderStatus_OnMember > Ended @ 2018-03-17 09:05:29.197 + > ``` > Last distributedTest running: > ``` > Started @ 2018-03-17 08:33:20.100 + > 2018-03-17 08:56:15.914 + > org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest > testGatewaySenderStatus_OnMember > Ended @ 2018-03-17 09:05:29.197 + > ``` > Stack dumps are taken at 5-10 second intervals and they all look the same ... > so it looks like 433 is stuck in waiting during cache close => > distributedLockServiceDestroys waiting for replies from 493 for ElderInit. > 493 is in ClusterDistributionManager.elderChangeWait(). > * Dumping stack for process 433: > 2018-03-17 10:55:59 > ``` > "RMI TCP Connection(1)-172.17.0.3" #30 daemon prio=5 os_prio=0 > tid=0x7f9760001800 nid=0x1ec waiting on condition [0x7f975bffb000] >java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0xe08dd870> (a > java.util.concurrent.CountDownLatch$Sync) > at > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) > at > org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) > at > org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853) > at > org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72) > at > org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.getElderStateWithTryLock(ClusterDistributionManager.java:3359) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.getElderState(ClusterDistributionManager.java:3309) > at > org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:238) > at >
[jira] [Created] (GEODE-4891) Update metrics script to account for API change
Sean Goller created GEODE-4891: -- Summary: Update metrics script to account for API change Key: GEODE-4891 URL: https://issues.apache.org/jira/browse/GEODE-4891 Project: Geode Issue Type: Bug Components: ci Reporter: Sean Goller Concourse changed their API, fix our metrics script to account for it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4451) When a gateway sender is created using gfsh and fails to connect due to AuthenticationFailedException, it is left in an inconsistent state
[
https://issues.apache.org/jira/browse/GEODE-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405346#comment-16405346
]
ASF subversion and git services commented on GEODE-4451:
Commit 841ef33eaa7c63fd2d3b05251195e2df0c1f0122 in geode's branch
refs/heads/feature/GEODE-4451-2 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=841ef33 ]
GEODE-4451: Prevented sender from being created when members aren't all current
version
> When a gateway sender is created using gfsh and fails to connect due to
> AuthenticationFailedException, it is left in an inconsistent state
> --
>
> Key: GEODE-4451
> URL: https://issues.apache.org/jira/browse/GEODE-4451
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If I attempt to create a gateway sender with invalid credentials using gfsh,
> it fails like:
> {noformat}
> (2) Executing - create gateway-sender --remote-distributed-system-id=1
> --id=ny --dispatcher-threads=1 --parallel=true
> Member | Status
> -- |
> --
> ln-1 | ERROR: Could not start a gateway sender ny because of exception Could
> not start a gateway sender 84 because of exception
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials.
> {noformat}
> The 84 should be the gateway sender id; instead its the thread id (from
> \{{ConcurrentParallelGatewaySenderEventProcessor.waitForRunningStatus}}.
> In the server log, I see 5 AuthenticationFailedException stacks like (one per
> dispatcher-thread):
> {noformat}
> [severe 2018/01/31 16:13:12.638 PST ln-1 GatewaySender_ny_0> tid=0x55] Message dispatch failed due to unexpected
> exception..
> org.apache.geode.internal.cache.wan.GatewaySenderException:
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials., caused by
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials.
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:432)
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.(GatewaySenderEventRemoteDispatcher.java:75)
> at
> org.apache.geode.internal.cache.wan.parallel.RemoteParallelGatewaySenderEventProcessor.initializeEventDispatcher(RemoteParallelGatewaySenderEventProcessor.java:74)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.setRunningStatus(AbstractGatewaySenderEventProcessor.java:1078)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1050)
> Caused by: org.apache.geode.security.AuthenticationFailedException:
> Authentication error. Please check your credentials.
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.readMessage(HandShake.java:1397)
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.handshakeWithServer(HandShake.java:1253)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:118)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:136)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:259)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:206)
> at
> org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:902)
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:388)
> ... 4 more
> {noformat}
> A thread dump shows the Event Processor threads are gone, but 5
> BatchRemovalThreads like this exist:
> {noformat}
> "BatchRemovalThread" #96 daemon prio=10 os_prio=31 tid=0x7fc1dd009000
> nid=0xcb03 waiting on condition [0x7e245000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0007a04043c8> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at
[jira] [Updated] (GEODE-4892) CI failure: geode-wan distributedTest hung in org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended
[
https://issues.apache.org/jira/browse/GEODE-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-4892:
---
Description:
geode-wan distributed tests hung after 8 hours (usually takes 5-6 hours)
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/207
The progress files show this DistributedTest run starting ~4 am ... but it also
shows this test completing at 9:05 ... which is only 5 hours. Are we somehow
stuck in cache close for 3 hours before the hang is declared while trying to
shut down the DUnit VM.
dunit-hangs.txt
{noformat}
Started @ 2018-03-17 03:57:50.567 +
Ended @ 2018-03-17 03:59:28.268 +
Started @ 2018-03-17 04:00:05.872 +
Ended @ 2018-03-17 04:52:41.879 +
Started @ 2018-03-17 04:53:00.358 +
Ended @ 2018-03-17 04:55:07.622 +
Started @ 2018-03-17 04:55:33.550 +
Ended @ 2018-03-17 07:34:11.639 +
Started @ 2018-03-17 07:34:51.022 +
Ended @ 2018-03-17 08:08:34.849 +
Started @ 2018-03-17 08:09:33.853 +
Ended @ 2018-03-17 08:31:43.646 +
Started @ 2018-03-17 08:31:54.175 +
Ended @ 2018-03-17 08:32:02.523 +
Started @ 2018-03-17 08:32:13.946 +
Ended @ 2018-03-17 08:32:34.626 +
Started @ 2018-03-17 08:33:20.100 +
2018-03-17 08:56:15.914 +
org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest
testGatewaySenderStatus_OnMember
Ended @ 2018-03-17 09:05:29.197 +
{noformat}
Last distributedTest running:
{noformat}
Started @ 2018-03-17 08:33:20.100 +
2018-03-17 08:56:15.914 +
org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest
testGatewaySenderStatus_OnMember
Ended @ 2018-03-17 09:05:29.197 +
{noformat}
Stack dumps are taken at 5-10 second intervals and they all look the same ...
so it looks like 433 is stuck in waiting during cache close =>
distributedLockServiceDestroys waiting for replies from 493 for ElderInit. 493
is in ClusterDistributionManager.elderChangeWait().
Dumping stack for process 433:
2018-03-17 10:55:59
{noformat}
"RMI TCP Connection(1)-172.17.0.3" #30 daemon prio=5 os_prio=0
tid=0x7f9760001800 nid=0x1ec waiting on condition [0x7f975bffb000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xe08dd870> (a
java.util.concurrent.CountDownLatch$Sync)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
at
org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64)
at
org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853)
at
org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72)
at
org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.getElderStateWithTryLock(ClusterDistributionManager.java:3359)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.getElderState(ClusterDistributionManager.java:3309)
at
org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:238)
at
org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:347)
at
org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:327)
at
org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:318)
at
org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:872)
at
org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1227)
- locked <0xe09a8768> (a
org.apache.geode.distributed.internal.locks.DLockGrantor)
at
org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:646)
at
[jira] [Commented] (GEODE-4878) Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405224#comment-16405224 ] ASF subversion and git services commented on GEODE-4878: Commit ce0c965141fcb2705f4c95b51d29d22da07090cd in geode's branch refs/heads/develop from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ce0c965 ] GEODE-4878: Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest (#1633) > Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest > - > > Key: GEODE-4878 > URL: https://issues.apache.org/jira/browse/GEODE-4878 > Project: Geode > Issue Type: Test > Components: gfsh >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4892) CI failure: geode-wan distributedTest hung in org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended
Shelley Lynn Hughes-Godfrey created GEODE-4892: -- Summary: CI failure: geode-wan distributedTest hung in org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended Key: GEODE-4892 URL: https://issues.apache.org/jira/browse/GEODE-4892 Project: Geode Issue Type: Bug Components: distributed lock service, gfsh Reporter: Shelley Lynn Hughes-Godfrey geode-wan distributed tests hung after 8 hours (usually takes 5-6 hours) https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/207 The progress files show this DistributedTest run starting ~4 am ... but it also shows this test completing at 9:05 ... which is only 5 hours. Are we somehow stuck in cache close for 3 hours before the hang is declared while trying to shut down the DUnit VM. dunit-hangs.txt ``` Started @ 2018-03-17 03:57:50.567 + Ended @ 2018-03-17 03:59:28.268 + Started @ 2018-03-17 04:00:05.872 + Ended @ 2018-03-17 04:52:41.879 + Started @ 2018-03-17 04:53:00.358 + Ended @ 2018-03-17 04:55:07.622 + Started @ 2018-03-17 04:55:33.550 + Ended @ 2018-03-17 07:34:11.639 + Started @ 2018-03-17 07:34:51.022 + Ended @ 2018-03-17 08:08:34.849 + Started @ 2018-03-17 08:09:33.853 + Ended @ 2018-03-17 08:31:43.646 + Started @ 2018-03-17 08:31:54.175 + Ended @ 2018-03-17 08:32:02.523 + Started @ 2018-03-17 08:32:13.946 + Ended @ 2018-03-17 08:32:34.626 + Started @ 2018-03-17 08:33:20.100 + 2018-03-17 08:56:15.914 + org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended @ 2018-03-17 09:05:29.197 + ``` Last distributedTest running: ``` Started @ 2018-03-17 08:33:20.100 + 2018-03-17 08:56:15.914 + org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended @ 2018-03-17 09:05:29.197 + ``` Stack dumps are taken at 5-10 second intervals and they all look the same ... so it looks like 433 is stuck in waiting during cache close => distributedLockServiceDestroys waiting for replies from 493 for ElderInit. 493 is in ClusterDistributionManager.elderChangeWait(). * Dumping stack for process 433: 2018-03-17 10:55:59 ``` "RMI TCP Connection(1)-172.17.0.3" #30 daemon prio=5 os_prio=0 tid=0x7f9760001800 nid=0x1ec waiting on condition [0x7f975bffb000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xe08dd870> (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) at org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) at org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853) at org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72) at org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56) at org.apache.geode.distributed.internal.ClusterDistributionManager.getElderStateWithTryLock(ClusterDistributionManager.java:3359) at org.apache.geode.distributed.internal.ClusterDistributionManager.getElderState(ClusterDistributionManager.java:3309) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:238) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:347) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:327) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:318) at org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:872) at org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1227)
[jira] [Resolved] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database
[ https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-4833. - Resolution: Fixed Fix Version/s: 1.6.0 > JdbcWriter and JdbcAsyncWriter may fail to write null fields to database > > > Key: GEODE-4833 > URL: https://issues.apache.org/jira/browse/GEODE-4833 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.4.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Both JdbcWriter and JdbcAsyncWriter end up calling the JDBC method > PreparedStatement.setObject with a value of "null" if the pdx field contains > "null". > This will work with jdbc drivers that support sending "non-typed Null" to the > backend database. > But some drivers do not support this and these puts will fail with a > SQLException. > For portability the jdbc connector should be changed to not pass "null" to > setObject without a type. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4885) DistributedRestoreSystemPropertiesTest is failing
[
https://issues.apache.org/jira/browse/GEODE-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405355#comment-16405355
]
Kirk Lund commented on GEODE-4885:
--
I changed DUnitLauncher.launchIfNeeded() to throw an Error and this only shows
up for ShowLogCommandDUnitTest. The others show up in the JUnit report for
"test" with zero tests, zero failures, zero ignored. The customer Runners for
parameters seem to forcing the gradle junit plugin to instantiate the class in
order to examine the Categories but only for the ones that have the custom
runners.
> DistributedRestoreSystemPropertiesTest is failing
> -
>
> Key: GEODE-4885
> URL: https://issues.apache.org/jira/browse/GEODE-4885
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This test is supposedly checking for any {{DUnitTest}} that inadvertently
> runs under the {{test}} gradle task or, more specifically, is categorized as
> a {{UnitTest}}.
> Unfortunately, due to the way that Junit determines what category a test is
> in (by creating an instance of the class), it will also invoke any static
> declarations. It also triggers parameterized values. The result is that some
> {{DistributedTests}} actually end up launching DUnit VMs even though the
> actual tests don't run. Depending on test ordering this can lead to
> {{DistributedRestoreSystemPropertiesTest}} failing intermittently.
> By examining the test report, it appears that the following DUnit tests are
> triggering this problem:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowLogCommandDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest
> org.apache.geode.security.ClientAuthenticationPart2DUnitTest
> org.apache.geode.cache.lucene.LuceneCommandsSecurityDUnitTest
> org.apache.geode.management.internal.configuration.ClusterConfigurationIndexWithFromClauseDUnitTest
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTest
> org.apache.geode.security.ClientAuthenticationDUnitTest
> org.apache.geode.security.ClientAuthorizationCQDUnitTest
> org.apache.geode.internal.cache.TxCommitMessageBackwardCompatibilityDUnitTest
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4873) Javadocs on ProtobufUtilities are generating a warning
[
https://issues.apache.org/jira/browse/GEODE-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dodge reassigned GEODE-4873:
Assignee: Michael Dodge
> Javadocs on ProtobufUtilities are generating a warning
> --
>
> Key: GEODE-4873
> URL: https://issues.apache.org/jira/browse/GEODE-4873
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Kirk Lund
>Assignee: Michael Dodge
>Priority: Major
>
> Javadocs on ProtobufUtilities are generating a warning:
> {noformat}
> /Users/klund/dev/gemfire_CLEAN/open/geode-protobuf/src/main/java/org/apache/geode/internal/protocol/protobuf/v1/utilities/ProtobufUtilities.java:33:
> warning - Tag @link: reference not found: ProtobufRequestUtilities
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4893) import cluster configuration command shuts down the existing servers
Jinmei Liao created GEODE-4893: -- Summary: import cluster configuration command shuts down the existing servers Key: GEODE-4893 URL: https://issues.apache.org/jira/browse/GEODE-4893 Project: Geode Issue Type: Bug Components: configuration, gfsh Reporter: Jinmei Liao `import cluster-configuration --zip-file-name=...` in a cluster which has locator and servers (Server has no application regions defined yet). the server is shutdown without any message in the logs as to why the server was shutdown. Gfsh says import was successful. On manual restart of the server I can see that the config was actually imported successfully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-4875) JdbcLoader will not always find an existing pdx field type if it is not all lower case
[ https://issues.apache.org/jira/browse/GEODE-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider closed GEODE-4875. --- > JdbcLoader will not always find an existing pdx field type if it is not all > lower case > -- > > Key: GEODE-4875 > URL: https://issues.apache.org/jira/browse/GEODE-4875 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.6.0 >Reporter: Darrel Schneider >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > When doing a read using the JdbcLoader, if the region mapping has a > pdx-class-name and does not have a pdx-field to column-name mapping, then it > will only find the existing pdx field type if the field name is all lower > case. > You will see a JdbcConnectorException with this message when you hit this bug: > "Could not find PdxType for field " + fieldName + ". Add class " + > pdxClassName + " with " + fieldName + " to pdx registry." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4892) CI failure: geode-wan distributedTest hung in org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended
[
https://issues.apache.org/jira/browse/GEODE-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-4892:
---
Description:
geode-wan distributed tests hung after 8 hours (usually takes 5-6 hours)
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/207
The progress files show this DistributedTest run starting ~4 am ... but it also
shows this test completing at 9:05 ... which is only 5 hours. Are we somehow
stuck in cache close for 3 hours before the hang is declared while trying to
shut down the DUnit VM.
dunit-hangs.txt
{noformat}
Started @ 2018-03-17 03:57:50.567 +
Ended @ 2018-03-17 03:59:28.268 +
Started @ 2018-03-17 04:00:05.872 +
Ended @ 2018-03-17 04:52:41.879 +
Started @ 2018-03-17 04:53:00.358 +
Ended @ 2018-03-17 04:55:07.622 +
Started @ 2018-03-17 04:55:33.550 +
Ended @ 2018-03-17 07:34:11.639 +
Started @ 2018-03-17 07:34:51.022 +
Ended @ 2018-03-17 08:08:34.849 +
Started @ 2018-03-17 08:09:33.853 +
Ended @ 2018-03-17 08:31:43.646 +
Started @ 2018-03-17 08:31:54.175 +
Ended @ 2018-03-17 08:32:02.523 +
Started @ 2018-03-17 08:32:13.946 +
Ended @ 2018-03-17 08:32:34.626 +
Started @ 2018-03-17 08:33:20.100 +
2018-03-17 08:56:15.914 +
org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest
testGatewaySenderStatus_OnMember
Ended @ 2018-03-17 09:05:29.197 +
{noformat}
Last distributedTest running:
{noformat}
Started @ 2018-03-17 08:33:20.100 +
2018-03-17 08:56:15.914 +
org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest
testGatewaySenderStatus_OnMember
Ended @ 2018-03-17 09:05:29.197 +
{noformat}
Stack dumps are taken at 5-10 second intervals and they all look the same ...
so it looks like 433 is stuck in waiting during cache close =>
distributedLockServiceDestroys waiting for replies from 493 for ElderInit. 493
is in ClusterDistributionManager.elderChangeWait().
* Dumping stack for process 433:
2018-03-17 10:55:59
{noformat}
"RMI TCP Connection(1)-172.17.0.3" #30 daemon prio=5 os_prio=0
tid=0x7f9760001800 nid=0x1ec waiting on condition [0x7f975bffb000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xe08dd870> (a
java.util.concurrent.CountDownLatch$Sync)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
at
org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64)
at
org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766)
at
org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853)
at
org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72)
at
org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.getElderStateWithTryLock(ClusterDistributionManager.java:3359)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.getElderState(ClusterDistributionManager.java:3309)
at
org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:238)
at
org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:347)
at
org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:327)
at
org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:318)
at
org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:872)
at
org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1227)
- locked <0xe09a8768> (a
org.apache.geode.distributed.internal.locks.DLockGrantor)
at
org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:646)
at
[jira] [Commented] (GEODE-4749) change AnalyzeSerializables to not store method bytecodes in sanctioned/actual files
[
https://issues.apache.org/jira/browse/GEODE-4749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405351#comment-16405351
]
Michael Dodge commented on GEODE-4749:
--
{{CompiledClassUtils}} may also need a little work.
> change AnalyzeSerializables to not store method bytecodes in
> sanctioned/actual files
>
>
> Key: GEODE-4749
> URL: https://issues.apache.org/jira/browse/GEODE-4749
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Reporter: Bruce Schuchardt
>Priority: Major
>
> AnalyzeSerializables stores a string representation of the bytecodes of the
> toData/fromData methods in sanctionedDataSerializables.txt and
> actualDataSerializables.dat but it only pays attention to the number of
> bytecodes when detecting changes to these methods. Many of the bytecode
> strings are now out of date. Though the methods have the same number of
> bytecodes the actual code generated by the compiler is different now than it
> used to be.
> We need to change the ClassAndMethodDetails class to only care about the
> number of bytecodes and not hold onto the bytes themselves. Then regenerate
> all of the sanctionedDataSerializables.txt files in the various modules (run
> the test and copy the actualDataSerializables.dat file over the
> sanctionedDataSerializables.txt file). This will help our git pull request
> diffs be compact and understandable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4893) import cluster configuration command shuts down the existing servers
[
https://issues.apache.org/jira/browse/GEODE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-4893:
---
Description:
`import cluster-configuration --zip-file-name=...` in a cluster which has
locator and servers (Server has no application regions defined yet). the server
is shutdown without any message in the logs as to why the server was shutdown.
Gfsh says import was successful.
On manual restart of the server I can see that the config was actually imported
successfully.
We had added the feature that user can do an {{import cluster-configuration
--zip-file-name=...}} without shutting down the vanilla servers, and the
servers cache would just bounce. This feature needs to be re-hashed out.
was:
`import cluster-configuration --zip-file-name=...` in a cluster which has
locator and servers (Server has no application regions defined yet). the server
is shutdown without any message in the logs as to why the server was shutdown.
Gfsh says import was successful.
On manual restart of the server I can see that the config was actually imported
successfully.
> import cluster configuration command shuts down the existing servers
>
>
> Key: GEODE-4893
> URL: https://issues.apache.org/jira/browse/GEODE-4893
> Project: Geode
> Issue Type: Bug
> Components: configuration, gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>
> `import cluster-configuration --zip-file-name=...` in a cluster which has
> locator and servers (Server has no application regions defined yet). the
> server is shutdown without any message in the logs as to why the server was
> shutdown. Gfsh says import was successful.
> On manual restart of the server I can see that the config was actually
> imported successfully.
>
> We had added the feature that user can do an {{import cluster-configuration
> --zip-file-name=...}} without shutting down the vanilla servers, and the
> servers cache would just bounce. This feature needs to be re-hashed out.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4894) JDBC connector needs to be work with databases support for mixed case identifiers
[ https://issues.apache.org/jira/browse/GEODE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-4894: Affects Version/s: 1.4.0 > JDBC connector needs to be work with databases support for mixed case > identifiers > - > > Key: GEODE-4894 > URL: https://issues.apache.org/jira/browse/GEODE-4894 > Project: Geode > Issue Type: Bug > Components: docs, extensions, regions >Affects Versions: 1.4.0 >Reporter: Darrel Schneider >Priority: Major > > Currently, the jdbc connector will convert a database column name to all > lower case if a region mapping for that column does not exist. But it is > possible that the database supports mixed case identifiers in which case the > connector should honor the mixed case column name. > Also, when the connector is creating the prepared statement, the string it > uses does not quote the column names in that string. They should be quoted > since the database may support mixed case quoted identifiers. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4875) JdbcLoader will not always find an existing pdx field type if it is not all lower case
[ https://issues.apache.org/jira/browse/GEODE-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-4875. - Resolution: Duplicate > JdbcLoader will not always find an existing pdx field type if it is not all > lower case > -- > > Key: GEODE-4875 > URL: https://issues.apache.org/jira/browse/GEODE-4875 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.6.0 >Reporter: Darrel Schneider >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > When doing a read using the JdbcLoader, if the region mapping has a > pdx-class-name and does not have a pdx-field to column-name mapping, then it > will only find the existing pdx field type if the field name is all lower > case. > You will see a JdbcConnectorException with this message when you hit this bug: > "Could not find PdxType for field " + fieldName + ". Add class " + > pdxClassName + " with " + fieldName + " to pdx registry." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4894) JDBC connector needs to be work with databases support for mixed case identifiers
Darrel Schneider created GEODE-4894: --- Summary: JDBC connector needs to be work with databases support for mixed case identifiers Key: GEODE-4894 URL: https://issues.apache.org/jira/browse/GEODE-4894 Project: Geode Issue Type: Bug Components: docs, extensions, regions Reporter: Darrel Schneider Currently, the jdbc connector will convert a database column name to all lower case if a region mapping for that column does not exist. But it is possible that the database supports mixed case identifiers in which case the connector should honor the mixed case column name. Also, when the connector is creating the prepared statement, the string it uses does not quote the column names in that string. They should be quoted since the database may support mixed case quoted identifiers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4873) Javadocs on ProtobufUtilities are generating a warning
[
https://issues.apache.org/jira/browse/GEODE-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-4873:
--
Labels: pull-request-available (was: )
> Javadocs on ProtobufUtilities are generating a warning
> --
>
> Key: GEODE-4873
> URL: https://issues.apache.org/jira/browse/GEODE-4873
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Kirk Lund
>Assignee: Michael Dodge
>Priority: Major
> Labels: pull-request-available
>
> Javadocs on ProtobufUtilities are generating a warning:
> {noformat}
> /Users/klund/dev/gemfire_CLEAN/open/geode-protobuf/src/main/java/org/apache/geode/internal/protocol/protobuf/v1/utilities/ProtobufUtilities.java:33:
> warning - Tag @link: reference not found: ProtobufRequestUtilities
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4815) ParallelGatewaySenderOperation_2_DUnitTest testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion failed with suspect string
[
https://issues.apache.org/jira/browse/GEODE-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405349#comment-16405349
]
ASF subversion and git services commented on GEODE-4815:
Commit 752bc238c37003ebabe132af7598469cbbf07eb6 in geode's branch
refs/heads/develop from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=752bc23 ]
GEODE-4815: Forced locator members to be LOCATOR_DM_TYPES
> ParallelGatewaySenderOperation_2_DUnitTest
> testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion
> failed with suspect string
>
>
> Key: GEODE-4815
> URL: https://issues.apache.org/jira/browse/GEODE-4815
> Project: Geode
> Issue Type: Improvement
> Components: tests, wan
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ParallelGatewaySenderOperation_2_DUnitTest
> testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion
> failed with suspect string
> {noformat}
> Found suspect string in log4j at line 2444
> [fatal 2018/03/06 23:47:36.347 UTC tid=770]
> Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.5(181):32771]
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:403)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:561)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:508)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:495)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4888) Document security-udp-dhalgo property
[ https://issues.apache.org/jira/browse/GEODE-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-4888: -- Assignee: Karen Smoler Miller > Document security-udp-dhalgo property > - > > Key: GEODE-4888 > URL: https://issues.apache.org/jira/browse/GEODE-4888 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > > Document the security-udp-dhalgo property. It is a string that defines the > name of a valid symmetric key cipher supported by the JDK. When defined, the > cipher will be used for server to server UDP communications. > Also update the ssl-enabled-components property definition to recommend to > users that when ssl-enabled-components is defined, they should also set > security-udp-dhalgo to secure cluster communications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4888) Document security-udp-dhalgo property
Karen Smoler Miller created GEODE-4888: -- Summary: Document security-udp-dhalgo property Key: GEODE-4888 URL: https://issues.apache.org/jira/browse/GEODE-4888 Project: Geode Issue Type: Improvement Components: docs Reporter: Karen Smoler Miller Document the security-udp-dhalgo property. It is a string that defines the name of a valid symmetric key cipher supported by the JDK. When defined, the cipher will be used for server to server UDP communications. Also update the ssl-enabled-components property definition to recommend to users that when ssl-enabled-components is defined, they should also set security-udp-dhalgo to secure cluster communications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4885) DistributedRestoreSystemPropertiesTest is failing
[
https://issues.apache.org/jira/browse/GEODE-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-4885:
Assignee: Kirk Lund
> DistributedRestoreSystemPropertiesTest is failing
> -
>
> Key: GEODE-4885
> URL: https://issues.apache.org/jira/browse/GEODE-4885
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>Priority: Major
>
> This test is supposedly checking for any {{DUnitTest}} that inadvertently
> runs under the {{test}} gradle task or, more specifically, is categorized as
> a {{UnitTest}}.
> Unfortunately, due to the way that Junit determines what category a test is
> in (by creating an instance of the class), it will also invoke any static
> declarations. It also triggers parameterized values. The result is that some
> {{DistributedTests}} actually end up launching DUnit VMs even though the
> actual tests don't run. Depending on test ordering this can lead to
> {{DistributedRestoreSystemPropertiesTest}} failing intermittently.
> By examining the test report, it appears that the following DUnit tests are
> triggering this problem:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowLogCommandDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest
> org.apache.geode.security.ClientAuthenticationPart2DUnitTest
> org.apache.geode.cache.lucene.LuceneCommandsSecurityDUnitTest
> org.apache.geode.management.internal.configuration.ClusterConfigurationIndexWithFromClauseDUnitTest
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTest
> org.apache.geode.security.ClientAuthenticationDUnitTest
> org.apache.geode.security.ClientAuthorizationCQDUnitTest
> org.apache.geode.internal.cache.TxCommitMessageBackwardCompatibilityDUnitTest
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4857) make a public ClusterConfigurationService to retrive/perisist configuration objects
[ https://issues.apache.org/jira/browse/GEODE-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405103#comment-16405103 ] ASF subversion and git services commented on GEODE-4857: Commit 694ee1dfab0aaf07824c2b3aecafbbc47dfbf45d in geode's branch refs/heads/develop from [~jinmeiliao] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=694ee1d ] GEODE-4857: add interface methods to ClusterConfigurationService (#1637) * GEODE-4857: add interface methods to ClusterConfigurationService > make a public ClusterConfigurationService to retrive/perisist configuration > objects > --- > > Key: GEODE-4857 > URL: https://issues.apache.org/jira/browse/GEODE-4857 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > # have InternalClusterConfigurationService implement this interface > # All the internal commands should still be able to access the > InternalClusterConfigService. > # Refer to the wiki for the apis: > [https://cwiki.apache.org/confluence/display/GEODE/Public+API+for+Cluster+Configuration] > # Mark this interface @experimental -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4857) make a public ClusterConfigurationService to retrive/perisist configuration objects
[ https://issues.apache.org/jira/browse/GEODE-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405104#comment-16405104 ] ASF subversion and git services commented on GEODE-4857: Commit 694ee1dfab0aaf07824c2b3aecafbbc47dfbf45d in geode's branch refs/heads/develop from [~jinmeiliao] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=694ee1d ] GEODE-4857: add interface methods to ClusterConfigurationService (#1637) * GEODE-4857: add interface methods to ClusterConfigurationService > make a public ClusterConfigurationService to retrive/perisist configuration > objects > --- > > Key: GEODE-4857 > URL: https://issues.apache.org/jira/browse/GEODE-4857 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > # have InternalClusterConfigurationService implement this interface > # All the internal commands should still be able to access the > InternalClusterConfigService. > # Refer to the wiki for the apis: > [https://cwiki.apache.org/confluence/display/GEODE/Public+API+for+Cluster+Configuration] > # Mark this interface @experimental -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4889) Make Cache::createDataInput/Output return value type
Blake Bender created GEODE-4889: --- Summary: Make Cache::createDataInput/Output return value type Key: GEODE-4889 URL: https://issues.apache.org/jira/browse/GEODE-4889 Project: Geode Issue Type: Improvement Components: native client Reporter: Blake Bender There doesn't appear to be any compelling reason why we're handing out shared pointers here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4498) CI failure: org.apache.geode.management.internal.cli.commands.DestroyAsyncEventQueueCommandDUnitTest > destroyAeqWhenQueueDoesNotExist_deafultReturnsError FAILED
[
https://issues.apache.org/jira/browse/GEODE-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-4498:
---
Affects Version/s: 1.6.0
> CI failure:
> org.apache.geode.management.internal.cli.commands.DestroyAsyncEventQueueCommandDUnitTest
> > destroyAeqWhenQueueDoesNotExist_deafultReturnsError FAILED
> -
>
> Key: GEODE-4498
> URL: https://issues.apache.org/jira/browse/GEODE-4498
> Project: Geode
> Issue Type: Bug
> Components: gfsh, wan
>Affects Versions: 1.4.0, 1.6.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Priority: Major
> Labels: CI
>
> Occurred in CI on geode 1.4:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.4.0/jobs/DistributedTest/builds/16
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.MemberVM$$Lambda$43/465470667.run in VM 0
> running on Host 39e2a1b72a9e with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:363)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
> at
> org.apache.geode.test.dunit.rules.MemberVM.waitTillAsyncEventQueuesAreReadyOnServers(MemberVM.java:126)
> at
> org.apache.geode.management.internal.cli.commands.DestroyAsyncEventQueueCommandDUnitTest.destroyAeqWhenQueueDoesNotExist_deafultReturnsError(DestroyAsyncEventQueueCommandDUnitTest.java:90)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in org.apache.geode.test.junit.rules.MemberStarterRule was not
> fulfilled within 2 seconds.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4890) intermittent failure of ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest dataWriterCanStillOnlyWriteAfterFailover
[
https://issues.apache.org/jira/browse/GEODE-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider updated GEODE-4890:
Affects Version/s: 1.6.0
> intermittent failure of
> ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest
> dataWriterCanStillOnlyWriteAfterFailover
>
>
> Key: GEODE-4890
> URL: https://issues.apache.org/jira/browse/GEODE-4890
> Project: Geode
> Issue Type: Bug
> Components: client/server, security
>Affects Versions: 1.6.0
>Reporter: Darrel Schneider
>Priority: Major
>
> Looking at this test on line 263 I think we just might need to have the test
> wait a while for the client pool to detect that it has a new primary on the
> "assertThat" line in the following block:
> {noformat}
> server_to_fail.invoke(() -> ClusterStartupRule.getCache().close()); //
> Confirm failover VMProvider secondaryServer =
> (server1.equals(server_to_fail)) ? server2 : server1;
> assertThat(secondaryServer).isEqualTo(determinePrimaryServer(client));
> {noformat}
> {noformat}
> dataWriterCanStillOnlyWriteAfterFailover[clientVersion=130]
> org.junit.ComparisonFailure: expected:<...unit.rules.MemberVM@[19582245]> but
> was:<...unit.rules.MemberVM@[23c51fe4]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.security.ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.dataWriterCanStillOnlyWriteAfterFailover(ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.java:263)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4890) intermittent failure of ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest dataWriterCanStillOnlyWriteAfterFailover
Darrel Schneider created GEODE-4890:
---
Summary: intermittent failure of
ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest
dataWriterCanStillOnlyWriteAfterFailover
Key: GEODE-4890
URL: https://issues.apache.org/jira/browse/GEODE-4890
Project: Geode
Issue Type: Bug
Components: client/server, security
Reporter: Darrel Schneider
Looking at this test on line 263 I think we just might need to have the test
wait a while for the client pool to detect that it has a new primary on the
"assertThat" line in the following block:
{noformat}
server_to_fail.invoke(() -> ClusterStartupRule.getCache().close()); // Confirm
failover VMProvider secondaryServer = (server1.equals(server_to_fail)) ?
server2 : server1;
assertThat(secondaryServer).isEqualTo(determinePrimaryServer(client));
{noformat}
{noformat}
dataWriterCanStillOnlyWriteAfterFailover[clientVersion=130]
org.junit.ComparisonFailure: expected:<...unit.rules.MemberVM@[19582245]> but
was:<...unit.rules.MemberVM@[23c51fe4]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.security.ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.dataWriterCanStillOnlyWriteAfterFailover(ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.java:263)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4885) DistributedRestoreSystemPropertiesTest is failing
[
https://issues.apache.org/jira/browse/GEODE-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-4885:
--
Labels: pull-request-available (was: )
> DistributedRestoreSystemPropertiesTest is failing
> -
>
> Key: GEODE-4885
> URL: https://issues.apache.org/jira/browse/GEODE-4885
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
>
> This test is supposedly checking for any {{DUnitTest}} that inadvertently
> runs under the {{test}} gradle task or, more specifically, is categorized as
> a {{UnitTest}}.
> Unfortunately, due to the way that Junit determines what category a test is
> in (by creating an instance of the class), it will also invoke any static
> declarations. It also triggers parameterized values. The result is that some
> {{DistributedTests}} actually end up launching DUnit VMs even though the
> actual tests don't run. Depending on test ordering this can lead to
> {{DistributedRestoreSystemPropertiesTest}} failing intermittently.
> By examining the test report, it appears that the following DUnit tests are
> triggering this problem:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowLogCommandDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest
> org.apache.geode.security.ClientAuthenticationPart2DUnitTest
> org.apache.geode.cache.lucene.LuceneCommandsSecurityDUnitTest
> org.apache.geode.management.internal.configuration.ClusterConfigurationIndexWithFromClauseDUnitTest
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTest
> org.apache.geode.security.ClientAuthenticationDUnitTest
> org.apache.geode.security.ClientAuthorizationCQDUnitTest
> org.apache.geode.internal.cache.TxCommitMessageBackwardCompatibilityDUnitTest
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4814) Categorize FunctionService Tests
[ https://issues.apache.org/jira/browse/GEODE-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-4814. Resolution: Fixed > Categorize FunctionService Tests > > > Key: GEODE-4814 > URL: https://issues.apache.org/jira/browse/GEODE-4814 > Project: Geode > Issue Type: Task > Components: functions >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > add a new FunctionServiceTest interface and categorize all relevant dunit and > integration tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4869) Move all the Configuration objects to a public package
[ https://issues.apache.org/jira/browse/GEODE-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4869: -- Labels: pull-request-available (was: ) > Move all the Configuration objects to a public package > -- > > Key: GEODE-4869 > URL: https://issues.apache.org/jira/browse/GEODE-4869 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > > # Currently the configuration objects generated by the xsd is in > org.apache.geode.internal.cache.configuration package. We need to move them > all to a public package, probably org.apache.geode.cache.configuration > package. > # Consider rename CacheConfig to CacheType and RegionConfig to RegionType > for consistency with other classes in the package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4887) ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
[
https://issues.apache.org/jira/browse/GEODE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-4887:
Affects Version/s: 1.5.0
> ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
> ---
>
> Key: GEODE-4887
> URL: https://issues.apache.org/jira/browse/GEODE-4887
> Project: Geode
> Issue Type: Bug
> Components: offheap
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Priority: Major
>
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest >
> testDistributedUpdate FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest$1.run in VM 1
> running on Host 34d5b30e2f93 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:313)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:59)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:48)
> at
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest.preTearDownAssertions(PartitionedRegionOffHeapDUnitTest.java:49)
> Caused by:
> java.lang.AssertionError:
> Expecting empty but was:<[MemoryBlock{MemoryAddress=139834149486752,
> State=ALLOCATED, BlockSize=24, SlabId=0, FreeListId=NONE, RefCount=1,
> isSerialized=true, isCompressed=false, DataType=java.lang.String,
> DataValue=NEW_VALUE}]>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4887) ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
[
https://issues.apache.org/jira/browse/GEODE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-4887:
Component/s: offheap
> ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
> ---
>
> Key: GEODE-4887
> URL: https://issues.apache.org/jira/browse/GEODE-4887
> Project: Geode
> Issue Type: Bug
> Components: offheap
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Priority: Major
>
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest >
> testDistributedUpdate FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest$1.run in VM 1
> running on Host 34d5b30e2f93 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:313)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:59)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:48)
> at
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest.preTearDownAssertions(PartitionedRegionOffHeapDUnitTest.java:49)
> Caused by:
> java.lang.AssertionError:
> Expecting empty but was:<[MemoryBlock{MemoryAddress=139834149486752,
> State=ALLOCATED, BlockSize=24, SlabId=0, FreeListId=NONE, RefCount=1,
> isSerialized=true, isCompressed=false, DataType=java.lang.String,
> DataValue=NEW_VALUE}]>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4887) ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
Eric Shu created GEODE-4887:
---
Summary: ci Failure:
PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
Key: GEODE-4887
URL: https://issues.apache.org/jira/browse/GEODE-4887
Project: Geode
Issue Type: Bug
Reporter: Eric Shu
org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest >
testDistributedUpdate FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest$1.run in VM 1
running on Host 34d5b30e2f93 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
at org.apache.geode.test.dunit.VM.invoke(VM.java:313)
at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:59)
at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:48)
at
org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest.preTearDownAssertions(PartitionedRegionOffHeapDUnitTest.java:49)
Caused by:
java.lang.AssertionError:
Expecting empty but was:<[MemoryBlock{MemoryAddress=139834149486752,
State=ALLOCATED, BlockSize=24, SlabId=0, FreeListId=NONE, RefCount=1,
isSerialized=true, isCompressed=false, DataType=java.lang.String,
DataValue=NEW_VALUE}]>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4886) Add test to WANRollingUpgradeDUnitTest to detect serialization changes to GatewaySenderEventImpl
nabarun created GEODE-4886: -- Summary: Add test to WANRollingUpgradeDUnitTest to detect serialization changes to GatewaySenderEventImpl Key: GEODE-4886 URL: https://issues.apache.org/jira/browse/GEODE-4886 Project: Geode Issue Type: Bug Components: wan Reporter: nabarun GatewaySenderEventImpl types are added to the queue. When rolling upgrade occurs, these events are gii'd/distributed as region data/ not as messages. That means the toData_version and fromData_version code does not get executed. We should have a test (or two) in WANRollingUpgradeDUnitTest that can detect this scenario. I believe the scenario is trying to get a new sender to deserialize an old event: 1.create a sender, pause 2.do puts, build up the queue. 3. roll to current 4.start senders on current The second scenario is to get new events to flow back to the old member and have the old member try to deserialize the new event 1.)create a sender, pause 2.)do puts, build up the queue. 3.) roll to current 4.) do additional puts that get queued in the new member with a redundant copy on the old member 5.) remove the new member 6.) start sender on old member -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4815) ParallelGatewaySenderOperation_2_DUnitTest testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion failed with suspect string
[
https://issues.apache.org/jira/browse/GEODE-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405127#comment-16405127
]
ASF subversion and git services commented on GEODE-4815:
Commit 4cfc83f075940cadcaf48471e80cfab463f07793 in geode's branch
refs/heads/feature/GEODE-4815 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4cfc83f ]
GEODE-4815: Forced locator members to be LOCATOR_DM_TYPES
> ParallelGatewaySenderOperation_2_DUnitTest
> testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion
> failed with suspect string
>
>
> Key: GEODE-4815
> URL: https://issues.apache.org/jira/browse/GEODE-4815
> Project: Geode
> Issue Type: Improvement
> Components: tests, wan
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ParallelGatewaySenderOperation_2_DUnitTest
> testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion
> failed with suspect string
> {noformat}
> Found suspect string in log4j at line 2444
> [fatal 2018/03/06 23:47:36.347 UTC tid=770]
> Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.5(181):32771]
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:403)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:561)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:508)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:495)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4869) Move all the Configuration objects to a public package
[ https://issues.apache.org/jira/browse/GEODE-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-4869: --- Component/s: configuration > Move all the Configuration objects to a public package > -- > > Key: GEODE-4869 > URL: https://issues.apache.org/jira/browse/GEODE-4869 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > > # Currently the configuration objects generated by the xsd is in > org.apache.geode.internal.cache.configuration package. We need to move them > all to a public package, probably org.apache.geode.cache.configuration > package. > # Consider rename CacheConfig to CacheType and RegionConfig to RegionType > for consistency with other classes in the package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-1279) Tests for old TRAC bugs should be renamed to useful names
[ https://issues.apache.org/jira/browse/GEODE-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-1279: -- Labels: pull-request-available (was: ) > Tests for old TRAC bugs should be renamed to useful names > - > > Key: GEODE-1279 > URL: https://issues.apache.org/jira/browse/GEODE-1279 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > > Examples: > * Bug52289JUnitTest -> FinalStaticArrayShouldNotCauseSegFaultTest > * Bug36619JUnitTest -> MembershipAttributesAreSerializableTest > * Bug34387DUnitTest -> CreateAndLocalDestroyInTXRegressionTest > * Bug35214DUnitTest -> EntriesDoNotExpireDuringGIIRegressionTest > * Bug38013DUnitTest -> RemotePRValuesAreNotDeserializedRegressionTest > * Bug34948DUnitTest -> ValuesAreLazilyDeserializedRegressionTest > Remaining: > * > geode-core/src/test/java/org/apache/geode/cache/query/Bug32947ValueConstraintJUnitTest.java > * geode-core/src/test/java/org/apache/geode/cache/query/BugJUnitTest.java > * geode-core/src/test/java/org/apache/geode/cache30/Bug38741DUnitTest.java > * geode-core/src/test/java/org/apache/geode/cache30/Bug40255JUnitTest.java > * geode-core/src/test/java/org/apache/geode/cache30/Bug40662JUnitTest.java > * geode-core/src/test/java/org/apache/geode/cache30/Bug44418JUnitTest.java > * > geode-core/src/test/java/org/apache/geode/distributed/internal/Bug40751DUnitTest.java > * geode-core/src/test/java/org/apache/geode/internal/Bug49856JUnitTest.java > * geode-core/src/test/java/org/apache/geode/internal/Bug51616JUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug33359DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug33726DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug33726JUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug34179TooManyFilesOpenJUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug34583JUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug37241DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug37244JUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug37377DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug37500JUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug39079DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug40299DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug40632DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug41091DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug41733DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug41957DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug42055DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug45164DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug45934DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug47667DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/Bug48182JUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/ha/Bug36853EventsExpiryDUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/ha/Bug48571DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/ha/Bug48879DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/Bug39356DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/Bug43684DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/Bug47388DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/Bug51400DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/tier/Bug40396DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/Bug36269DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/Bug36457DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/Bug36805DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/Bug36829DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/Bug36995DUnitTest.java > * > geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/Bug37210DUnitTest.java > *
[jira] [Updated] (GEODE-4895) Users can see how to build from source
[ https://issues.apache.org/jira/browse/GEODE-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-4895: --- Description: This will include min system requirements to both build from source and run. Section will include how to build using cmake on Linux, Windows, Solaris, and Mac. (was: This will include min system requirements to both build from source and run.) Summary: Users can see how to build from source (was: Users can see min system requirements) > Users can see how to build from source > -- > > Key: GEODE-4895 > URL: https://issues.apache.org/jira/browse/GEODE-4895 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > > This will include min system requirements to both build from source and run. > Section will include how to build using cmake on Linux, Windows, Solaris, and > Mac. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4888) Document security-udp-dhalgo property
[ https://issues.apache.org/jira/browse/GEODE-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405528#comment-16405528 ] ASF subversion and git services commented on GEODE-4888: Commit 4b5d42d6fd4fcf85d44283ce0bda9323406e4cee in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4b5d42d ] GEODE-4888 Document security-udp-dhalgo property (#1642) * GEODE-4888 Document security-udp-dhalgo property * GEODE-4888 security-udp-dhalgo revisions, per review > Document security-udp-dhalgo property > - > > Key: GEODE-4888 > URL: https://issues.apache.org/jira/browse/GEODE-4888 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Document the security-udp-dhalgo property. It is a string that defines the > name of a valid symmetric key cipher supported by the JDK. When defined, the > cipher will be used for server to server UDP communications. > Also update the ssl-enabled-components property definition to recommend to > users that when ssl-enabled-components is defined, they should also set > security-udp-dhalgo to secure cluster communications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4888) Document security-udp-dhalgo property
[ https://issues.apache.org/jira/browse/GEODE-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405530#comment-16405530 ] ASF subversion and git services commented on GEODE-4888: Commit 4b5d42d6fd4fcf85d44283ce0bda9323406e4cee in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4b5d42d ] GEODE-4888 Document security-udp-dhalgo property (#1642) * GEODE-4888 Document security-udp-dhalgo property * GEODE-4888 security-udp-dhalgo revisions, per review > Document security-udp-dhalgo property > - > > Key: GEODE-4888 > URL: https://issues.apache.org/jira/browse/GEODE-4888 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Document the security-udp-dhalgo property. It is a string that defines the > name of a valid symmetric key cipher supported by the JDK. When defined, the > cipher will be used for server to server UDP communications. > Also update the ssl-enabled-components property definition to recommend to > users that when ssl-enabled-components is defined, they should also set > security-udp-dhalgo to secure cluster communications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4888) Document security-udp-dhalgo property
[ https://issues.apache.org/jira/browse/GEODE-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405527#comment-16405527 ] ASF subversion and git services commented on GEODE-4888: Commit 4b5d42d6fd4fcf85d44283ce0bda9323406e4cee in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4b5d42d ] GEODE-4888 Document security-udp-dhalgo property (#1642) * GEODE-4888 Document security-udp-dhalgo property * GEODE-4888 security-udp-dhalgo revisions, per review > Document security-udp-dhalgo property > - > > Key: GEODE-4888 > URL: https://issues.apache.org/jira/browse/GEODE-4888 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Document the security-udp-dhalgo property. It is a string that defines the > name of a valid symmetric key cipher supported by the JDK. When defined, the > cipher will be used for server to server UDP communications. > Also update the ssl-enabled-components property definition to recommend to > users that when ssl-enabled-components is defined, they should also set > security-udp-dhalgo to secure cluster communications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-4885) DistributedRestoreSystemPropertiesTest is failing
[
https://issues.apache.org/jira/browse/GEODE-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405355#comment-16405355
]
Kirk Lund edited comment on GEODE-4885 at 3/19/18 9:00 PM:
---
I changed DUnitLauncher.launchIfNeeded() to throw an Error and this only shows
up for ShowLogCommandDUnitTest. The others show up in the JUnit report for
"test" with zero tests, zero failures, zero ignored. The custom Runners for
parameters seem to forcing the gradle junit plugin to instantiate the class in
order to examine the Categories but only for the ones that have the custom
runners.
was (Author: klund):
I changed DUnitLauncher.launchIfNeeded() to throw an Error and this only shows
up for ShowLogCommandDUnitTest. The others show up in the JUnit report for
"test" with zero tests, zero failures, zero ignored. The customer Runners for
parameters seem to forcing the gradle junit plugin to instantiate the class in
order to examine the Categories but only for the ones that have the custom
runners.
> DistributedRestoreSystemPropertiesTest is failing
> -
>
> Key: GEODE-4885
> URL: https://issues.apache.org/jira/browse/GEODE-4885
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This test is supposedly checking for any {{DUnitTest}} that inadvertently
> runs under the {{test}} gradle task or, more specifically, is categorized as
> a {{UnitTest}}.
> Unfortunately, due to the way that Junit determines what category a test is
> in (by creating an instance of the class), it will also invoke any static
> declarations. It also triggers parameterized values. The result is that some
> {{DistributedTests}} actually end up launching DUnit VMs even though the
> actual tests don't run. Depending on test ordering this can lead to
> {{DistributedRestoreSystemPropertiesTest}} failing intermittently.
> By examining the test report, it appears that the following DUnit tests are
> triggering this problem:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowLogCommandDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest
> org.apache.geode.security.ClientAuthenticationPart2DUnitTest
> org.apache.geode.cache.lucene.LuceneCommandsSecurityDUnitTest
> org.apache.geode.management.internal.configuration.ClusterConfigurationIndexWithFromClauseDUnitTest
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTest
> org.apache.geode.security.ClientAuthenticationDUnitTest
> org.apache.geode.security.ClientAuthorizationCQDUnitTest
> org.apache.geode.internal.cache.TxCommitMessageBackwardCompatibilityDUnitTest
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4869) Move all the Configuration objects to a public package
[ https://issues.apache.org/jira/browse/GEODE-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405473#comment-16405473 ] ASF subversion and git services commented on GEODE-4869: Commit d8e29f021ceee6312692fb8aeeb139f9260fde6c in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d8e29f0 ] GEODE-4869: Move all the Configuration objects to a public package (#1638) * Moved all jaxb config objects to public package * Added experimental annotation to all config objects > Move all the Configuration objects to a public package > -- > > Key: GEODE-4869 > URL: https://issues.apache.org/jira/browse/GEODE-4869 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > # Currently the configuration objects generated by the xsd is in > org.apache.geode.internal.cache.configuration package. We need to move them > all to a public package, probably org.apache.geode.cache.configuration > package. > # Consider rename CacheConfig to CacheType and RegionConfig to RegionType > for consistency with other classes in the package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4859) Create a public version of GfshCommand
[ https://issues.apache.org/jira/browse/GEODE-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4859: -- Labels: pull-request-available (was: ) > Create a public version of GfshCommand > --- > > Key: GEODE-4859 > URL: https://issues.apache.org/jira/browse/GEODE-4859 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > > this would expose > # the public Cache interface > # the public ClusterConfigurationService > # other methods in GfshCommand if appropriate, like findMember, > executeFunction etc. > # add @experiental to it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4771) Configuring 'auto-serializable-classes' incorrectly sets 'check-portability' as 'true'
[
https://issues.apache.org/jira/browse/GEODE-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405534#comment-16405534
]
ASF subversion and git services commented on GEODE-4771:
Commit 54b18eded8802561b8607b4bcdc1525915436e85 in geode's branch
refs/heads/develop from [~jujoramos]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=54b18ed ]
GEODE-4771: Changes requested by reviewers.
> Configuring 'auto-serializable-classes' incorrectly sets 'check-portability'
> as 'true'
> --
>
> Key: GEODE-4771
> URL: https://issues.apache.org/jira/browse/GEODE-4771
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> According to the documentation, the [configure
> pdx|https://geode.apache.org/docs/guide/14/tools_modules/gfsh/command-pages/configure.html]
> command should set the {{check-portability}} parameter as {{false}} when the
> user configures a list of auto serializable classes through the
> {{--auto-serializable-classes}} parameter. However, {{check-portability}}
> parameter is set as {{true}} by default.
> The problematic code is below:
>
> {code:title=ConfigurePDXCommand.java|borderStyle=solid}
> @CliCommand(value = CliStrings.CONFIGURE_PDX, help =
> CliStrings.CONFIGURE_PDX__HELP)
> @CliMetaData(relatedTopic = CliStrings.TOPIC_GEODE_REGION)
> @ResourceOperation(resource = ResourcePermission.Resource.CLUSTER, operation
> = ResourcePermission.Operation.MANAGE)
> public Result configurePDX(
> ...
> @CliOption(key = CliStrings.CONFIGURE_PDX__AUTO__SERIALIZER__CLASSES,
> /* auto-serializable-classes */
> help = CliStrings.CONFIGURE_PDX__AUTO__SERIALIZER__CLASSES__HELP)
> String[] patterns, /* the patterns which are matched against domain class
> names to determine whether they should be serialized, serialization done by
> the auto-serializer will throw an exception if the object of these classes
> are not portable to non-java languages */
> @CliOption(key =
> CliStrings.CONFIGURE_PDX__PORTABLE__AUTO__SERIALIZER__CLASSES /*
> portable-auto-serializable-classes */,
> help =
> CliStrings.CONFIGURE_PDX__PORTABLE__AUTO__SERIALIZER__CLASSES__HELP) String[]
> portablePatterns /* the patterns which are matched against domain class names
> to determine whether they should be serialized */) {
> ...
> if (patterns != null) {
> ReflectionBasedAutoSerializer nonPortableAutoSerializer
> = new ReflectionBasedAutoSerializer(true, patterns);
> cache.setPdxSerializer(nonPortableAutoSerializer);
> ird.addLine("PDX Serializer : " +
> cache.getPdxSerializer().getClass().getName());
> ird.addLine("Non portable classes :" +
> Arrays.toString(patterns));
> }
> ...
> {code}
> The help text for parameters {{auto-serializable-classes}} and
> {{portable-auto-serializable-classes}} is also wrong, it's clear that they
> should be swapped.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4771) Configuring 'auto-serializable-classes' incorrectly sets 'check-portability' as 'true'
[
https://issues.apache.org/jira/browse/GEODE-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405535#comment-16405535
]
ASF subversion and git services commented on GEODE-4771:
Commit 3fa3074af9b328a33ee2c811a711c36208c8cfce in geode's branch
refs/heads/develop from [~khowe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3fa3074 ]
GEODE-4771: Internal API was renamed
ClusterConfigurationService was changed to InternalClusterConfigurationService
after the original PR (#1574) was created.
> Configuring 'auto-serializable-classes' incorrectly sets 'check-portability'
> as 'true'
> --
>
> Key: GEODE-4771
> URL: https://issues.apache.org/jira/browse/GEODE-4771
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> According to the documentation, the [configure
> pdx|https://geode.apache.org/docs/guide/14/tools_modules/gfsh/command-pages/configure.html]
> command should set the {{check-portability}} parameter as {{false}} when the
> user configures a list of auto serializable classes through the
> {{--auto-serializable-classes}} parameter. However, {{check-portability}}
> parameter is set as {{true}} by default.
> The problematic code is below:
>
> {code:title=ConfigurePDXCommand.java|borderStyle=solid}
> @CliCommand(value = CliStrings.CONFIGURE_PDX, help =
> CliStrings.CONFIGURE_PDX__HELP)
> @CliMetaData(relatedTopic = CliStrings.TOPIC_GEODE_REGION)
> @ResourceOperation(resource = ResourcePermission.Resource.CLUSTER, operation
> = ResourcePermission.Operation.MANAGE)
> public Result configurePDX(
> ...
> @CliOption(key = CliStrings.CONFIGURE_PDX__AUTO__SERIALIZER__CLASSES,
> /* auto-serializable-classes */
> help = CliStrings.CONFIGURE_PDX__AUTO__SERIALIZER__CLASSES__HELP)
> String[] patterns, /* the patterns which are matched against domain class
> names to determine whether they should be serialized, serialization done by
> the auto-serializer will throw an exception if the object of these classes
> are not portable to non-java languages */
> @CliOption(key =
> CliStrings.CONFIGURE_PDX__PORTABLE__AUTO__SERIALIZER__CLASSES /*
> portable-auto-serializable-classes */,
> help =
> CliStrings.CONFIGURE_PDX__PORTABLE__AUTO__SERIALIZER__CLASSES__HELP) String[]
> portablePatterns /* the patterns which are matched against domain class names
> to determine whether they should be serialized */) {
> ...
> if (patterns != null) {
> ReflectionBasedAutoSerializer nonPortableAutoSerializer
> = new ReflectionBasedAutoSerializer(true, patterns);
> cache.setPdxSerializer(nonPortableAutoSerializer);
> ird.addLine("PDX Serializer : " +
> cache.getPdxSerializer().getClass().getName());
> ird.addLine("Non portable classes :" +
> Arrays.toString(patterns));
> }
> ...
> {code}
> The help text for parameters {{auto-serializable-classes}} and
> {{portable-auto-serializable-classes}} is also wrong, it's clear that they
> should be swapped.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4771) Configuring 'auto-serializable-classes' incorrectly sets 'check-portability' as 'true'
[
https://issues.apache.org/jira/browse/GEODE-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405533#comment-16405533
]
ASF subversion and git services commented on GEODE-4771:
Commit bafab6bb72938f714961c524e3e2800f4a26f827 in geode's branch
refs/heads/develop from [~jujoramos]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=bafab6b ]
GEODE-4771: Defaults in ConfigurePDXCommand
- Refactored `ConfigurePDXCommand` to allow unit testing.
- Added a custom `Interceptor` to validate command input.
- Added unit and integration tests for `ConfigurePDXCommand`.
- Fixed help strings for `auto-serializable-classes` and
`portable-auto-serializable-classes`.
- Fixed `ConfigurePDXCommand` to set `check-portability=false` when
`--auto-serializable-classes` is used.
> Configuring 'auto-serializable-classes' incorrectly sets 'check-portability'
> as 'true'
> --
>
> Key: GEODE-4771
> URL: https://issues.apache.org/jira/browse/GEODE-4771
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> According to the documentation, the [configure
> pdx|https://geode.apache.org/docs/guide/14/tools_modules/gfsh/command-pages/configure.html]
> command should set the {{check-portability}} parameter as {{false}} when the
> user configures a list of auto serializable classes through the
> {{--auto-serializable-classes}} parameter. However, {{check-portability}}
> parameter is set as {{true}} by default.
> The problematic code is below:
>
> {code:title=ConfigurePDXCommand.java|borderStyle=solid}
> @CliCommand(value = CliStrings.CONFIGURE_PDX, help =
> CliStrings.CONFIGURE_PDX__HELP)
> @CliMetaData(relatedTopic = CliStrings.TOPIC_GEODE_REGION)
> @ResourceOperation(resource = ResourcePermission.Resource.CLUSTER, operation
> = ResourcePermission.Operation.MANAGE)
> public Result configurePDX(
> ...
> @CliOption(key = CliStrings.CONFIGURE_PDX__AUTO__SERIALIZER__CLASSES,
> /* auto-serializable-classes */
> help = CliStrings.CONFIGURE_PDX__AUTO__SERIALIZER__CLASSES__HELP)
> String[] patterns, /* the patterns which are matched against domain class
> names to determine whether they should be serialized, serialization done by
> the auto-serializer will throw an exception if the object of these classes
> are not portable to non-java languages */
> @CliOption(key =
> CliStrings.CONFIGURE_PDX__PORTABLE__AUTO__SERIALIZER__CLASSES /*
> portable-auto-serializable-classes */,
> help =
> CliStrings.CONFIGURE_PDX__PORTABLE__AUTO__SERIALIZER__CLASSES__HELP) String[]
> portablePatterns /* the patterns which are matched against domain class names
> to determine whether they should be serialized */) {
> ...
> if (patterns != null) {
> ReflectionBasedAutoSerializer nonPortableAutoSerializer
> = new ReflectionBasedAutoSerializer(true, patterns);
> cache.setPdxSerializer(nonPortableAutoSerializer);
> ird.addLine("PDX Serializer : " +
> cache.getPdxSerializer().getClass().getName());
> ird.addLine("Non portable classes :" +
> Arrays.toString(patterns));
> }
> ...
> {code}
> The help text for parameters {{auto-serializable-classes}} and
> {{portable-auto-serializable-classes}} is also wrong, it's clear that they
> should be swapped.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4894) JDBC connector needs to be work with databases support for mixed case identifiers
[ https://issues.apache.org/jira/browse/GEODE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-4894: --- Assignee: Darrel Schneider > JDBC connector needs to be work with databases support for mixed case > identifiers > - > > Key: GEODE-4894 > URL: https://issues.apache.org/jira/browse/GEODE-4894 > Project: Geode > Issue Type: Bug > Components: docs, extensions, regions >Affects Versions: 1.4.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > > Currently, the jdbc connector will convert a database column name to all > lower case if a region mapping for that column does not exist. But it is > possible that the database supports mixed case identifiers in which case the > connector should honor the mixed case column name. > Also, when the connector is creating the prepared statement, the string it > uses does not quote the column names in that string. They should be quoted > since the database may support mixed case quoted identifiers. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4815) ParallelGatewaySenderOperation_2_DUnitTest testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion failed with suspect string
[
https://issues.apache.org/jira/browse/GEODE-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barry Oglesby resolved GEODE-4815.
--
Resolution: Fixed
> ParallelGatewaySenderOperation_2_DUnitTest
> testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion
> failed with suspect string
>
>
> Key: GEODE-4815
> URL: https://issues.apache.org/jira/browse/GEODE-4815
> Project: Geode
> Issue Type: Improvement
> Components: tests, wan
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ParallelGatewaySenderOperation_2_DUnitTest
> testParallelGatewaySender_SingleNode_UserPR_Destroy_SimultaneousPut_RecreateRegion
> failed with suspect string
> {noformat}
> Found suspect string in log4j at line 2444
> [fatal 2018/03/06 23:47:36.347 UTC tid=770]
> Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.5(181):32771]
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:403)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:561)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:508)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:495)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4864) Document new gfsh create jndi binding command
[ https://issues.apache.org/jira/browse/GEODE-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4864: -- Labels: pull-request-available (was: ) > Document new gfsh create jndi binding command > - > > Key: GEODE-4864 > URL: https://issues.apache.org/jira/browse/GEODE-4864 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > > The new gfsh command to create a JNDI binding was included in Geode 1.5, but > the documentation of the command was forgotten. This ticket is to complete > the documentation of the new gfsh command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4895) Users can see min system requirements
Addison created GEODE-4895: -- Summary: Users can see min system requirements Key: GEODE-4895 URL: https://issues.apache.org/jira/browse/GEODE-4895 Project: Geode Issue Type: Sub-task Components: native client Reporter: Addison This will include min system requirements to both build from source and run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4888) Document security-udp-dhalgo property
[ https://issues.apache.org/jira/browse/GEODE-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-4888. Resolution: Fixed Fix Version/s: 1.6.0 > Document security-udp-dhalgo property > - > > Key: GEODE-4888 > URL: https://issues.apache.org/jira/browse/GEODE-4888 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Document the security-udp-dhalgo property. It is a string that defines the > name of a valid symmetric key cipher supported by the JDK. When defined, the > cipher will be used for server to server UDP communications. > Also update the ssl-enabled-components property definition to recommend to > users that when ssl-enabled-components is defined, they should also set > security-udp-dhalgo to secure cluster communications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4882) AnalyzeConnectorsSerializablesJUnitTest failing intermittently with CacheClosedException
[
https://issues.apache.org/jira/browse/GEODE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405435#comment-16405435
]
ASF subversion and git services commented on GEODE-4882:
Commit c6dee63151030f5ac99c90066b66ea82be6679f7 in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c6dee63 ]
GEODE-4882: Add FlakyTest category to AnalyzeConnectorsSerializablesJUnitTest
Test testSanctionedClassesExistAndDoDeserialize is failing intermittently:
org.apache.geode.cache.CacheClosedException: Could not PDX serialize because
the cache was closed
> AnalyzeConnectorsSerializablesJUnitTest failing intermittently with
> CacheClosedException
>
>
> Key: GEODE-4882
> URL: https://issues.apache.org/jira/browse/GEODE-4882
> Project: Geode
> Issue Type: Bug
> Components: extensions, regions
>Reporter: Darrel Schneider
>Priority: Major
>
> The following failure has happened twice this week but not in a row. So this
> test is intermittently failing.
> {noformat}
> :geode-connectors:integrationTest
>
> org.apache.geode.codeAnalysis.AnalyzeConnectorsSerializablesJUnitTest >
> testSanctionedClassesExistAndDoDeserialize FAILED
> org.apache.geode.cache.CacheClosedException: Could not PDX serialize because
> the cache was closed
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4896) FunctionExceptionTest should be deleted from geode-old-client-support
Kirk Lund created GEODE-4896:
Summary: FunctionExceptionTest should be deleted from
geode-old-client-support
Key: GEODE-4896
URL: https://issues.apache.org/jira/browse/GEODE-4896
Project: Geode
Issue Type: Wish
Components: tests
Reporter: Kirk Lund
I accidentally replicated FunctionExceptionTest from geode-core under
geode-old-client-support in this previous commit from a year ago:
{noformat}
commit 97a6e1ae58504ee04f22a4cafa93d6ea32b215e2
Author: Kirk Lund
Date: Fri May 19 14:23:17 2017 -0700
GEODE-2929: remove superfluous final from methods
{noformat}
This was by accident. Module geode-old-client-support needs a
com.gemstone.gemfire version of FunctionException but it doesn't need a unit
test for it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4896) FunctionExceptionTest should be deleted from geode-old-client-support
[
https://issues.apache.org/jira/browse/GEODE-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-4896:
Assignee: Kirk Lund
> FunctionExceptionTest should be deleted from geode-old-client-support
> -
>
> Key: GEODE-4896
> URL: https://issues.apache.org/jira/browse/GEODE-4896
> Project: Geode
> Issue Type: Wish
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> I accidentally replicated FunctionExceptionTest from geode-core under
> geode-old-client-support in this previous commit from a year ago:
> {noformat}
> commit 97a6e1ae58504ee04f22a4cafa93d6ea32b215e2
> Author: Kirk Lund
> Date: Fri May 19 14:23:17 2017 -0700
> GEODE-2929: remove superfluous final from methods
> {noformat}
> This was by accident. Module geode-old-client-support needs a
> com.gemstone.gemfire version of FunctionException but it doesn't need a unit
> test for it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4832) CacheWriterGetOldValueIntegrationTest can fail because previous test left disk store around
[
https://issues.apache.org/jira/browse/GEODE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-4832:
-
Labels: Flaky (was: )
> CacheWriterGetOldValueIntegrationTest can fail because previous test left
> disk store around
> ---
>
> Key: GEODE-4832
> URL: https://issues.apache.org/jira/browse/GEODE-4832
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Priority: Minor
> Labels: Flaky
>
> The following failure was seen once. It is hard to say what was left around
> from a previous test that impacted this one. But if this one would use a tmp
> directory for its disk store then it would not accidently use a disk store
> that a previous test left around.
> Also if it used a unique region name, instead of "/region" it would not have
> had the following failure.
> {noformat}
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doTest(CacheWriterGetOldValueIntegrationTest.java:110)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry(CacheWriterGetOldValueIntegrationTest.java:71)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> doRemoveAll FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doRemoveAll(CacheWriterGetOldValueIntegrationTest.java:93)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> getOldValueInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either
[jira] [Assigned] (GEODE-4832) CacheWriterGetOldValueIntegrationTest can fail because previous test left disk store around
[
https://issues.apache.org/jira/browse/GEODE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-4832:
Assignee: Kirk Lund
> CacheWriterGetOldValueIntegrationTest can fail because previous test left
> disk store around
> ---
>
> Key: GEODE-4832
> URL: https://issues.apache.org/jira/browse/GEODE-4832
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Assignee: Kirk Lund
>Priority: Minor
> Labels: Flaky
>
> The following failure was seen once. It is hard to say what was left around
> from a previous test that impacted this one. But if this one would use a tmp
> directory for its disk store then it would not accidently use a disk store
> that a previous test left around.
> Also if it used a unique region name, instead of "/region" it would not have
> had the following failure.
> {noformat}
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doTest(CacheWriterGetOldValueIntegrationTest.java:110)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry(CacheWriterGetOldValueIntegrationTest.java:71)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> doRemoveAll FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doRemoveAll(CacheWriterGetOldValueIntegrationTest.java:93)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> getOldValueInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk
[jira] [Commented] (GEODE-4832) CacheWriterGetOldValueIntegrationTest can fail because previous test left disk store around
[
https://issues.apache.org/jira/browse/GEODE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405589#comment-16405589
]
ASF subversion and git services commented on GEODE-4832:
Commit 5bfccee21f8c7d9a1d77c8ee643d106eeecb6a20 in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5bfccee ]
GEODE-4832: Add FlakyTest category to CacheWriterGetOldValueIntegrationTest
Previously run IntegrationTest(s) is/are leaving behind a disk store
in the current working directory which then causes this test to fail.
This is intermittent because the test execution ordering is not always
consistent.
> CacheWriterGetOldValueIntegrationTest can fail because previous test left
> disk store around
> ---
>
> Key: GEODE-4832
> URL: https://issues.apache.org/jira/browse/GEODE-4832
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Priority: Minor
>
> The following failure was seen once. It is hard to say what was left around
> from a previous test that impacted this one. But if this one would use a tmp
> directory for its disk store then it would not accidently use a disk store
> that a previous test left around.
> Also if it used a unique region name, instead of "/region" it would not have
> had the following failure.
> {noformat}
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doTest(CacheWriterGetOldValueIntegrationTest.java:110)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry(CacheWriterGetOldValueIntegrationTest.java:71)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> doRemoveAll FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
>
[jira] [Assigned] (GEODE-4898) Fix field names in DestroyJndiBindingCommand
[ https://issues.apache.org/jira/browse/GEODE-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-4898: -- Assignee: Sai Boorlagadda > Fix field names in DestroyJndiBindingCommand > > > Key: GEODE-4898 > URL: https://issues.apache.org/jira/browse/GEODE-4898 > Project: Geode > Issue Type: Task > Components: gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > > Field names in DestroyJndiBindingCommand uses CREATE_BINDING. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4832) CacheWriterGetOldValueIntegrationTest can fail because previous test left disk store around
[
https://issues.apache.org/jira/browse/GEODE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405596#comment-16405596
]
ASF subversion and git services commented on GEODE-4832:
Commit 8f36acf34b91708f37a46f95e61561dd8b741823 in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f36acf ]
GEODE-4832: Cleanup CacheWriterGetOldValueIntegrationTest
> CacheWriterGetOldValueIntegrationTest can fail because previous test left
> disk store around
> ---
>
> Key: GEODE-4832
> URL: https://issues.apache.org/jira/browse/GEODE-4832
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Assignee: Kirk Lund
>Priority: Minor
> Labels: Flaky
>
> The following failure was seen once. It is hard to say what was left around
> from a previous test that impacted this one. But if this one would use a tmp
> directory for its disk store then it would not accidently use a disk store
> that a previous test left around.
> Also if it used a unique region name, instead of "/region" it would not have
> had the following failure.
> {noformat}
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doTest(CacheWriterGetOldValueIntegrationTest.java:110)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry(CacheWriterGetOldValueIntegrationTest.java:71)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> doRemoveAll FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
>
[jira] [Created] (GEODE-4898) Fix field names in DestroyJndiBindingCommand
Sai Boorlagadda created GEODE-4898: -- Summary: Fix field names in DestroyJndiBindingCommand Key: GEODE-4898 URL: https://issues.apache.org/jira/browse/GEODE-4898 Project: Geode Issue Type: Task Components: gfsh Reporter: Sai Boorlagadda Field names in DestroyJndiBindingCommand uses CREATE_BINDING. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3523) AutoConnectionSourceDUnitTest: testDynamicallyFindLocators failed with Unable to connect to any locators in the list
[ https://issues.apache.org/jira/browse/GEODE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-3523: - Fix Version/s: (was: 1.5.0) > AutoConnectionSourceDUnitTest: testDynamicallyFindLocators failed with Unable > to connect to any locators in the list > > > Key: GEODE-3523 > URL: https://issues.apache.org/jira/browse/GEODE-3523 > Project: Geode > Issue Type: Bug > Components: locator >Reporter: Hitesh Khamesra >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest > > testDynamicallyFindLocators FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest$3.call > in VM 2 running on Host 97e556d10832 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:387) > at org.apache.geode.test.dunit.VM.invoke(VM.java:357) > at org.apache.geode.test.dunit.VM.invoke(VM.java:325) > at > org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.putInVM(AutoConnectionSourceDUnitTest.java:470) > at > org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.putAndWaitForSuccess(AutoConnectionSourceDUnitTest.java:448) > at > org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.testDynamicallyFindLocators(AutoConnectionSourceDUnitTest.java:199) > Caused by: > org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to > connect to any locators in the list [LocatorAddress > [socketInetAddress=97e556d10832/172.17.0.4:26078, hostname=97e556d10832, > isIpString=false], LocatorAddress > [socketInetAddress=97e556d10832/172.17.0.4:29796, hostname=172.17.0.4, > isIpString=true]] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4864) Document new gfsh create jndi binding command
[ https://issues.apache.org/jira/browse/GEODE-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405639#comment-16405639 ] ASF subversion and git services commented on GEODE-4864: Commit 05feafbfe6eed4a7894e1fbc960a518ffe7bfaba in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=05feafb ] GEODE-4864 Document the gfsh create jndi-binding command (#1644) * GEODE-4864 Document the gfsh create jndi-binding command * GEODE-4864 gfsh create jndi-binding ref page revision, per review * GEODE-4864 Minor gfsh create jndi-binding description change, per review > Document new gfsh create jndi binding command > - > > Key: GEODE-4864 > URL: https://issues.apache.org/jira/browse/GEODE-4864 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > The new gfsh command to create a JNDI binding was included in Geode 1.5, but > the documentation of the command was forgotten. This ticket is to complete > the documentation of the new gfsh command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4864) Document new gfsh create jndi binding command
[ https://issues.apache.org/jira/browse/GEODE-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405640#comment-16405640 ] ASF subversion and git services commented on GEODE-4864: Commit 05feafbfe6eed4a7894e1fbc960a518ffe7bfaba in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=05feafb ] GEODE-4864 Document the gfsh create jndi-binding command (#1644) * GEODE-4864 Document the gfsh create jndi-binding command * GEODE-4864 gfsh create jndi-binding ref page revision, per review * GEODE-4864 Minor gfsh create jndi-binding description change, per review > Document new gfsh create jndi binding command > - > > Key: GEODE-4864 > URL: https://issues.apache.org/jira/browse/GEODE-4864 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > The new gfsh command to create a JNDI binding was included in Geode 1.5, but > the documentation of the command was forgotten. This ticket is to complete > the documentation of the new gfsh command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4864) Document new gfsh create jndi binding command
[ https://issues.apache.org/jira/browse/GEODE-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405641#comment-16405641 ] ASF subversion and git services commented on GEODE-4864: Commit 05feafbfe6eed4a7894e1fbc960a518ffe7bfaba in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=05feafb ] GEODE-4864 Document the gfsh create jndi-binding command (#1644) * GEODE-4864 Document the gfsh create jndi-binding command * GEODE-4864 gfsh create jndi-binding ref page revision, per review * GEODE-4864 Minor gfsh create jndi-binding description change, per review > Document new gfsh create jndi binding command > - > > Key: GEODE-4864 > URL: https://issues.apache.org/jira/browse/GEODE-4864 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > The new gfsh command to create a JNDI binding was included in Geode 1.5, but > the documentation of the command was forgotten. This ticket is to complete > the documentation of the new gfsh command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4864) Document new gfsh create jndi binding command
[ https://issues.apache.org/jira/browse/GEODE-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405642#comment-16405642 ] ASF subversion and git services commented on GEODE-4864: Commit 05feafbfe6eed4a7894e1fbc960a518ffe7bfaba in geode's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=05feafb ] GEODE-4864 Document the gfsh create jndi-binding command (#1644) * GEODE-4864 Document the gfsh create jndi-binding command * GEODE-4864 gfsh create jndi-binding ref page revision, per review * GEODE-4864 Minor gfsh create jndi-binding description change, per review > Document new gfsh create jndi binding command > - > > Key: GEODE-4864 > URL: https://issues.apache.org/jira/browse/GEODE-4864 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > The new gfsh command to create a JNDI binding was included in Geode 1.5, but > the documentation of the command was forgotten. This ticket is to complete > the documentation of the new gfsh command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4896) FunctionExceptionTest should be deleted from geode-old-client-support
[
https://issues.apache.org/jira/browse/GEODE-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-4896.
--
Resolution: Fixed
Fix Version/s: 1.6.0
> FunctionExceptionTest should be deleted from geode-old-client-support
> -
>
> Key: GEODE-4896
> URL: https://issues.apache.org/jira/browse/GEODE-4896
> Project: Geode
> Issue Type: Wish
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.6.0
>
>
> I accidentally replicated FunctionExceptionTest from geode-core under
> geode-old-client-support in this previous commit from a year ago:
> {noformat}
> commit 97a6e1ae58504ee04f22a4cafa93d6ea32b215e2
> Author: Kirk Lund
> Date: Fri May 19 14:23:17 2017 -0700
> GEODE-2929: remove superfluous final from methods
> {noformat}
> This was by accident. Module geode-old-client-support needs a
> com.gemstone.gemfire version of FunctionException but it doesn't need a unit
> test for it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4896) FunctionExceptionTest should be deleted from geode-old-client-support
[
https://issues.apache.org/jira/browse/GEODE-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405582#comment-16405582
]
ASF subversion and git services commented on GEODE-4896:
Commit 1564f45b474c1ca1e370b4055dad284f5677cad2 in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1564f45 ]
GEODE-4896: Delete com.gemstone.gemfire duplicate of FunctionExceptionTest
> FunctionExceptionTest should be deleted from geode-old-client-support
> -
>
> Key: GEODE-4896
> URL: https://issues.apache.org/jira/browse/GEODE-4896
> Project: Geode
> Issue Type: Wish
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.6.0
>
>
> I accidentally replicated FunctionExceptionTest from geode-core under
> geode-old-client-support in this previous commit from a year ago:
> {noformat}
> commit 97a6e1ae58504ee04f22a4cafa93d6ea32b215e2
> Author: Kirk Lund
> Date: Fri May 19 14:23:17 2017 -0700
> GEODE-2929: remove superfluous final from methods
> {noformat}
> This was by accident. Module geode-old-client-support needs a
> com.gemstone.gemfire version of FunctionException but it doesn't need a unit
> test for it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3881) [CI Failure] org.apache.geode.redis.SetsJUnitTest > testSDiffAndStore FAILED
[
https://issues.apache.org/jira/browse/GEODE-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405593#comment-16405593
]
Dan Smith commented on GEODE-3881:
--
This reproduced again:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/IntegrationTest/builds/7]
{noformat}
redis.clients.jedis.exceptions.JedisDataException: ERR This key could not be
created. Gemfire does not allow certain characters to used in keys
at redis.clients.jedis.Protocol.processError(Protocol.java:127)
at redis.clients.jedis.Protocol.process(Protocol.java:161)
at redis.clients.jedis.Protocol.read(Protocol.java:215)
at
redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
at redis.clients.jedis.Connection.getIntegerReply(Connection.java:265)
at redis.clients.jedis.Jedis.sadd(Jedis.java:1109)
at
org.apache.geode.redis.SetsJUnitTest.testSDiffAndStore(SetsJUnitTest.java:147){noformat}
stdout has this underlying failure
{noformat}
[error 2018/03/16 21:53:00.813 UTC tid=0x39]
null
org.apache.geode.redis.internal.RegionCreationException:
Member| Status
|
---
d0fc05e6-3569-4ab6-58a3-73f99447926d(34629:loner):0:3d18cd30 | ERROR: Region
names may not begin with a double-underscore: __FFwUZtX`a
at
org.apache.geode.redis.internal.RegionProvider.createRegionGlobally(RegionProvider.java:412)
at
org.apache.geode.redis.internal.RegionProvider.getOrCreateRegion0(RegionProvider.java:289)
at
org.apache.geode.redis.internal.RegionProvider.getOrCreateRegion(RegionProvider.java:209)
at
org.apache.geode.redis.internal.executor.set.SAddExecutor.executeCommand(SAddExecutor.java:43)
at
org.apache.geode.redis.internal.ExecutionHandlerContext.executeWithoutTransaction(ExecutionHandlerContext.java:235)
at
org.apache.geode.redis.internal.ExecutionHandlerContext.executeCommand(ExecutionHandlerContext.java:199)
at
org.apache.geode.redis.internal.ExecutionHandlerContext.channelRead(ExecutionHandlerContext.java:139)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
at
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:141)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:645)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:580)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:497)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:459)
at
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886)
at java.lang.Thread.run(Thread.java:748)
{noformat}
> [CI Failure] org.apache.geode.redis.SetsJUnitTest > testSDiffAndStore FAILED
>
>
> Key: GEODE-3881
> URL: https://issues.apache.org/jira/browse/GEODE-3881
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Eric Shu
>Priority: Major
>
> {noformat}
> org.apache.geode.redis.SetsJUnitTest > testSDiffAndStore FAILED
> redis.clients.jedis.exceptions.JedisDataException: ERR This key could not
> be created. Gemfire does not allow certain characters to used in keys
> at
[jira] [Reopened] (GEODE-3205) CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles
[
https://issues.apache.org/jira/browse/GEODE-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu reopened GEODE-3205:
-
Reproduced with different stack.
org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest >
aboveZeroDeletesPreviousFiles FAILED
java.lang.AssertionError:
Expecting file:
to exist.
at
org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles(DiskSpaceLimitIntegrationTest.java:205)
> CI failure:
> org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles
>
>
> Key: GEODE-3205
> URL: https://issues.apache.org/jira/browse/GEODE-3205
> Project: Geode
> Issue Type: Bug
> Components: statistics, tests
>Reporter: Lynn Gallinat
>Assignee: Kirk Lund
>Priority: Major
> Labels: Flaky, pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest >
> aboveZeroDeletesPreviousFiles FAILED
> org.junit.ComparisonFailure: [Unexpected files:
> [/tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles-02-01.gfs,
> /tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles-02-02.gfs,
> /tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles.gfs]]
> expected:<[2]> but was:<[3]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.validateNumberFiles(DiskSpaceLimitIntegrationTest.java:263)
> at
> org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles(DiskSpaceLimitIntegrationTest.java:202)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4897) Availability is wrong on some commands.
Sai Boorlagadda created GEODE-4897:
--
Summary: Availability is wrong on some commands.
Key: GEODE-4897
URL: https://issues.apache.org/jira/browse/GEODE-4897
Project: Geode
Issue Type: Bug
Components: gfsh
Reporter: Sai Boorlagadda
For example, look at any JDBC connector commands or ListJndiBindingCommand and
could be more. When you launch gfsh (and not connected) then you can see these
commands are available.
{noformat}
create jdbc-connection (Available)
(Experimental) Create a connection for communicating with a database through
jdbc.
create jdbc-mapping (Available)
(Experimental) Create a mapping for a region for use with a JDBC database
connection.{noformat}
{{There is a test to test the availability marker but the test itself has a bug
due to which the command authors are not warned about the marker. Look into
CommandAvailabilityIndicatorTest}}
{noformat}
if (cliMetaData != null && !cliMetaData.shellOnly()) -> here cliMetaData could
be null if the command author forget to annotate the command.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4893) import cluster configuration command shuts down the existing servers
[
https://issues.apache.org/jira/browse/GEODE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-4893:
---
Component/s: docs
> import cluster configuration command shuts down the existing servers
>
>
> Key: GEODE-4893
> URL: https://issues.apache.org/jira/browse/GEODE-4893
> Project: Geode
> Issue Type: Bug
> Components: configuration, docs, gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>
> `import cluster-configuration --zip-file-name=...` in a cluster which has
> locator and servers (Server has no application regions defined yet). the
> server is shutdown without any message in the logs as to why the server was
> shutdown. Gfsh says import was successful.
> On manual restart of the server I can see that the config was actually
> imported successfully.
>
> We had added the feature that user can do an {{import cluster-configuration
> --zip-file-name=...}} without shutting down the vanilla servers, and the
> servers cache would just bounce. This feature needs to be re-hashed out.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4832) CacheWriterGetOldValueIntegrationTest can fail because previous test left disk store around
[
https://issues.apache.org/jira/browse/GEODE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405600#comment-16405600
]
Kirk Lund commented on GEODE-4832:
--
To fix this bug we'll probably need either:
* Gradle JUnit change or custom JUnit Runner that runs each test class with a
unique, temporary current working directory
* Custom JUnit Rule that deletes all Geode output artifacts from current
working directory
> CacheWriterGetOldValueIntegrationTest can fail because previous test left
> disk store around
> ---
>
> Key: GEODE-4832
> URL: https://issues.apache.org/jira/browse/GEODE-4832
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Assignee: Kirk Lund
>Priority: Minor
> Labels: Flaky
>
> The following failure was seen once. It is hard to say what was left around
> from a previous test that impacted this one. But if this one would use a tmp
> directory for its disk store then it would not accidently use a disk store
> that a previous test left around.
> Also if it used a unique region name, instead of "/region" it would not have
> had the following failure.
> {noformat}
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doTest(CacheWriterGetOldValueIntegrationTest.java:110)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry(CacheWriterGetOldValueIntegrationTest.java:71)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> doRemoveAll FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doRemoveAll(CacheWriterGetOldValueIntegrationTest.java:93)
>
[jira] [Reopened] (GEODE-3523) AutoConnectionSourceDUnitTest: testDynamicallyFindLocators failed with Unable to connect to any locators in the list
[
https://issues.apache.org/jira/browse/GEODE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reopened GEODE-3523:
--
This issue reoccurred even after this fix.
[http://files.apachegeode-ci.info/builds/1.5.0-build.8/test-results/distributedTest/1521258734/classes/org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.html#testDynamicallyFindLocators]
{noformat}
org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest >
testDynamicallyFindLocators FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest$3.call in
VM 2 running on Host 45b2d9d9ceba with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
at org.apache.geode.test.dunit.VM.invoke(VM.java:336)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.putInVM(AutoConnectionSourceDUnitTest.java:470)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.putAndWaitForSuccess(AutoConnectionSourceDUnitTest.java:448)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.testDynamicallyFindLocators(AutoConnectionSourceDUnitTest.java:199)
Caused by:
org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
connect to any locators in the list [LocatorAddress
[socketInetAddress=45b2d9d9ceba/172.17.0.3:24659, hostname=172.17.0.3,
isIpString=true], LocatorAddress
[socketInetAddress=45b2d9d9ceba/172.17.0.3:26744, hostname=45b2d9d9ceba,
isIpString=false]]
{noformat}
> AutoConnectionSourceDUnitTest: testDynamicallyFindLocators failed with Unable
> to connect to any locators in the list
>
>
> Key: GEODE-3523
> URL: https://issues.apache.org/jira/browse/GEODE-3523
> Project: Geode
> Issue Type: Bug
> Components: locator
>Reporter: Hitesh Khamesra
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest >
> testDynamicallyFindLocators FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest$3.call
> in VM 2 running on Host 97e556d10832 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:325)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.putInVM(AutoConnectionSourceDUnitTest.java:470)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.putAndWaitForSuccess(AutoConnectionSourceDUnitTest.java:448)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.testDynamicallyFindLocators(AutoConnectionSourceDUnitTest.java:199)
> Caused by:
> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to
> connect to any locators in the list [LocatorAddress
> [socketInetAddress=97e556d10832/172.17.0.4:26078, hostname=97e556d10832,
> isIpString=false], LocatorAddress
> [socketInetAddress=97e556d10832/172.17.0.4:29796, hostname=172.17.0.4,
> isIpString=true]]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4898) Fix field names in DestroyJndiBindingCommand
[ https://issues.apache.org/jira/browse/GEODE-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4898: -- Labels: pull-request-available (was: ) > Fix field names in DestroyJndiBindingCommand > > > Key: GEODE-4898 > URL: https://issues.apache.org/jira/browse/GEODE-4898 > Project: Geode > Issue Type: Task > Components: gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > > Field names in DestroyJndiBindingCommand uses CREATE_BINDING. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-4832) CacheWriterGetOldValueIntegrationTest can fail because previous test left disk store around
[
https://issues.apache.org/jira/browse/GEODE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405600#comment-16405600
]
Kirk Lund edited comment on GEODE-4832 at 3/20/18 12:11 AM:
To fix this bug we'll probably need either:
* Gradle JUnit change or custom JUnit Runner that runs each test class with a
unique, temporary current working directory
* Custom JUnit Rule that deletes all Geode output artifacts from current
working directory
Some additional things that could help:
* Change integration test to use test names for region names
* Change all integration tests to use TemporaryFolder for all Geode artifacts
was (Author: klund):
To fix this bug we'll probably need either:
* Gradle JUnit change or custom JUnit Runner that runs each test class with a
unique, temporary current working directory
* Custom JUnit Rule that deletes all Geode output artifacts from current
working directory
> CacheWriterGetOldValueIntegrationTest can fail because previous test left
> disk store around
> ---
>
> Key: GEODE-4832
> URL: https://issues.apache.org/jira/browse/GEODE-4832
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Assignee: Kirk Lund
>Priority: Minor
> Labels: Flaky
>
> The following failure was seen once. It is hard to say what was left around
> from a previous test that impacted this one. But if this one would use a tmp
> directory for its disk store then it would not accidently use a disk store
> that a previous test left around.
> Also if it used a unique region name, instead of "/region" it would not have
> had the following failure.
> {noformat}
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doTest(CacheWriterGetOldValueIntegrationTest.java:110)
> at
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry(CacheWriterGetOldValueIntegrationTest.java:71)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest >
> doRemoveAll FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted
> to disk so it can not be recreated on the same disk store without
> persistence. Either destroy the persistent region, recreate it as overflow
> and persistent, or create the overflow only region on a different disk store.
> at
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at
>
[jira] [Commented] (GEODE-4881) handle concurrent lucene indexing (after region created) with rebalance
[
https://issues.apache.org/jira/browse/GEODE-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405636#comment-16405636
]
ASF subversion and git services commented on GEODE-4881:
Commit eb3c725636b256ff8881dc949b2fa586631a349b in geode's branch
refs/heads/feature/GEODE-4881 from [~lhughesgodfrey]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=eb3c725 ]
GEODE-4881: Support lucene reindexing (of existing data) with rebalance
* LuceneServiceImpl changes to support AEQ addition to existing region (after
index initialized)
* Testing with and without redundancy
> handle concurrent lucene indexing (after region created) with rebalance
> ---
>
> Key: GEODE-4881
> URL: https://issues.apache.org/jira/browse/GEODE-4881
> Project: Geode
> Issue Type: New Feature
> Components: lucene
>Reporter: Shelley Lynn Hughes-Godfrey
>Priority: Major
>
> {noformat}
> While adding a Lucene index to a region with data, if a rebalance is
> triggered during re-indexing, the index should complete successfully and
> match the region data.
> If I add a Lucene index while a rebalance is in progress, the index should
> successfully complete and match the region data. (*)
> (*) Note: It may be acceptable to detect a rebalance in progress before
> starting and wait for it to finish before adding the Lucene index.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
