[jira] [Commented] (GEODE-6616) Flaky: AutoConnectionSourceDUnitTest > testClientDynamicallyDropsStoppedLocator FAILED
[
https://issues.apache.org/jira/browse/GEODE-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949845#comment-16949845
]
Aaron Lindsey commented on GEODE-6616:
--
Failed again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1158
{noformat}
org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest >
testClientDynamicallyDropsStoppedLocator FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1894
java.net.ConnectException: Connection refused (Connection refused)
at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
at
java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)
at
java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
at java.base/java.net.Socket.connect(Socket.java:591)
at
org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:898)
at
org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:839)
at
org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:828)
at
org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:205)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocatorUsingConnection(AutoConnectionSourceImpl.java:202)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:192)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:274)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.access$200(AutoConnectionSourceImpl.java:63)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl$UpdateLocatorListTask.run2(AutoConnectionSourceImpl.java:477)
at
org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1304)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at
java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at
org.apache.geode.internal.ScheduledThreadPoolExecutorWithKeepAlive$DelegatingScheduledFuture.run(ScheduledThreadPoolExecutorWithKeepAlive.java:276)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
> Flaky: AutoConnectionSourceDUnitTest >
> testClientDynamicallyDropsStoppedLocator FAILED
> --
>
> Key: GEODE-6616
> URL: https://issues.apache.org/jira/browse/GEODE-6616
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Minor
>
> Failed connection..
> {noformat}
> [vm3] [info 2019/04/09 06:48:44.919 UTC
> tid=0x20] Got result: EXCEPTION_OCCURRED
> [vm3] org.apache.geode.cache.client.ServerOperationException: remote server
> on 16f27a14ad79(255:loner):52816:5f2bdb00: : While performing a remote put
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:389)
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:313)
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.attemptReadResponse(PutOp.java:454)
> [vm3] at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:387)
> [vm3] at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:289)
> [vm3] at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:351)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:908)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:172)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:130)
> [vm3] at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:792)
> [vm3] at
>
[jira] [Updated] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey updated GEODE-7237:
-
Labels: (was: observability)
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Aaron Lindsey
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey updated GEODE-7237:
-
Labels: observability (was: )
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Kirk Lund
>Priority: Major
> Labels: observability
> Fix For: 1.11.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey reassigned GEODE-7237:
Assignee: Aaron Lindsey (was: Kirk Lund)
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Aaron Lindsey
>Priority: Major
> Labels: observability
> Fix For: 1.11.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7289) StandaloneClientManagementAPIAcceptanceTest uses default JMX port
[ https://issues.apache.org/jira/browse/GEODE-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-7289. -- Fix Version/s: 1.11.0 Resolution: Fixed > StandaloneClientManagementAPIAcceptanceTest uses default JMX port > - > > Key: GEODE-7289 > URL: https://issues.apache.org/jira/browse/GEODE-7289 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Fix For: 1.11.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > StandaloneClientManagementAPIAcceptanceTest picks random ports for locator > port and http service port, but uses default for jmx manager port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7288) LuceneIntegrationTest uses non-existent system property logLevel
[
https://issues.apache.org/jira/browse/GEODE-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-7288.
--
Fix Version/s: 1.11.0
Resolution: Fixed
> LuceneIntegrationTest uses non-existent system property logLevel
>
>
> Key: GEODE-7288
> URL: https://issues.apache.org/jira/browse/GEODE-7288
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> DUnit ProcessManager used to set the system property {{logLevel}} but this
> was changed to {{gemfire.log-level}} in 2016. The only uses of {{logLevel}}
> were:
> *
> geode-core/src/distributedTest/java/org/apache/geode/distributed/internal/LDM
> (which is an unused class)
> *
> geode-lucene-test/src/main/java/org/apache/geode/cache/lucene/LuceneIntegrationTest
> (super class for other lucene tests)
> LuceneIntegrationTest:
> {noformat}
> cf.set(ConfigurationProperties.LOG_LEVEL, System.getProperty("logLevel",
> "info"));
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7288) LuceneIntegrationTest uses non-existent system property logLevel
[
https://issues.apache.org/jira/browse/GEODE-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-7288:
Assignee: Kirk Lund
> LuceneIntegrationTest uses non-existent system property logLevel
>
>
> Key: GEODE-7288
> URL: https://issues.apache.org/jira/browse/GEODE-7288
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> DUnit ProcessManager used to set the system property {{logLevel}} but this
> was changed to {{gemfire.log-level}} in 2016. The only uses of {{logLevel}}
> were:
> *
> geode-core/src/distributedTest/java/org/apache/geode/distributed/internal/LDM
> (which is an unused class)
> *
> geode-lucene-test/src/main/java/org/apache/geode/cache/lucene/LuceneIntegrationTest
> (super class for other lucene tests)
> LuceneIntegrationTest:
> {noformat}
> cf.set(ConfigurationProperties.LOG_LEVEL, System.getProperty("logLevel",
> "info"));
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7288) LuceneIntegrationTest uses non-existent system property logLevel
[
https://issues.apache.org/jira/browse/GEODE-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949840#comment-16949840
]
ASF subversion and git services commented on GEODE-7288:
Commit 1dabc155adf2c41639a92b720ca76eed942f3dc8 in geode's branch
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1dabc15 ]
GEODE-7288: Remove broken uses of logLevel system property (#4148)
* Delete LDM which is unused
* Remove line that reads logLevel system property in LuceneIntegrationTest
> LuceneIntegrationTest uses non-existent system property logLevel
>
>
> Key: GEODE-7288
> URL: https://issues.apache.org/jira/browse/GEODE-7288
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Kirk Lund
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> DUnit ProcessManager used to set the system property {{logLevel}} but this
> was changed to {{gemfire.log-level}} in 2016. The only uses of {{logLevel}}
> were:
> *
> geode-core/src/distributedTest/java/org/apache/geode/distributed/internal/LDM
> (which is an unused class)
> *
> geode-lucene-test/src/main/java/org/apache/geode/cache/lucene/LuceneIntegrationTest
> (super class for other lucene tests)
> LuceneIntegrationTest:
> {noformat}
> cf.set(ConfigurationProperties.LOG_LEVEL, System.getProperty("logLevel",
> "info"));
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7289) StandaloneClientManagementAPIAcceptanceTest uses default JMX port
[ https://issues.apache.org/jira/browse/GEODE-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949838#comment-16949838 ] ASF subversion and git services commented on GEODE-7289: Commit 198bec05cd8212e8b8fffbf66f4ec4292eae8f56 in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=198bec0 ] GEODE-7289: Use random port in StandaloneClientManagementAPIAcceptanceTest (#4151) The test is already using random ports for the locator port and http service port. Use a random port for jmx manager port as well. > StandaloneClientManagementAPIAcceptanceTest uses default JMX port > - > > Key: GEODE-7289 > URL: https://issues.apache.org/jira/browse/GEODE-7289 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > StandaloneClientManagementAPIAcceptanceTest picks random ports for locator > port and http service port, but uses default for jmx manager port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-3780) suspected member is never watched again after passing final check
[ https://issues.apache.org/jira/browse/GEODE-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949831#comment-16949831 ] ASF subversion and git services commented on GEODE-3780: Commit b70dcebef7ab4703058546b67dc3c395fc5d3b39 in geode's branch refs/heads/develop from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b70dceb ] GEODE-3780: Fixing monitoring of suspected member after passed final check - Suspected member is never watched again after passing final check - This restores our original behavior (pre-1.0) behavior of performing a final check on a member if UDP communications with that member fail. - We now also send exonoration messages to all other members if a suspect is cleared. We need to do that because another member may have sent a Suspect message that was ignored because the suspect was already undergoing a final check. - I also noticed that our tcp/ip final check loop was performing more than one check in many cases because the nanosecond clock has a coarse granularity. A socket so-timeout based on the millisecond clock was timing out but the nanosecond clock didn't line up with that timeout and caused the "for" loop to make another attempt. I changed that loop to convert the nanosecond clock value to milliseconds. > suspected member is never watched again after passing final check > - > > Key: GEODE-3780 > URL: https://issues.apache.org/jira/browse/GEODE-3780 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce J Schuchardt >Assignee: Bruce J Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 3h > Remaining Estimate: 0h > > In a network-down test we saw a node on the losing side of the network > partition perform final checks on members on the winning side. One of the > final checks mysteriously succeeded > [info 2017/09/17 12:24:45.552 PDT > gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 Detection thread 4> tid=0x128] Final check failed but detected recent message > traffic for suspect member > 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135):1026 > [info 2017/09/17 12:24:45.552 PDT > gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 Detection thread 4> tid=0x128] Final check passed for suspect member > 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135):1026 > After this the suspected member was never checked again and the losing side > failed to shut down. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949829#comment-16949829
]
ASF subversion and git services commented on GEODE-7237:
Commit 924e3f8948352dca8e2cdfd49a8b96a524af8b13 in geode's branch
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=924e3f8 ]
GEODE-7237: Disable invalidHostname temporarily
Revert this when GEODE-7237 is fixed.
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949830#comment-16949830
]
ASF subversion and git services commented on GEODE-7237:
Commit 924e3f8948352dca8e2cdfd49a8b96a524af8b13 in geode's branch
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=924e3f8 ]
GEODE-7237: Disable invalidHostname temporarily
Revert this when GEODE-7237 is fixed.
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7240) Prevent Usage of Aggregates within WHERE clause
[
https://issues.apache.org/jira/browse/GEODE-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949826#comment-16949826
]
Anilkumar Gingade commented on GEODE-7240:
--
[~jjramos]
It will be nice to have failing query as part of the ticket. That would tell
how the failing query looks like.
> Prevent Usage of Aggregates within WHERE clause
> ---
>
> Key: GEODE-7240
> URL: https://issues.apache.org/jira/browse/GEODE-7240
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Aggregate functions shouldn't be allowed as part of the {{WHERE}} clause.
> Currently, instead of rejecting the query, we throw a {{ClassCastException}}
> while trying to evaluate the condition:
> {noformat}
> org.apache.geode.cache.query.TypeMismatchException: Unable to use a
> relational comparison operator to compare an instance of class '
> org.apache.geode.cache.query.internal.aggregate.XXX ' with an instance of '
> java.lang.XXX '
> at
> org.apache.geode.cache.query.internal.types.TypeUtils$ComparisonStrategy.get(TypeUtils.java:144)
> at
> org.apache.geode.cache.query.internal.types.TypeUtils.compare(TypeUtils.java:499)
> at
> org.apache.geode.cache.query.internal.CompiledComparison.evaluate(CompiledComparison.java:137)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:438)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:53)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.executeUsingContext(DefaultQuery.java:432)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:267)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:199)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7096) GemcachedBinaryClientJUnitTest > testExpiration timed out waiting for operation
[
https://issues.apache.org/jira/browse/GEODE-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949825#comment-16949825
]
Aaron Lindsey commented on GEODE-7096:
--
Failed again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1143
> GemcachedBinaryClientJUnitTest > testExpiration timed out waiting for
> operation
> ---
>
> Key: GEODE-7096
> URL: https://issues.apache.org/jira/browse/GEODE-7096
> Project: Geode
> Issue Type: Bug
>Reporter: Bill Burcham
>Priority: Major
>
> In this CI build:
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/WindowsIntegrationTestOpenJDK8/builds/668
> {code}
> org.apache.geode.memcached.GemcachedBinaryClientJUnitTest > testExpiration
> FAILED
> java.lang.RuntimeException: Timed out waiting for operation
> Caused by:
> net.spy.memcached.internal.CheckedOperationTimeoutException: Timed
> out waiting for operation - failing node:
> packer-5d4b73b4-8160-44b6-cb53-08c803700c64/10.0.0.64:28196
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6871) Disk free space info exposed via JMX
[ https://issues.apache.org/jira/browse/GEODE-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949817#comment-16949817 ] ASF subversion and git services commented on GEODE-6871: Commit 7440b89a9607b9f413d4ef0ab1d935814deaef84 in geode's branch refs/heads/develop from Alberto Bustamante Reyes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7440b89 ] GEODE-6871: Disk free space info exposed via JMX (#4067) * GEODE-6871: Disk free space info exposed via JMX - fix test cases naming - defaults for getDiskUsagePercentage & getDiskFreePercentage - Change test case name > Disk free space info exposed via JMX > > > Key: GEODE-6871 > URL: https://issues.apache.org/jira/browse/GEODE-6871 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Time Spent: 3.5h > Remaining Estimate: 0h > > Given I need to scale down or scale up my servers based on usage > When I setup my monitoring of JMX metrics through an MBean > Then I have the ability to see Disk Free Percentage > AND Disk Free in Bytes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-6159) SystemOutRule does not play well with Log4j in tests that verify logging behavior
[ https://issues.apache.org/jira/browse/GEODE-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-6159. -- Resolution: Won't Fix > SystemOutRule does not play well with Log4j in tests that verify logging > behavior > - > > Key: GEODE-6159 > URL: https://issues.apache.org/jira/browse/GEODE-6159 > Project: Geode > Issue Type: Bug > Components: logging, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > We need to find a better solution that is simpler than having to specify a > custom log4j2.xml with LoggerContextRule but works better than SystemOutRule. > The problem with using SystemOutRule to test output from a logger is that > log4j captures System.out into its own static final reference. So tests like > this must be run in their own forked JVM. > See GEODE-6158 for some background about the tests that do specify custom > log4j2.xml config files. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GEODE-6159) SystemOutRule does not play well with Log4j in tests that verify logging behavior
[ https://issues.apache.org/jira/browse/GEODE-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund closed GEODE-6159. > SystemOutRule does not play well with Log4j in tests that verify logging > behavior > - > > Key: GEODE-6159 > URL: https://issues.apache.org/jira/browse/GEODE-6159 > Project: Geode > Issue Type: Bug > Components: logging, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > We need to find a better solution that is simpler than having to specify a > custom log4j2.xml with LoggerContextRule but works better than SystemOutRule. > The problem with using SystemOutRule to test output from a logger is that > log4j captures System.out into its own static final reference. So tests like > this must be run in their own forked JVM. > See GEODE-6158 for some background about the tests that do specify custom > log4j2.xml config files. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-6183) CI Failure: LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-6183. -- Resolution: Fixed > CI Failure: > LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed > with ConditionTimeoutException > > > Key: GEODE-6183 > URL: https://issues.apache.org/jira/browse/GEODE-6183 > Project: Geode > Issue Type: Bug > Components: ci, gfsh >Reporter: Eric Shu >Assignee: Kirk Lund >Priority: Major > Fix For: 1.11.0 > > Time Spent: 5h 50m > Remaining Estimate: 0h > > Test failed in > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/223 > org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > > startDeletesStaleControlFiles FAILED > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase that > uses org.apache.geode.distributed.LocatorLauncher expected:<[online]> but > was:<[not responding]> within 300 seconds. > Caused by: > org.junit.ComparisonFailure: expected:<[online]> but was:<[not > responding]> -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-6566) CI failure: MemberMBeanAttributesDUnitTest testReplRegionAttributes failed with suspect string
[
https://issues.apache.org/jira/browse/GEODE-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-6566.
--
Fix Version/s: 1.11.0
Resolution: Fixed
> CI failure: MemberMBeanAttributesDUnitTest testReplRegionAttributes failed
> with suspect string
> --
>
> Key: GEODE-6566
> URL: https://issues.apache.org/jira/browse/GEODE-6566
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Barrett Oglesby
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> CI run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/543
> Suspect strings:
> {noformat}
> org.apache.geode.management.MemberMBeanAttributesDUnitTest >
> testReplRegionAttributes FAILED
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2383
> [fatal 2019/03/27 01:09:04.965 UTC tid=195] null
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
> at java.util.HashMap$ValueIterator.next(HashMap.java:1471)
> at
> org.apache.geode.internal.statistics.SampleCollector.sample(SampleCollector.java:231)
> at
> org.apache.geode.internal.statistics.HostStatSampler.run(HostStatSampler.java:232)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in log4j at line 2396
> [fatal 2019/03/27 01:09:04.972 UTC tid=195] Uncaught exception
> in thread Thread[StatSampler,10,RMI Runtime]
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
> at java.util.HashMap$ValueIterator.next(HashMap.java:1471)
> at
> org.apache.geode.internal.statistics.SampleCollector.sample(SampleCollector.java:231)
> at
> org.apache.geode.internal.statistics.HostStatSampler.run(HostStatSampler.java:232)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6566) CI failure: MemberMBeanAttributesDUnitTest testReplRegionAttributes failed with suspect string
[
https://issues.apache.org/jira/browse/GEODE-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949775#comment-16949775
]
ASF subversion and git services commented on GEODE-6566:
Commit ee5ec15413714008db0024eafb6540d14f9a5392 in geode's branch
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ee5ec15 ]
GEODE-6566: Rename to MemberMXBeanAttributesDistributedTest
Rename MemberMBeanAttributesDUnitTest as MemberMXBeanAttributesDistributedTest.
> CI failure: MemberMBeanAttributesDUnitTest testReplRegionAttributes failed
> with suspect string
> --
>
> Key: GEODE-6566
> URL: https://issues.apache.org/jira/browse/GEODE-6566
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Barrett Oglesby
>Assignee: Kirk Lund
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> CI run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/543
> Suspect strings:
> {noformat}
> org.apache.geode.management.MemberMBeanAttributesDUnitTest >
> testReplRegionAttributes FAILED
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2383
> [fatal 2019/03/27 01:09:04.965 UTC tid=195] null
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
> at java.util.HashMap$ValueIterator.next(HashMap.java:1471)
> at
> org.apache.geode.internal.statistics.SampleCollector.sample(SampleCollector.java:231)
> at
> org.apache.geode.internal.statistics.HostStatSampler.run(HostStatSampler.java:232)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in log4j at line 2396
> [fatal 2019/03/27 01:09:04.972 UTC tid=195] Uncaught exception
> in thread Thread[StatSampler,10,RMI Runtime]
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
> at java.util.HashMap$ValueIterator.next(HashMap.java:1471)
> at
> org.apache.geode.internal.statistics.SampleCollector.sample(SampleCollector.java:231)
> at
> org.apache.geode.internal.statistics.HostStatSampler.run(HostStatSampler.java:232)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7289) StandaloneClientManagementAPIAcceptanceTest uses default JMX port
Kirk Lund created GEODE-7289: Summary: StandaloneClientManagementAPIAcceptanceTest uses default JMX port Key: GEODE-7289 URL: https://issues.apache.org/jira/browse/GEODE-7289 Project: Geode Issue Type: Test Components: tests Reporter: Kirk Lund StandaloneClientManagementAPIAcceptanceTest picks random ports for locator port and http service port, but uses default for jmx manager port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7189) CI Failure: ServerLauncherTest > startWaitsForStartupTasksToComplete failed
[
https://issues.apache.org/jira/browse/GEODE-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-7189:
Assignee: Kirk Lund
> CI Failure: ServerLauncherTest > startWaitsForStartupTasksToComplete failed
> ---
>
> Key: GEODE-7189
> URL: https://issues.apache.org/jira/browse/GEODE-7189
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Assignee: Kirk Lund
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> org.apache.geode.distributed.ServerLauncherTest >
> startWaitsForStartupTasksToComplete FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.distributed.ServerLauncherTest that uses
> java.util.concurrent.CompletableFuture
> Wanted but not invoked:
> completableFuture.thenRun();
> -> at
> org.apache.geode.distributed.ServerLauncherTest.lambda$startWaitsForStartupTasksToComplete$14(ServerLauncherTest.java:428)
> Actually, there were zero interactions with this mock.
> within 300 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.distributed.ServerLauncherTest.startWaitsForStartupTasksToComplete(ServerLauncherTest.java:428)
> Caused by:
> Wanted but not invoked:
> completableFuture.thenRun();
> -> at
> org.apache.geode.distributed.ServerLauncherTest.lambda$startWaitsForStartupTasksToComplete$14(ServerLauncherTest.java:428)
> Actually, there were zero interactions with this mock.
> at
> org.apache.geode.distributed.ServerLauncherTest.lambda$startWaitsForStartupTasksToComplete$14(ServerLauncherTest.java:428)
> {noformat}
> UnitTestOpenJDK11 #943:
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/UnitTestOpenJDK11/builds/943
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0108/test-results/test/1568154432/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0108/test-artifacts/1568154432/unittestfiles-OpenJDK11-9.10.0-build.0108.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7285) Several Examples Don't Work on Windows
[ https://issues.apache.org/jira/browse/GEODE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949710#comment-16949710 ] ASF subversion and git services commented on GEODE-7285: Commit 7f2197e4e5867799f8292bf868e9fbe5374d9aac in geode-native's branch refs/heads/develop from Michael Martell [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=7f2197e ] GEODE-7285: Fix examples on Windows - servers scripts using wrong region name > Several Examples Don't Work on Windows > -- > > Key: GEODE-7285 > URL: https://issues.apache.org/jira/browse/GEODE-7285 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The list of examples below do not work do to a mismatch between the server > start/stop scripts and the code. Specifically, several scripts create/destroy > a region of one name, but the example code tries to use a region of a > different name. > Broken examples: > * continuousquery (Windows) > * dataserializable (Windows) > * pdxserializable (Windows) > * pdxserializer (Windows) > * transaction (Windows) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949679#comment-16949679
]
Aaron Lindsey commented on GEODE-7237:
--
Failed again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1147
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey reopened GEODE-7237:
--
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7277) CI failure: DestroyLuceneIndexCommandsDUnitTest > testDestroyIndexesWithOneIndexAndRegionInOneMember failed with RegionDestroyedException suspicious string
[
https://issues.apache.org/jira/browse/GEODE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaojian Zhou reassigned GEODE-7277:
Assignee: Xiaojian Zhou
> CI failure: DestroyLuceneIndexCommandsDUnitTest >
> testDestroyIndexesWithOneIndexAndRegionInOneMember failed with
> RegionDestroyedException suspicious string
> ---
>
> Key: GEODE-7277
> URL: https://issues.apache.org/jira/browse/GEODE-7277
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Reporter: Barrett Oglesby
>Assignee: Xiaojian Zhou
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DistributedTestOpenJDK11 #1147
> (https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1147)
> failed with this RegionDestroyedException suspicious string:
> {noformat}
> org.apache.geode.cache.lucene.internal.cli.DestroyLuceneIndexCommandsDUnitTest
> > testDestroyIndexesWithOneIndexAndRegionInOneMember FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2012
> [fatal 2019/10/07 21:18:02.334 GMT tid=845] Uncaught
> exception in thread Thread[FederatingManager4,5,RMI Runtime]
> org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/_monitoringRegion_172.17.0.1041002';scope=DISTRIBUTED_NO_ACK';dataPolicy=REPLICATE]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7293)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6157)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroyRegion(DistributedRegion.java:1821)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6128)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroyRegion(LocalRegion.java:2251)
> at
> org.apache.geode.internal.cache.AbstractRegion.localDestroyRegion(AbstractRegion.java:452)
> at
> org.apache.geode.management.internal.FederatingManager.removeMemberArtifacts(FederatingManager.java:216)
> at
> org.apache.geode.management.internal.FederatingManager.access$000(FederatingManager.java:67)
> at
> org.apache.geode.management.internal.FederatingManager$RemoveMemberTask.run(FederatingManager.java:564)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> This failure has nothing to do with Lucene.
> Some analysis shows that stopping a member and stopping the locator nearly
> simultaneously can cause this RegionDestroyedException.
> The test output shows:
> The locator starts:
> {noformat}
> [vm0] [info 2019/10/07 21:17:55.174 GMT
> tid=0x22] Starting DistributionManager
> 172.17.0.10(locator-0:87:locator):41000. (took 26 ms)
> {noformat}
> Server1 starts and _monitoringRegion_172.17.0.1041001 is created for it
> in the locator:
> {noformat}
> [vm1] [info 2019/10/07 21:17:59.681 GMT
> tid=0x22] Starting DistributionManager 172.17.0.10(server-1:95):41001.
> (took 405 ms)
> [vm0] [info 2019/10/07 21:17:59.684 GMT tid=0x332]
> Initializing region _monitoringRegion_172.17.0.1041001
> [vm0] [info 2019/10/07 21:17:59.694 GMT tid=0x332]
> Initialization of region _monitoringRegion_172.17.0.1041001 completed
> {noformat}
> Server2 starts and _monitoringRegion_172.17.0.1041002 is created for it
> in the locator:
> {noformat}
> [vm2] [info 2019/10/07 21:18:00.379 GMT
> tid=0x22] Starting DistributionManager 172.17.0.10(server-2:104):41002.
> (took 361 ms)
> [vm0] [info 2019/10/07 21:18:00.379 GMT tid=0x33c]
> Initializing region _monitoringRegion_172.17.0.1041002
> [vm0] [info 2019/10/07 21:18:00.424 GMT tid=0x33c]
> Initialization of region _monitoringRegion_172.17.0.1041002 completed
> {noformat}
> Server2 shuts down:
> {noformat}
> [vm2] [info 2019/10/07 21:18:02.007 GMT
> tid=0x22] Shutting down DistributionManager
> 172.17.0.10(server-2:104):41002.
> [vm2] [info 2019/10/07 21:18:02.127 GMT
> tid=0x22] Marking DistributionManager 172.17.0.10(server-2:104):41002 as
> closed.
> {noformat}
> Server1 shuts down:
> {noformat}
> [vm1] [info 2019/10/07 21:18:02.189 GMT
> tid=0x22] Shutting down DistributionManager
>
[jira] [Issue Comment Deleted] (GEODE-7277) CI failure: DestroyLuceneIndexCommandsDUnitTest > testDestroyIndexesWithOneIndexAndRegionInOneMember failed with RegionDestroyedException suspicious string
[
https://issues.apache.org/jira/browse/GEODE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaojian Zhou updated GEODE-7277:
-
Comment: was deleted
(was: This is reproduced in
http://hydradb.gemfire.pivotal.io/hdb/testresult/6479293)
> CI failure: DestroyLuceneIndexCommandsDUnitTest >
> testDestroyIndexesWithOneIndexAndRegionInOneMember failed with
> RegionDestroyedException suspicious string
> ---
>
> Key: GEODE-7277
> URL: https://issues.apache.org/jira/browse/GEODE-7277
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Reporter: Barrett Oglesby
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DistributedTestOpenJDK11 #1147
> (https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1147)
> failed with this RegionDestroyedException suspicious string:
> {noformat}
> org.apache.geode.cache.lucene.internal.cli.DestroyLuceneIndexCommandsDUnitTest
> > testDestroyIndexesWithOneIndexAndRegionInOneMember FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2012
> [fatal 2019/10/07 21:18:02.334 GMT tid=845] Uncaught
> exception in thread Thread[FederatingManager4,5,RMI Runtime]
> org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/_monitoringRegion_172.17.0.1041002';scope=DISTRIBUTED_NO_ACK';dataPolicy=REPLICATE]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7293)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6157)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroyRegion(DistributedRegion.java:1821)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6128)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroyRegion(LocalRegion.java:2251)
> at
> org.apache.geode.internal.cache.AbstractRegion.localDestroyRegion(AbstractRegion.java:452)
> at
> org.apache.geode.management.internal.FederatingManager.removeMemberArtifacts(FederatingManager.java:216)
> at
> org.apache.geode.management.internal.FederatingManager.access$000(FederatingManager.java:67)
> at
> org.apache.geode.management.internal.FederatingManager$RemoveMemberTask.run(FederatingManager.java:564)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> This failure has nothing to do with Lucene.
> Some analysis shows that stopping a member and stopping the locator nearly
> simultaneously can cause this RegionDestroyedException.
> The test output shows:
> The locator starts:
> {noformat}
> [vm0] [info 2019/10/07 21:17:55.174 GMT
> tid=0x22] Starting DistributionManager
> 172.17.0.10(locator-0:87:locator):41000. (took 26 ms)
> {noformat}
> Server1 starts and _monitoringRegion_172.17.0.1041001 is created for it
> in the locator:
> {noformat}
> [vm1] [info 2019/10/07 21:17:59.681 GMT
> tid=0x22] Starting DistributionManager 172.17.0.10(server-1:95):41001.
> (took 405 ms)
> [vm0] [info 2019/10/07 21:17:59.684 GMT tid=0x332]
> Initializing region _monitoringRegion_172.17.0.1041001
> [vm0] [info 2019/10/07 21:17:59.694 GMT tid=0x332]
> Initialization of region _monitoringRegion_172.17.0.1041001 completed
> {noformat}
> Server2 starts and _monitoringRegion_172.17.0.1041002 is created for it
> in the locator:
> {noformat}
> [vm2] [info 2019/10/07 21:18:00.379 GMT
> tid=0x22] Starting DistributionManager 172.17.0.10(server-2:104):41002.
> (took 361 ms)
> [vm0] [info 2019/10/07 21:18:00.379 GMT tid=0x33c]
> Initializing region _monitoringRegion_172.17.0.1041002
> [vm0] [info 2019/10/07 21:18:00.424 GMT tid=0x33c]
> Initialization of region _monitoringRegion_172.17.0.1041002 completed
> {noformat}
> Server2 shuts down:
> {noformat}
> [vm2] [info 2019/10/07 21:18:02.007 GMT
> tid=0x22] Shutting down DistributionManager
> 172.17.0.10(server-2:104):41002.
> [vm2] [info 2019/10/07 21:18:02.127 GMT
> tid=0x22] Marking DistributionManager 172.17.0.10(server-2:104):41002 as
> closed.
> {noformat}
> Server1 shuts down:
> {noformat}
> [vm1] [info 2019/10/07 21:18:02.189 GMT
> tid=0x22] Shutting down
[jira] [Commented] (GEODE-7277) CI failure: DestroyLuceneIndexCommandsDUnitTest > testDestroyIndexesWithOneIndexAndRegionInOneMember failed with RegionDestroyedException suspicious string
[
https://issues.apache.org/jira/browse/GEODE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949662#comment-16949662
]
ASF subversion and git services commented on GEODE-7277:
Commit 24360c69284cdac44fa85f654b6abd7010cbee6a in geode's branch
refs/heads/feature/GEODE-7277 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=24360c6 ]
GEODE-7277: need to wrap the local destroy region in try-catch
> CI failure: DestroyLuceneIndexCommandsDUnitTest >
> testDestroyIndexesWithOneIndexAndRegionInOneMember failed with
> RegionDestroyedException suspicious string
> ---
>
> Key: GEODE-7277
> URL: https://issues.apache.org/jira/browse/GEODE-7277
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Reporter: Barrett Oglesby
>Priority: Major
>
> DistributedTestOpenJDK11 #1147
> (https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1147)
> failed with this RegionDestroyedException suspicious string:
> {noformat}
> org.apache.geode.cache.lucene.internal.cli.DestroyLuceneIndexCommandsDUnitTest
> > testDestroyIndexesWithOneIndexAndRegionInOneMember FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2012
> [fatal 2019/10/07 21:18:02.334 GMT tid=845] Uncaught
> exception in thread Thread[FederatingManager4,5,RMI Runtime]
> org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/_monitoringRegion_172.17.0.1041002';scope=DISTRIBUTED_NO_ACK';dataPolicy=REPLICATE]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7293)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6157)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroyRegion(DistributedRegion.java:1821)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6128)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroyRegion(LocalRegion.java:2251)
> at
> org.apache.geode.internal.cache.AbstractRegion.localDestroyRegion(AbstractRegion.java:452)
> at
> org.apache.geode.management.internal.FederatingManager.removeMemberArtifacts(FederatingManager.java:216)
> at
> org.apache.geode.management.internal.FederatingManager.access$000(FederatingManager.java:67)
> at
> org.apache.geode.management.internal.FederatingManager$RemoveMemberTask.run(FederatingManager.java:564)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> This failure has nothing to do with Lucene.
> Some analysis shows that stopping a member and stopping the locator nearly
> simultaneously can cause this RegionDestroyedException.
> The test output shows:
> The locator starts:
> {noformat}
> [vm0] [info 2019/10/07 21:17:55.174 GMT
> tid=0x22] Starting DistributionManager
> 172.17.0.10(locator-0:87:locator):41000. (took 26 ms)
> {noformat}
> Server1 starts and _monitoringRegion_172.17.0.1041001 is created for it
> in the locator:
> {noformat}
> [vm1] [info 2019/10/07 21:17:59.681 GMT
> tid=0x22] Starting DistributionManager 172.17.0.10(server-1:95):41001.
> (took 405 ms)
> [vm0] [info 2019/10/07 21:17:59.684 GMT tid=0x332]
> Initializing region _monitoringRegion_172.17.0.1041001
> [vm0] [info 2019/10/07 21:17:59.694 GMT tid=0x332]
> Initialization of region _monitoringRegion_172.17.0.1041001 completed
> {noformat}
> Server2 starts and _monitoringRegion_172.17.0.1041002 is created for it
> in the locator:
> {noformat}
> [vm2] [info 2019/10/07 21:18:00.379 GMT
> tid=0x22] Starting DistributionManager 172.17.0.10(server-2:104):41002.
> (took 361 ms)
> [vm0] [info 2019/10/07 21:18:00.379 GMT tid=0x33c]
> Initializing region _monitoringRegion_172.17.0.1041002
> [vm0] [info 2019/10/07 21:18:00.424 GMT tid=0x33c]
> Initialization of region _monitoringRegion_172.17.0.1041002 completed
> {noformat}
> Server2 shuts down:
> {noformat}
> [vm2] [info 2019/10/07 21:18:02.007 GMT
> tid=0x22] Shutting down DistributionManager
> 172.17.0.10(server-2:104):41002.
> [vm2] [info 2019/10/07 21:18:02.127 GMT
> tid=0x22] Marking DistributionManager
[jira] [Commented] (GEODE-7189) CI Failure: ServerLauncherTest > startWaitsForStartupTasksToComplete failed
[
https://issues.apache.org/jira/browse/GEODE-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949659#comment-16949659
]
Aaron Lindsey commented on GEODE-7189:
--
Failed again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK11/builds/1158
> CI Failure: ServerLauncherTest > startWaitsForStartupTasksToComplete failed
> ---
>
> Key: GEODE-7189
> URL: https://issues.apache.org/jira/browse/GEODE-7189
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barrett Oglesby
>Priority: Major
>
> {noformat}
> org.apache.geode.distributed.ServerLauncherTest >
> startWaitsForStartupTasksToComplete FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.distributed.ServerLauncherTest that uses
> java.util.concurrent.CompletableFuture
> Wanted but not invoked:
> completableFuture.thenRun();
> -> at
> org.apache.geode.distributed.ServerLauncherTest.lambda$startWaitsForStartupTasksToComplete$14(ServerLauncherTest.java:428)
> Actually, there were zero interactions with this mock.
> within 300 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.distributed.ServerLauncherTest.startWaitsForStartupTasksToComplete(ServerLauncherTest.java:428)
> Caused by:
> Wanted but not invoked:
> completableFuture.thenRun();
> -> at
> org.apache.geode.distributed.ServerLauncherTest.lambda$startWaitsForStartupTasksToComplete$14(ServerLauncherTest.java:428)
> Actually, there were zero interactions with this mock.
> at
> org.apache.geode.distributed.ServerLauncherTest.lambda$startWaitsForStartupTasksToComplete$14(ServerLauncherTest.java:428)
> {noformat}
> UnitTestOpenJDK11 #943:
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/UnitTestOpenJDK11/builds/943
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0108/test-results/test/1568154432/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0108/test-artifacts/1568154432/unittestfiles-OpenJDK11-9.10.0-build.0108.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7280) Clarify docs: DELETE V1 endpoint only for replicated regions
[ https://issues.apache.org/jira/browse/GEODE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949613#comment-16949613 ] ASF subversion and git services commented on GEODE-7280: Commit eda23b4a23e472c759dc4738de564fd5375f3d4c in geode's branch refs/heads/feature/GEODE-3780 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=eda23b4 ] GEODE-7280 Clarify docs: DELETE V1 only for replicated regions (#4133) > Clarify docs: DELETE V1 endpoint only for replicated regions > > > Key: GEODE-7280 > URL: https://issues.apache.org/jira/browse/GEODE-7280 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Fix For: 1.11.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The DELETE REST endpoint for removing all entries only works for replicated > (not partitioned) regions. This should be explicit within the documentation. > Here are two places (in the Geode 1.10 docs) that should identify that > restriction: > * reference: > [https://geode.apache.org/docs/guide/110/rest_apps/delete_all_data.html] > * > [https://geode.apache.org/docs/guide/110/rest_apps/develop_rest_apps.html#topic_qhs_f25_m4], > in the subsection titled Deleting Region Data -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6987) Implement RegExMethodAuthorizer
[ https://issues.apache.org/jira/browse/GEODE-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949614#comment-16949614 ] ASF subversion and git services commented on GEODE-6987: Commit 915e119343aeae7bb7e99892a6c02196adde3cdb in geode's branch refs/heads/feature/GEODE-3780 from Juan José Ramos [ https://gitbox.apache.org/repos/asf?p=geode.git;h=915e119 ] GEODE-6987: Implement RegExMethodAuthorizer (#4123) - Made the class final, immutable and thread safe. - Added comprehensive javadocs to the class and its methods. - Added several unit tests for the class and all public methods. > Implement RegExMethodAuthorizer > --- > > Key: GEODE-6987 > URL: https://issues.apache.org/jira/browse/GEODE-6987 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Juan Ramos >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons > Fix For: 1.11.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Implement the [RegExMethodAuthorizer > |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-RegExMethodAuthorizer] > class. > * Make sure the class is immutable and thread safe. > * Implement unit tests for the class and all of its methods. > * Add comprehensive and clear documentation to the class and all its public > methods so customers can use it without leaving their IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-3780) suspected member is never watched again after passing final check
[ https://issues.apache.org/jira/browse/GEODE-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949618#comment-16949618 ] ASF subversion and git services commented on GEODE-3780: Commit e527d21d91b6f6b5c1b79a418256fdb9b48a45de in geode's branch refs/heads/feature/GEODE-3780 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e527d21 ] GEODE-3780 suspected member is never watched again after passing final check This restores our original behavior (pre-1.0) behavior of performing a final check on a member if UDP communications with that member fail. We now also send exonoration messages to all other members if a suspect is cleared. We need to do that because another member may have sent a Suspect message that was ignored because the suspect was already undergoing a final check. I also noticed that our tcp/ip final check loop was performing more than one check in many cases because the nanosecond clock has a coarse granularity. A socket so-timeout based on the millisecond clock was timing out but the nanosecond clock didn't line up with that timeout and caused the "for" loop to make another attempt. I changed that loop to convert the nanosecond clock value to milliseconds. > suspected member is never watched again after passing final check > - > > Key: GEODE-3780 > URL: https://issues.apache.org/jira/browse/GEODE-3780 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce J Schuchardt >Assignee: Bruce J Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > In a network-down test we saw a node on the losing side of the network > partition perform final checks on members on the winning side. One of the > final checks mysteriously succeeded > [info 2017/09/17 12:24:45.552 PDT > gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 Detection thread 4> tid=0x128] Final check failed but detected recent message > traffic for suspect member > 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135):1026 > [info 2017/09/17 12:24:45.552 PDT > gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 Detection thread 4> tid=0x128] Final check passed for suspect member > 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135):1026 > After this the suspected member was never checked again and the losing side > failed to shut down. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6992) Deprecate allowUntrustedMethodInvocation System Property
[
https://issues.apache.org/jira/browse/GEODE-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949611#comment-16949611
]
ASF subversion and git services commented on GEODE-6992:
Commit 49612dad4d279be1384c5b075399d30b5b329f00 in geode's branch
refs/heads/feature/GEODE-3780 from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=49612da ]
GEODE-6992: Deprecate allowUntrustedMethodInvocation (#4127)
- Added warning log when the property is specified.
- Deprecate the allowUntrustedMethodInvocation system property.
> Deprecate allowUntrustedMethodInvocation System Property
>
>
> Key: GEODE-6992
> URL: https://issues.apache.org/jira/browse/GEODE-6992
> Project: Geode
> Issue Type: New Feature
> Components: configuration
>Reporter: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.11.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Deprecate the system property
> {{gemfire.QueryService.allowUntrustedMethodInvocation}}.
> Register a {{warning}} message on the logs whenever the member detects that
> the property is being used so our users are aware of the deprecation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7151) Remove some not used test classes
[ https://issues.apache.org/jira/browse/GEODE-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949610#comment-16949610 ] ASF subversion and git services commented on GEODE-7151: Commit a653e50134f6356002cf13faf1fae981dc21857e in geode's branch refs/heads/feature/GEODE-3780 from Alberto Bustamante Reyes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a653e50 ] GEODE-7151: Remove some unused classes (#3995) > Remove some not used test classes > - > > Key: GEODE-7151 > URL: https://issues.apache.org/jira/browse/GEODE-7151 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Trivial > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following classes are not used and can be removed from the code: > * geode-core/src/test/java/com/examples/LinkNode.java > * geode-core/src/test/java/com/examples/SuperClass.java > * geode-core/src/test/java/com/examples/TestObject.java -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7268) Make gfsh alter region command similar to the API behavior
[ https://issues.apache.org/jira/browse/GEODE-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949615#comment-16949615 ] ASF subversion and git services commented on GEODE-7268: Commit 0be31dd0c3df469ab906a183ad64aa965d9f1d08 in geode's branch refs/heads/feature/GEODE-3780 from Naburun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0be31dd ] GEODE-7268: Remove bucket assignment in alter region gfsh command while adding gateways * Remove the assign buckets to the partition step in the alter region function to add gateway senders * This step is not present in the API version of altering region using mutators. * Keeping this also resulted in a soft hang while altering many regions by adding gateways senders. > Make gfsh alter region command similar to the API behavior > --- > > Key: GEODE-7268 > URL: https://issues.apache.org/jira/browse/GEODE-7268 > Project: Geode > Issue Type: Bug >Reporter: Nabarun Nag >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > * currently the gfsh command for alter region assigns the buckets to the > region, before starting with the PR update config. > * This is not what the API does while altering a region > * This was requirement from the Lucene reindex story but that feature > follows a different code path and will the be not affected if the assign > buckets command was removed from the gfsh command. > * This also results in soft hangs when there are a lot of regions and > gateway senders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7255) Need to pick up CVE-2019-16942
[ https://issues.apache.org/jira/browse/GEODE-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949612#comment-16949612 ] ASF subversion and git services commented on GEODE-7255: Commit 4d635aa59bde33351b2c03f7bee0ee642572a763 in geode's branch refs/heads/feature/GEODE-3780 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4d635aa ] GEODE-7255: Pickup Jackson CVE fix (#4102) > Need to pick up CVE-2019-16942 > -- > > Key: GEODE-7255 > URL: https://issues.apache.org/jira/browse/GEODE-7255 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Fix For: 1.11.0 > > Time Spent: 1h > Remaining Estimate: 0h > > There is a CVE out on Jackson versions before 2.10.0... We need to upgrade to > 2.10.0 to get a fix. > see CVE-2019-16942 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7177) Move membership's logging dependencies to its own module
[ https://issues.apache.org/jira/browse/GEODE-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949616#comment-16949616 ] ASF subversion and git services commented on GEODE-7177: Commit 5981a139a1acc078d2d3024ddcfaad35642d7684 in geode's branch refs/heads/feature/GEODE-3780 from Ernie Burghardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5981a13 ] GEODE-7177: Logging as a submodule (#4129) * GEODE-7177: Extract LogService to a separate submodule - Extracting LogService and it's dependencies to a separate geode-logging submodule so that other modules not in geode-core can still use LogService to get a Logger. - Removing the use of the logging SPI from LogService LogService had a dependency on the logging SPI in geode-core. However, this dependency was unecessary - the LoggingProvider loaded statically in this class never had `configure` called on it. In addition, the getLogger methods of this class are merely creating FastLoggers which can live inside geode-logging and do not need to be pluggable. - Moved executors that are not dependent on geode-core to geode-logging and renamed the remaining executors to be CoreLoggingExecutors. - Refactor the marker interface from Loggable to EntriesCollection - EntriesCollection put back into internal.cache and AbstractRegion now implements the marker - Formerly known as Loggable renamed to LogWithToString - Remove marker interface called EntriesCollection completely, replace with LogWithToString. > Move membership's logging dependencies to its own module > > > Key: GEODE-7177 > URL: https://issues.apache.org/jira/browse/GEODE-7177 > Project: Geode > Issue Type: Improvement > Components: logging, membership >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Time Spent: 5.5h > Remaining Estimate: 0h > > As part of eliminating membership's dependency on geode-core, we want to move > LogService and some other supporting classes to its own module which > membership can depend on. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7177) Move membership's logging dependencies to its own module
[ https://issues.apache.org/jira/browse/GEODE-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949617#comment-16949617 ] ASF subversion and git services commented on GEODE-7177: Commit 5981a139a1acc078d2d3024ddcfaad35642d7684 in geode's branch refs/heads/feature/GEODE-3780 from Ernie Burghardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5981a13 ] GEODE-7177: Logging as a submodule (#4129) * GEODE-7177: Extract LogService to a separate submodule - Extracting LogService and it's dependencies to a separate geode-logging submodule so that other modules not in geode-core can still use LogService to get a Logger. - Removing the use of the logging SPI from LogService LogService had a dependency on the logging SPI in geode-core. However, this dependency was unecessary - the LoggingProvider loaded statically in this class never had `configure` called on it. In addition, the getLogger methods of this class are merely creating FastLoggers which can live inside geode-logging and do not need to be pluggable. - Moved executors that are not dependent on geode-core to geode-logging and renamed the remaining executors to be CoreLoggingExecutors. - Refactor the marker interface from Loggable to EntriesCollection - EntriesCollection put back into internal.cache and AbstractRegion now implements the marker - Formerly known as Loggable renamed to LogWithToString - Remove marker interface called EntriesCollection completely, replace with LogWithToString. > Move membership's logging dependencies to its own module > > > Key: GEODE-7177 > URL: https://issues.apache.org/jira/browse/GEODE-7177 > Project: Geode > Issue Type: Improvement > Components: logging, membership >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Time Spent: 5.5h > Remaining Estimate: 0h > > As part of eliminating membership's dependency on geode-core, we want to move > LogService and some other supporting classes to its own module which > membership can depend on. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949609#comment-16949609
]
ASF subversion and git services commented on GEODE-7237:
Commit 3686b4358eb088ab8e9a8a498bbcd14729a838b9 in geode's branch
refs/heads/feature/GEODE-3780 from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3686b43 ]
GEODE-7237: Use invalid host name in ConnectCommandAcceptanceTest (#4128)
The test invalidHostname continues to fail intermittently. In the
failure, something fails to throw UnknownHostException. Having
spaces in the "invalid host name" should guarantee that it always
throws UnknownHostException now.
Also, remove the double negative from the assumeTrue by flipping it
to assumeFalse. Move the comment into the assumeFalse as a message.
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7270) WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY
[
https://issues.apache.org/jira/browse/GEODE-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaojian Zhou resolved GEODE-7270.
--
Fix Version/s: 1.11.0
Resolution: Fixed
> WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY
> ---
>
> Key: GEODE-7270
> URL: https://issues.apache.org/jira/browse/GEODE-7270
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY failed with a Null
> Pointer Exception.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1138]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-results/distributedTest/1570043011/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-artifacts/1570043011/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0174.tgz]
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest$$Lambda$172/1647741944.run
> in VM 0 running on Host 1cafba0ee536 with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.test_TK_Recognises_LN_AND_NY(WanAutoDiscoveryDUnitTest.java:228)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
>
[jira] [Commented] (GEODE-7270) WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY
[
https://issues.apache.org/jira/browse/GEODE-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949592#comment-16949592
]
ASF subversion and git services commented on GEODE-7270:
Commit eaf796661a341dadd226f5ffce4012dbda6a5883 in geode's branch
refs/heads/develop from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=eaf7966 ]
GEODE-7270: wait until expected sites are ready to make test stable (#4146)
> WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY
> ---
>
> Key: GEODE-7270
> URL: https://issues.apache.org/jira/browse/GEODE-7270
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Time Spent: 20m
> Remaining Estimate: 0h
>
> WanAutoDiscoveryDUnitTest. test_TK_Recognises_LN_AND_NY failed with a Null
> Pointer Exception.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1138]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-results/distributedTest/1570043011/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0174/test-artifacts/1570043011/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0174.tgz]
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest$$Lambda$172/1647741944.run
> in VM 0 running on Host 1cafba0ee536 with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.test_TK_Recognises_LN_AND_NY(WanAutoDiscoveryDUnitTest.java:228)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Assigned] (GEODE-7287) Add test case for REST function invocation with a filter
[ https://issues.apache.org/jira/browse/GEODE-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Gomez reassigned GEODE-7287: Assignee: Alberto Gomez > Add test case for REST function invocation with a filter > > > Key: GEODE-7287 > URL: https://issues.apache.org/jira/browse/GEODE-7287 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Fix For: 1.11.0 > > > There isn't an integration test for the REST function invocation in which a > filter is passed. > It would be nice to have one in the RestAccessControllerTest class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7287) Add test case for REST function invocation with a filter
Alberto Gomez created GEODE-7287: Summary: Add test case for REST function invocation with a filter Key: GEODE-7287 URL: https://issues.apache.org/jira/browse/GEODE-7287 Project: Geode Issue Type: Improvement Components: tests Reporter: Alberto Gomez Fix For: 1.11.0 There isn't an integration test for the REST function invocation in which a filter is passed. It would be nice to have one in the RestAccessControllerTest class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
