[jira] [Created] (GEODE-5100) CI Failure: WanCommandListDUnitTest fails intermittently with null pointer
Sai Boorlagadda created GEODE-5100:
--
Summary: CI Failure: WanCommandListDUnitTest fails intermittently
with null pointer
Key: GEODE-5100
URL: https://issues.apache.org/jira/browse/GEODE-5100
Project: Geode
Issue Type: New Feature
Components: gfsh
Reporter: Sai Boorlagadda
{noformat}
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 2783
[error 2018/04/18 00:26:03.706 UTC tid=92]
Could not execute "list gateways".
java.lang.NullPointerException
at java.util.Arrays.stream(Arrays.java:5004)
at
org.apache.geode.management.internal.cli.commands.ListGatewayCommand.accumulateListGatewayResult(ListGatewayCommand.java:153)
at
org.apache.geode.management.internal.cli.commands.ListGatewayCommand.listGateway(ListGatewayCommand.java:112)
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.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
at
org.apache.geode.management.internal.cli.remote.OnlineCommandProcessor.executeCommand(OnlineCommandProcessor.java:127)
at
org.apache.geode.management.internal.beans.MemberMBeanBridge.processCommand(MemberMBeanBridge.java:1514)
at
org.apache.geode.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:417)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
at
com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193)
at
com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175)
at
com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117)
at
com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54)
at
com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
at
javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
at
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
at
[jira] [Updated] (GEODE-5085) authentication failure when auto-reconnecting
[
https://issues.apache.org/jira/browse/GEODE-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Blum updated GEODE-5085:
-
Attachment: geode-server-context.xml
> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
> Issue Type: Bug
> Components: membership, security
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Labels: pull-request-available
> Attachments: geode-server-context.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum()
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT tid=92] Exception
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
> @Override
> public Properties getDistributedSystemProperties() {
> if (dsProperties == null) {
> dsProperties = new Properties();
> dsProperties.put(MAX_WAIT_TIME_RECONNECT, "2");
> dsProperties.put(ENABLE_NETWORK_PARTITION_DETECTION, "true");
> dsProperties.put(DISABLE_AUTO_RECONNECT, "false");
> dsProperties.put(ENABLE_CLUSTER_CONFIGURATION, "false");
> dsProperties.put(LOCATORS, "localHost[" + locatorPort + "]");
> dsProperties.put(MCAST_PORT, "0");
> dsProperties.put(MEMBER_TIMEOUT, "1000");
> dsProperties.put(LOG_LEVEL, LogWriterUtils.getDUnitLogLevel());
> dsProperties.put(SECURITY_MANAGER,
> SimpleSecurityManager.class.getName());
> dsProperties.put("security-username", "clusterManage");
>
[jira] [Reopened] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn reopened GEODE-5070: --- Assignee: Sai Boorlagadda > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5100) CI Failure: WanCommandListDUnitTest fails intermittently with null pointer
[
https://issues.apache.org/jira/browse/GEODE-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn updated GEODE-5100:
--
Labels: ci (was: )
> CI Failure: WanCommandListDUnitTest fails intermittently with null pointer
> --
>
> Key: GEODE-5100
> URL: https://issues.apache.org/jira/browse/GEODE-5100
> Project: Geode
> Issue Type: New Feature
> Components: gfsh
>Reporter: Sai Boorlagadda
>Priority: Major
> Labels: ci
>
> {noformat}
> 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 2783
> [error 2018/04/18 00:26:03.706 UTC
> tid=92] Could not execute "list gateways".
> java.lang.NullPointerException
> at java.util.Arrays.stream(Arrays.java:5004)
> at
> org.apache.geode.management.internal.cli.commands.ListGatewayCommand.accumulateListGatewayResult(ListGatewayCommand.java:153)
> at
> org.apache.geode.management.internal.cli.commands.ListGatewayCommand.listGateway(ListGatewayCommand.java:112)
> 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.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
> at
> org.apache.geode.management.internal.cli.remote.OnlineCommandProcessor.executeCommand(OnlineCommandProcessor.java:127)
> at
> org.apache.geode.management.internal.beans.MemberMBeanBridge.processCommand(MemberMBeanBridge.java:1514)
> at
> org.apache.geode.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:417)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
> at
> com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193)
> at
> com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175)
> at
> com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117)
> at
> com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54)
> at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
> at
[jira] [Resolved] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-5070. --- Resolution: Won't Do > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: gfsh >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442887#comment-16442887 ] Barbara Pruijn commented on GEODE-5070: --- Background info on this ticket: Spring data users may have cluster config turned off. The current implementation of the describe jdbc-connection and list jdbc-connections takes the jdbc info from a random server in the cluster and returns that info. This reason this ticket was created is that there is no way to get the jdbc info from a specific server. But, currently, there is no advised way to have different jdbc-connections on different servers in the cluster and there is no user need for doing this up to this point. Since we therefore assume that the jdbc-connections will be the same on all servers in a cluster, we will not be adding the --member param for now. Therefore, closing this ticket as "will not do". > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: gfsh >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442900#comment-16442900 ] Barbara Pruijn commented on GEODE-5070: --- Reopening the ticket. Because of refactoring work, the original code has been remove (implementation of jdbc-connection commands without --member option). Therefore, we cannot roll back. We need to leave the ticket open to program code to get the command back to the original state (pick configuration from random server) after the refactoring code. > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5101) Cmake Find Module for Geode Native Not Correct
Michael Martell created GEODE-5101: -- Summary: Cmake Find Module for Geode Native Not Correct Key: GEODE-5101 URL: https://issues.apache.org/jira/browse/GEODE-5101 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Martell FindGeodeNaitve.cmake is hardcoded to look for the geode-native install in an apache-geode subdirectory. This should not be hardcoded, but should look in the install folder. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5096) AddCacheServerProfile should throw an error when conflicting Lucene indexes are concurrently created
[ https://issues.apache.org/jira/browse/GEODE-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442935#comment-16442935 ] ASF subversion and git services commented on GEODE-5096: Commit cc798b9a4158c09661a7ff2a88d8491e9add3880 in geode's branch refs/heads/feature/GEODE-5096 from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=cc798b9 ] GEODE-5096: Added support to validate server cache profiles in the case of concurrent updates to region cache profiles. > AddCacheServerProfile should throw an error when conflicting Lucene indexes > are concurrently created > > > Key: GEODE-5096 > URL: https://issues.apache.org/jira/browse/GEODE-5096 > Project: Geode > Issue Type: New Feature > Components: lucene >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > > When two servers concurrently define a LuceneIndex, the addCacheServerProfile > should throw an error to avoid conflicting indexes being defined. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5093) Update packer script for dev image to use Dependencies instead of Depends
[ https://issues.apache.org/jira/browse/GEODE-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5093: -- Labels: pull-request-available (was: ) > Update packer script for dev image to use Dependencies instead of Depends > - > > Key: GEODE-5093 > URL: https://issues.apache.org/jira/browse/GEODE-5093 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > > > **We should** replace Depends > **Because** Dependencies repo is a much improved version of Depends. > **Notes** The install is just a zipfile that needs to be downloaded and > unzipped and is at [https://github.com/lucasg/Dependencies] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments
[ https://issues.apache.org/jira/browse/GEODE-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn updated GEODE-4955: -- Fix Version/s: 1.7.0 > Improve spotless -- Remove empty javadocs and block comments > > > Key: GEODE-4955 > URL: https://issues.apache.org/jira/browse/GEODE-4955 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Fix For: 1.7.0 > > > This should be executed after GEODE-4654, since the removal of javadoc stubs > may yield a now-empty javadoc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs
[
https://issues.apache.org/jira/browse/GEODE-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn updated GEODE-4954:
--
Fix Version/s: 1.7.0
> Improve spotless -- remove trivial javadoc stubs
>
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
> Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the
> javadoc itself. Javadoc stubs that do not include description of a given
> term is trivial, redundant, and should be removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5105) Move implementation details from ClusterConfigurationService interface to its implementation.
Patrick Rhomberg created GEODE-5105: --- Summary: Move implementation details from ClusterConfigurationService interface to its implementation. Key: GEODE-5105 URL: https://issues.apache.org/jira/browse/GEODE-5105 Project: Geode Issue Type: Bug Reporter: Patrick Rhomberg Unless there are plans to make multiple implementations of the ClusterConfigurationService (which I believe there are not), then it doesn't really fit to have default implementations in the interface. These implementation details should be returned to the InternalClusterConfigurationService class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5085) authentication failure when auto-reconnecting
[
https://issues.apache.org/jira/browse/GEODE-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-5085.
-
Resolution: Fixed
Fix Version/s: 1.7.0
> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
> Issue Type: Bug
> Components: membership, security
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Attachments: geode-server-context.xml
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum()
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT tid=92] Exception
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
> @Override
> public Properties getDistributedSystemProperties() {
> if (dsProperties == null) {
> dsProperties = new Properties();
> dsProperties.put(MAX_WAIT_TIME_RECONNECT, "2");
> dsProperties.put(ENABLE_NETWORK_PARTITION_DETECTION, "true");
> dsProperties.put(DISABLE_AUTO_RECONNECT, "false");
> dsProperties.put(ENABLE_CLUSTER_CONFIGURATION, "false");
> dsProperties.put(LOCATORS, "localHost[" + locatorPort + "]");
> dsProperties.put(MCAST_PORT, "0");
> dsProperties.put(MEMBER_TIMEOUT, "1000");
> dsProperties.put(LOG_LEVEL, LogWriterUtils.getDUnitLogLevel());
> dsProperties.put(SECURITY_MANAGER,
> SimpleSecurityManager.class.getName());
>
[jira] [Created] (GEODE-5107) CI Failure: WanValidationsDUnitTest.testSameParallelGatewaySenderIdAcrossColocatedPartitionedRegion failed with AssertionError
Barry Oglesby created GEODE-5107:
Summary: CI Failure:
WanValidationsDUnitTest.testSameParallelGatewaySenderIdAcrossColocatedPartitionedRegion
failed with AssertionError
Key: GEODE-5107
URL: https://issues.apache.org/jira/browse/GEODE-5107
Project: Geode
Issue Type: Bug
Components: wan
Reporter: Barry Oglesby
[https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/7]
{noformat}
org.apache.geode.internal.cache.wan.misc.WanValidationsDUnitTest >
testSameParallelGatewaySenderIdAcrossColocatedPartitionedRegion 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 1019
[error 2018/04/18 03:06:55.922 UTC tid=1581]
Unexpected exception during bucket recovery
java.lang.IllegalStateException: Region specified in 'colocated-with'
(testSameParallelGatewaySenderIdAcrossColocatedPartitionedRegion_PR1) for
region /testSameParallelGatewaySenderIdAcrossColocatedPartitionedRegion_PR2
does not exist. It should be created before setting 'colocated-with' attribute
for this region.
at
org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
at
org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
at
org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:134)
at
org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:114)
at
org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1596)
at
org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:61)
at
org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:134)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5106) CI Failure: ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5106:
--
Labels: pull-request-available (was: )
> CI Failure:
> ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation
> failed with AssertionError
> ---
>
> Key: GEODE-5106
> URL: https://issues.apache.org/jira/browse/GEODE-5106
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/282]
> {noformat}
> org.apache.geode.internal.cache.wan.offheap.ParallelWANConflationOffHeapDUnitTest
> > testParallelPropagationBatchConflation FAILED
> java.lang.AssertionError: Event in secondary queue should be 0 after
> dispatched expected:<0> but was:<11>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5085) authentication failure when auto-reconnecting
[
https://issues.apache.org/jira/browse/GEODE-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443207#comment-16443207
]
ASF subversion and git services commented on GEODE-5085:
Commit 08ec4af911baa9eaca05f2aaf5d021618734bfe1 in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=08ec4af ]
GEODE-5085 authentication failure when auto-reconnecting
Modified auto-reconnect to gather the security properties from the
DistributionConfig and to use the non-parsed values of properties
instead of the parsed versions.
Modified unit tests to gather the security properties and use the
non-parsed values when deciding whether to create a new distributed system.
Added a security manager to all of the ReconnectDUnitTest test cases.
This closes #1807
> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
> Issue Type: Bug
> Components: membership, security
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Labels: pull-request-available
> Attachments: geode-server-context.xml
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum()
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT tid=92] Exception
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
> @Override
> public Properties getDistributedSystemProperties() {
> if (dsProperties == null) {
> dsProperties = new
[jira] [Commented] (GEODE-5098) Integrate OWASP Dependency Check for known vulnerabilities
[
https://issues.apache.org/jira/browse/GEODE-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443210#comment-16443210
]
Anthony Baker commented on GEODE-5098:
--
This is a good suggestion. We can pretty easily integrate this into our CI
pipeline via \{{https://github.com/apache/geode/tree/develop/ci}}.
> Integrate OWASP Dependency Check for known vulnerabilities
> --
>
> Key: GEODE-5098
> URL: https://issues.apache.org/jira/browse/GEODE-5098
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Praveendra Singh
>Priority: Major
>
> Given the sensitivity of the Geode system, we would like to avoid any
> vulnerable dependencies sneaking into the final product. One way to be little
> defensive is to leverage OWASP Dependency-Check. There are paid services
> (e.g. Veracode) in the market however OWASP tool gives results which are very
> close to the commercial services.
> h2. OWASP Dependency-Check
> Dependency-Check is a utility that identifies project dependencies and checks
> if there are any known, publicly disclosed, vulnerabilities.
>
> ref: [https://www.owasp.org/index.php/OWASP_Dependency_Check]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5106) CI Failure: ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaojian zhou reassigned GEODE-5106:
Assignee: xiaojian zhou
> CI Failure:
> ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation
> failed with AssertionError
> ---
>
> Key: GEODE-5106
> URL: https://issues.apache.org/jira/browse/GEODE-5106
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: xiaojian zhou
>Priority: Major
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/282]
> {noformat}
> org.apache.geode.internal.cache.wan.offheap.ParallelWANConflationOffHeapDUnitTest
> > testParallelPropagationBatchConflation FAILED
> java.lang.AssertionError: Event in secondary queue should be 0 after
> dispatched expected:<0> but was:<11>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5106) CI Failure: ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation failed with AssertionError
Barry Oglesby created GEODE-5106:
Summary: CI Failure:
ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation
failed with AssertionError
Key: GEODE-5106
URL: https://issues.apache.org/jira/browse/GEODE-5106
Project: Geode
Issue Type: Bug
Components: wan
Reporter: Barry Oglesby
[https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/282]
{noformat}
org.apache.geode.internal.cache.wan.offheap.ParallelWANConflationOffHeapDUnitTest
> testParallelPropagationBatchConflation FAILED
java.lang.AssertionError: Event in secondary queue should be 0 after dispatched
expected:<0> but was:<11>
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5069) Reduce direct exposure of GfJsonObject from CommandResult
[ https://issues.apache.org/jira/browse/GEODE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-5069. --- Resolution: Fixed > Reduce direct exposure of GfJsonObject from CommandResult > - > > Key: GEODE-5069 > URL: https://issues.apache.org/jira/browse/GEODE-5069 > Project: Geode > Issue Type: Sub-task > Components: gfsh >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5069) Reduce direct exposure of GfJsonObject from CommandResult
[ https://issues.apache.org/jira/browse/GEODE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn updated GEODE-5069: -- Fix Version/s: 1.7.0 > Reduce direct exposure of GfJsonObject from CommandResult > - > > Key: GEODE-5069 > URL: https://issues.apache.org/jira/browse/GEODE-5069 > Project: Geode > Issue Type: Sub-task > Components: gfsh >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-925) CI failure: QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
[
https://issues.apache.org/jira/browse/GEODE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Kohlmeyer reassigned GEODE-925:
---
Assignee: Udo Kohlmeyer
> CI failure:
> QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch
> -
>
> Key: GEODE-925
> URL: https://issues.apache.org/jira/browse/GEODE-925
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Sai Boorlagadda
>Assignee: Udo Kohlmeyer
>Priority: Major
> Labels: CI, Flaky
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> Stacktrace
> junit.framework.AssertionFailedError: Thread did not terminate after 200 ms:
> Thread[run invoked on an instance of
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest$9,5,]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.test.dunit.DistributedTestCase.join(DistributedTestCase.java:1241)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndexWithIndexAndQueryFromCluaseMisMatch(QueryDataInconsistencyDUnitTest.java:386)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor235.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor234.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5106) CI Failure: ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443247#comment-16443247
]
ASF subversion and git services commented on GEODE-5106:
Commit 540473958388f8000b45faf6bf771d54df8a2dc5 in geode's branch
refs/heads/feature/GEODE-5106 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5404739 ]
GEODE-5106: when primary queue is drained, the PQRM maybe still on the way.
> CI Failure:
> ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation
> failed with AssertionError
> ---
>
> Key: GEODE-5106
> URL: https://issues.apache.org/jira/browse/GEODE-5106
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: xiaojian zhou
>Priority: Major
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/282]
> {noformat}
> org.apache.geode.internal.cache.wan.offheap.ParallelWANConflationOffHeapDUnitTest
> > testParallelPropagationBatchConflation FAILED
> java.lang.AssertionError: Event in secondary queue should be 0 after
> dispatched expected:<0> but was:<11>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5102) Execute Lucene Rolling Upgrade tests with REINDEX flag enabled
[ https://issues.apache.org/jira/browse/GEODE-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5102: -- Labels: pull-request-available (was: ) > Execute Lucene Rolling Upgrade tests with REINDEX flag enabled > -- > > Key: GEODE-5102 > URL: https://issues.apache.org/jira/browse/GEODE-5102 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > > The existing rolling upgrade tests must run with the reindex flag enabled to > see the behavior of the indexing without region code when the reindex code is > enabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5103) During rebalance, a client node may miss a transactional event
Eric Shu created GEODE-5103: --- Summary: During rebalance, a client node may miss a transactional event Key: GEODE-5103 URL: https://issues.apache.org/jira/browse/GEODE-5103 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu During rebalance, a new primary bucket could be created on another node while the original primary bucket become secondary in a short period of time. If a transaction occurs on the primary bucket node, TXCommitMessage will be sent to the secondary primary bucket node. There is a race that a event could be missed to be added to the subscription queue when the now secondary bucket is being removed to satisfy the redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5104) CI output git SHA when updating passing reference file.
[ https://issues.apache.org/jira/browse/GEODE-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443058#comment-16443058 ] ASF subversion and git services commented on GEODE-5104: Commit 0bc70cac7d91ff3cd9cb41fdcba2528acfcf4245 in geode's branch refs/heads/develop from [~dcavender] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0bc70ca ] Merge pull request #1819 from smgoller/GEODE-5104 GEODE-5104 - Output git SHA when updating passing reference file. > CI output git SHA when updating passing reference file. > --- > > Key: GEODE-5104 > URL: https://issues.apache.org/jira/browse/GEODE-5104 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When concourse updates the file indicating the SHA that has passed all tests, > print it out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5104) CI output git SHA when updating passing reference file.
[ https://issues.apache.org/jira/browse/GEODE-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443059#comment-16443059 ] ASF subversion and git services commented on GEODE-5104: Commit 0bc70cac7d91ff3cd9cb41fdcba2528acfcf4245 in geode's branch refs/heads/develop from [~dcavender] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0bc70ca ] Merge pull request #1819 from smgoller/GEODE-5104 GEODE-5104 - Output git SHA when updating passing reference file. > CI output git SHA when updating passing reference file. > --- > > Key: GEODE-5104 > URL: https://issues.apache.org/jira/browse/GEODE-5104 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When concourse updates the file indicating the SHA that has passed all tests, > print it out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5104) CI output git SHA when updating passing reference file.
[ https://issues.apache.org/jira/browse/GEODE-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443057#comment-16443057 ] ASF subversion and git services commented on GEODE-5104: Commit 779bc5c96de5d77866dbc99381ecf8c4ac4d8987 in geode's branch refs/heads/develop from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=779bc5c ] GEODE-5104 - Output git SHA when updating passing reference file. > CI output git SHA when updating passing reference file. > --- > > Key: GEODE-5104 > URL: https://issues.apache.org/jira/browse/GEODE-5104 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When concourse updates the file indicating the SHA that has passed all tests, > print it out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5104) CI output git SHA when updating passing reference file.
[ https://issues.apache.org/jira/browse/GEODE-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5104: -- Labels: pull-request-available (was: ) > CI output git SHA when updating passing reference file. > --- > > Key: GEODE-5104 > URL: https://issues.apache.org/jira/browse/GEODE-5104 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > When concourse updates the file indicating the SHA that has passed all tests, > print it out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5102) Execute Lucene Rolling Upgrade tests with REINDEX flag enabled
nabarun created GEODE-5102: -- Summary: Execute Lucene Rolling Upgrade tests with REINDEX flag enabled Key: GEODE-5102 URL: https://issues.apache.org/jira/browse/GEODE-5102 Project: Geode Issue Type: Bug Components: lucene Reporter: nabarun The existing rolling upgrade tests must run with the reindex flag enabled to see the behavior of the indexing without region code when the reindex code is enabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-5065) DataSerializerPropagationDUnitTest.testServerUpFirstClientLater is flaky
[ https://issues.apache.org/jira/browse/GEODE-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Galen O'Sullivan reopened GEODE-5065: - Assignee: Galen O'Sullivan (was: Brian Rowe) This just failed again. I'm going to bump up the timeout and hope it doesn't show up again. > DataSerializerPropagationDUnitTest.testServerUpFirstClientLater is flaky > > > Key: GEODE-5065 > URL: https://issues.apache.org/jira/browse/GEODE-5065 > Project: Geode > Issue Type: Bug >Reporter: Brian Rowe >Assignee: Galen O'Sullivan >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Test tests that value set on server is propagated to client, but doesn't wait > for queue to be processed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5104) CI output git SHA when updating passing reference file.
Sean Goller created GEODE-5104: -- Summary: CI output git SHA when updating passing reference file. Key: GEODE-5104 URL: https://issues.apache.org/jira/browse/GEODE-5104 Project: Geode Issue Type: Task Components: ci Reporter: Sean Goller When concourse updates the file indicating the SHA that has passed all tests, print it out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5055) CI failure: LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion
[ https://issues.apache.org/jira/browse/GEODE-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh reassigned GEODE-5055: -- Assignee: nabarun > CI failure: > LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion > - > > Key: GEODE-5055 > URL: https://issues.apache.org/jira/browse/GEODE-5055 > Project: Geode > Issue Type: Sub-task > Components: lucene >Reporter: Jason Huynh >Assignee: nabarun >Priority: Major > > This is related to changes for GEODE-3926. The roll is occuring but because > we added the new complete file, the new server is probably "reindexing" at > the moment. > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit > > luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion[from_v140] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit$$Lambda$27/1996438298.run > in VM 0 running on Host eada542bc38a with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > at > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResultInEachVM(LuceneSearchWithRollingUpgradeDUnit.java:678) > at > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.executeLuceneQueryWithServerRollOvers(LuceneSearchWithRollingUpgradeDUnit.java:572) > at > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion(LuceneSearchWithRollingUpgradeDUnit.java:134) > Caused by: > java.lang.reflect.InvocationTargetException > 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.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:661) > at > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.lambda$verifyLuceneQueryResultInEachVM$b83f705c$2(LuceneSearchWithRollingUpgradeDUnit.java:678) > Caused by: > > org.apache.geode.cache.lucene.internal.LuceneIndexCreationInProgressException: > Lucene Index creation in progress for bucket: 1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals
[ https://issues.apache.org/jira/browse/GEODE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443576#comment-16443576 ] ASF subversion and git services commented on GEODE-4624: Commit 2805dfa31c0e17b02117a2d9f19104244ab691e0 in geode's branch refs/heads/feature/GEODE-4624 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2805dfa ] GEODE-4624: add a stats to trace total event removed by PQRM > Add a new stat for AyncEventQueue/GatewaySender to track the processing of > queueRemovals > > > Key: GEODE-4624 > URL: https://issues.apache.org/jira/browse/GEODE-4624 > Project: Geode > Issue Type: Bug > Components: docs, wan >Affects Versions: 1.5.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: xiaojian zhou >Priority: Major > Fix For: 1.7.0 > > > We currently track the number of events queues, queue size and > eventsDistributed ... but we don't track the number of events removed via > queue removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5104) CI output git SHA when updating passing reference file.
[ https://issues.apache.org/jira/browse/GEODE-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443582#comment-16443582 ] ASF subversion and git services commented on GEODE-5104: Commit 0bc70cac7d91ff3cd9cb41fdcba2528acfcf4245 in geode's branch refs/heads/feature/GEODE-4624 from [~dcavender] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0bc70ca ] Merge pull request #1819 from smgoller/GEODE-5104 GEODE-5104 - Output git SHA when updating passing reference file. > CI output git SHA when updating passing reference file. > --- > > Key: GEODE-5104 > URL: https://issues.apache.org/jira/browse/GEODE-5104 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When concourse updates the file indicating the SHA that has passed all tests, > print it out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5085) authentication failure when auto-reconnecting
[
https://issues.apache.org/jira/browse/GEODE-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443583#comment-16443583
]
ASF subversion and git services commented on GEODE-5085:
Commit 08ec4af911baa9eaca05f2aaf5d021618734bfe1 in geode's branch
refs/heads/feature/GEODE-4624 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=08ec4af ]
GEODE-5085 authentication failure when auto-reconnecting
Modified auto-reconnect to gather the security properties from the
DistributionConfig and to use the non-parsed values of properties
instead of the parsed versions.
Modified unit tests to gather the security properties and use the
non-parsed values when deciding whether to create a new distributed system.
Added a security manager to all of the ReconnectDUnitTest test cases.
This closes #1807
> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
> Issue Type: Bug
> Components: membership, security
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Attachments: geode-server-context.xml
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum()
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT tid=92] Exception
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
> @Override
> public Properties getDistributedSystemProperties() {
> if (dsProperties ==
[jira] [Commented] (GEODE-5070) Support --member option for describe & list jdbc connector commands
[ https://issues.apache.org/jira/browse/GEODE-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443578#comment-16443578 ] ASF subversion and git services commented on GEODE-5070: Commit a881a790da13c698a38a735d471df0871b552a7b in geode's branch refs/heads/feature/GEODE-4624 from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a881a79 ] GEODE-5070: Support --member option for describe & list jdbc connecto… (#1798) When cluster configuration service is disabled user have to provide --member option in-order to describe and list connections and mappings. > Support --member option for describe & list jdbc connector commands > --- > > Key: GEODE-5070 > URL: https://issues.apache.org/jira/browse/GEODE-5070 > Project: Geode > Issue Type: New Feature > Components: gfsh >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When cluster configuration service is disabled user have to provide --member > option in-order to describe and list connections and mappings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5043) Protobuf server and client are sending multiple packets for a single request
[ https://issues.apache.org/jira/browse/GEODE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443585#comment-16443585 ] ASF subversion and git services commented on GEODE-5043: Commit c303d01e408bc903f8ff5ac54b551618a4c5e782 in geode's branch refs/heads/feature/GEODE-4624 from [~geodeintegration] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c303d01 ] GEODE-5043: Buffering protobuf output to avoid multiple packet sends (#1768) GEODE-5043: Buffering protobuf output to avoid multiple packet sends Based on the stats all protobuf requests and responses were being sent as two packets. Using a BufferedOutputStream to make sure we only send 1 packet > Protobuf server and client are sending multiple packets for a single request > > > Key: GEODE-5043 > URL: https://issues.apache.org/jira/browse/GEODE-5043 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > While doing some performance testing, we discovered that the protobuf client > and protobuf server are actually sending multiple packets per request and > response based on the the LinuxSystemStats.xmitPackets. The messages are > small enough they should fit in a single packet. > > Looking at the code, it looks like in both the client and the server we are > writing directly to socket.getOutputStream(). As soon as data is written to > that outputstream it could be sent to the the remote side. Wrapping that in > the BufferedOutputStream eleminates the duplicate packets and improves the > performance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5043) Protobuf server and client are sending multiple packets for a single request
[ https://issues.apache.org/jira/browse/GEODE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443584#comment-16443584 ] ASF subversion and git services commented on GEODE-5043: Commit c303d01e408bc903f8ff5ac54b551618a4c5e782 in geode's branch refs/heads/feature/GEODE-4624 from [~geodeintegration] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c303d01 ] GEODE-5043: Buffering protobuf output to avoid multiple packet sends (#1768) GEODE-5043: Buffering protobuf output to avoid multiple packet sends Based on the stats all protobuf requests and responses were being sent as two packets. Using a BufferedOutputStream to make sure we only send 1 packet > Protobuf server and client are sending multiple packets for a single request > > > Key: GEODE-5043 > URL: https://issues.apache.org/jira/browse/GEODE-5043 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > While doing some performance testing, we discovered that the protobuf client > and protobuf server are actually sending multiple packets per request and > response based on the the LinuxSystemStats.xmitPackets. The messages are > small enough they should fit in a single packet. > > Looking at the code, it looks like in both the client and the server we are > writing directly to socket.getOutputStream(). As soon as data is written to > that outputstream it could be sent to the the remote side. Wrapping that in > the BufferedOutputStream eleminates the duplicate packets and improves the > performance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals
[ https://issues.apache.org/jira/browse/GEODE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443587#comment-16443587 ] ASF subversion and git services commented on GEODE-4624: Commit 50dd0c34ea1f00821f0ac11ad8d3f60e77694c64 in geode's branch refs/heads/feature/GEODE-4624 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=50dd0c3 ] GEODE-4624: add a stats to trace total event removed by PQRM > Add a new stat for AyncEventQueue/GatewaySender to track the processing of > queueRemovals > > > Key: GEODE-4624 > URL: https://issues.apache.org/jira/browse/GEODE-4624 > Project: Geode > Issue Type: Bug > Components: docs, wan >Affects Versions: 1.5.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: xiaojian zhou >Priority: Major > Fix For: 1.7.0 > > > We currently track the number of events queues, queue size and > eventsDistributed ... but we don't track the number of events removed via > queue removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5104) CI output git SHA when updating passing reference file.
[ https://issues.apache.org/jira/browse/GEODE-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443580#comment-16443580 ] ASF subversion and git services commented on GEODE-5104: Commit 779bc5c96de5d77866dbc99381ecf8c4ac4d8987 in geode's branch refs/heads/feature/GEODE-4624 from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=779bc5c ] GEODE-5104 - Output git SHA when updating passing reference file. > CI output git SHA when updating passing reference file. > --- > > Key: GEODE-5104 > URL: https://issues.apache.org/jira/browse/GEODE-5104 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When concourse updates the file indicating the SHA that has passed all tests, > print it out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4838) ClassCastException when registering interest against a Partitioned Region in LonerDistributedSystem
[ https://issues.apache.org/jira/browse/GEODE-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443579#comment-16443579 ] ASF subversion and git services commented on GEODE-4838: Commit 6d3771d9a80d32fdfe2164e3150b46152b28a85e in geode's branch refs/heads/feature/GEODE-4624 from [~huynhja] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6d3771d ] GEODE-4838: Throw IllegalStateException when registerinterest on PR in loner (#1614) > ClassCastException when registering interest against a Partitioned Region in > LonerDistributedSystem > --- > > Key: GEODE-4838 > URL: https://issues.apache.org/jira/browse/GEODE-4838 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > This is not a valid use case but we do get a ClassCastException when > attempting to register interest on a Partitioned Region in a > LonerDistributedSystem (mcast-port=0 and no locator specified). > Instead we can detect this scenario and throw an IllegalStateException and a > better explanation/message > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5081) ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property when configuring the DEFAULT Pool
[
https://issues.apache.org/jira/browse/GEODE-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443577#comment-16443577
]
ASF subversion and git services commented on GEODE-5081:
Commit b9bb961aa28074aa5643550c684614df33b1f613 in geode's branch
refs/heads/feature/GEODE-4624 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9bb961 ]
GEODE-5081 ClientCacheFactory is missing the
setPoolSubscriptionTimeoutMultiplier()
Added the missing method & a test for it
This closes #1804
> ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property
> when configuring the DEFAULT Pool
> --
>
> Key: GEODE-5081
> URL: https://issues.apache.org/jira/browse/GEODE-5081
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: John Blum
>Assignee: Bruce Schuchardt
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Apache Geode 1.4 introduced the new {{subscriptionTimeoutMultiplier}}
> configuration property when
> [configuring|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/PoolFactory.html#setSubscriptionTimeoutMultiplier-int-]
> a _Pool_ with the {{o.a.g.cache.client.PoolFactory}} class. The
> configuration setting for {{subscriptionTimeoutMultiplier}} could be queried
> using the {{o.a.g.cache.client.Pool's}} [property
> accessor|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html#getSubscriptionTimeoutMultiplier--].
> However, this same _Pool_ configuration property was not properly added to
> the
> [{{o.a.g.cache.client.ClientCacheFactory}}|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/ClientCacheFactory.html]
> when configuring the "DEFAULT" _Pool_, i.e. there is no
> {{setPoolSubscriptionTimeoutMultiplier(:int)}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5104) CI output git SHA when updating passing reference file.
[ https://issues.apache.org/jira/browse/GEODE-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443581#comment-16443581 ] ASF subversion and git services commented on GEODE-5104: Commit 0bc70cac7d91ff3cd9cb41fdcba2528acfcf4245 in geode's branch refs/heads/feature/GEODE-4624 from [~dcavender] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0bc70ca ] Merge pull request #1819 from smgoller/GEODE-5104 GEODE-5104 - Output git SHA when updating passing reference file. > CI output git SHA when updating passing reference file. > --- > > Key: GEODE-5104 > URL: https://issues.apache.org/jira/browse/GEODE-5104 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When concourse updates the file indicating the SHA that has passed all tests, > print it out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5106) CI Failure: ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443586#comment-16443586
]
ASF subversion and git services commented on GEODE-5106:
Commit 62fbcf0ba4f55c32d632142f93f8f250fc24889a in geode's branch
refs/heads/feature/GEODE-4624 from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=62fbcf0 ]
GEODE-5106: when primary queue is drained, the PQRM maybe still on the way.
(#1820)
> CI Failure:
> ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation
> failed with AssertionError
> ---
>
> Key: GEODE-5106
> URL: https://issues.apache.org/jira/browse/GEODE-5106
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/282]
> {noformat}
> org.apache.geode.internal.cache.wan.offheap.ParallelWANConflationOffHeapDUnitTest
> > testParallelPropagationBatchConflation FAILED
> java.lang.AssertionError: Event in secondary queue should be 0 after
> dispatched expected:<0> but was:<11>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals
[ https://issues.apache.org/jira/browse/GEODE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443590#comment-16443590 ] ASF subversion and git services commented on GEODE-4624: Commit 77e90cb7d2ef3a626a55febc27deb1c2eb872b2a in geode's branch refs/heads/feature/GEODE-4624 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=77e90cb ] GEODE-4624: add a stats to trace total event removed by PQRM > Add a new stat for AyncEventQueue/GatewaySender to track the processing of > queueRemovals > > > Key: GEODE-4624 > URL: https://issues.apache.org/jira/browse/GEODE-4624 > Project: Geode > Issue Type: Bug > Components: docs, wan >Affects Versions: 1.5.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: xiaojian zhou >Priority: Major > Fix For: 1.7.0 > > > We currently track the number of events queues, queue size and > eventsDistributed ... but we don't track the number of events removed via > queue removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16443262#comment-16443262
]
Galen O'Sullivan commented on GEODE-3523:
-
I'm seeing the issue again.
https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/1
Full stack trace:
{noformat}
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest$3.call in
VM 2 running on Host ad250661093a with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
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)
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.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
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
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
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
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
[jira] [Commented] (GEODE-5043) Protobuf server and client are sending multiple packets for a single request
[ https://issues.apache.org/jira/browse/GEODE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443303#comment-16443303 ] ASF subversion and git services commented on GEODE-5043: Commit c303d01e408bc903f8ff5ac54b551618a4c5e782 in geode's branch refs/heads/develop from [~geodeintegration] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c303d01 ] GEODE-5043: Buffering protobuf output to avoid multiple packet sends (#1768) GEODE-5043: Buffering protobuf output to avoid multiple packet sends Based on the stats all protobuf requests and responses were being sent as two packets. Using a BufferedOutputStream to make sure we only send 1 packet > Protobuf server and client are sending multiple packets for a single request > > > Key: GEODE-5043 > URL: https://issues.apache.org/jira/browse/GEODE-5043 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > While doing some performance testing, we discovered that the protobuf client > and protobuf server are actually sending multiple packets per request and > response based on the the LinuxSystemStats.xmitPackets. The messages are > small enough they should fit in a single packet. > > Looking at the code, it looks like in both the client and the server we are > writing directly to socket.getOutputStream(). As soon as data is written to > that outputstream it could be sent to the the remote side. Wrapping that in > the BufferedOutputStream eleminates the duplicate packets and improves the > performance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-5108) Geode examples should only run gradle tasks
[ https://issues.apache.org/jira/browse/GEODE-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443382#comment-16443382 ] Karen Smoler Miller edited comment on GEODE-5108 at 4/19/18 12:25 AM: -- Examples that should change: - async - eviction - expiration - functions - indexes - listener - loader - persistence - putall - serialization - transaction - writer was (Author: karensmolermiller): Examples that should change: - async - eviction - expiration - functions - indexes -listener - loader - persistence - putall - serialization - transaction - writer > Geode examples should only run gradle tasks > --- > > Key: GEODE-5108 > URL: https://issues.apache.org/jira/browse/GEODE-5108 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Karen Smoler Miller >Priority: Major > > Some of the Geode examples have instructions that have the user invoke gfsh > commands instead of gradle tasks. This is likely to lead to frustration on > the part of the person running an example, as which gfsh is picked up bound > to be wrong, or not anywhere within the person's PATH. > There's an easy fix for this, because gradle sets the path to the correct > gfsh. Change any Geode example's instruction that says > $ gfsh run --file=scripts/start.gfsh > to instead be > $ ../gradlew start > And, change any Geode example's instruction that says > $ gfsh run --file=scripts/stop.gfsh > to instead be > $ ../gradlew stop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5108) Geode examples should only run gradle tasks
[ https://issues.apache.org/jira/browse/GEODE-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443382#comment-16443382 ] Karen Smoler Miller commented on GEODE-5108: Examples that should change: - async - eviction - expiration - functions - indexes -listener - loader - persistence - putall - serialization - transaction - writer > Geode examples should only run gradle tasks > --- > > Key: GEODE-5108 > URL: https://issues.apache.org/jira/browse/GEODE-5108 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Karen Smoler Miller >Priority: Major > > Some of the Geode examples have instructions that have the user invoke gfsh > commands instead of gradle tasks. This is likely to lead to frustration on > the part of the person running an example, as which gfsh is picked up bound > to be wrong, or not anywhere within the person's PATH. > There's an easy fix for this, because gradle sets the path to the correct > gfsh. Change any Geode example's instruction that says > $ gfsh run --file=scripts/start.gfsh > to instead be > $ ../gradlew start > And, change any Geode example's instruction that says > $ gfsh run --file=scripts/stop.gfsh > to instead be > $ ../gradlew stop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5043) Protobuf server and client are sending multiple packets for a single request
[ https://issues.apache.org/jira/browse/GEODE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443302#comment-16443302 ] ASF subversion and git services commented on GEODE-5043: Commit c303d01e408bc903f8ff5ac54b551618a4c5e782 in geode's branch refs/heads/develop from [~geodeintegration] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c303d01 ] GEODE-5043: Buffering protobuf output to avoid multiple packet sends (#1768) GEODE-5043: Buffering protobuf output to avoid multiple packet sends Based on the stats all protobuf requests and responses were being sent as two packets. Using a BufferedOutputStream to make sure we only send 1 packet > Protobuf server and client are sending multiple packets for a single request > > > Key: GEODE-5043 > URL: https://issues.apache.org/jira/browse/GEODE-5043 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > While doing some performance testing, we discovered that the protobuf client > and protobuf server are actually sending multiple packets per request and > response based on the the LinuxSystemStats.xmitPackets. The messages are > small enough they should fit in a single packet. > > Looking at the code, it looks like in both the client and the server we are > writing directly to socket.getOutputStream(). As soon as data is written to > that outputstream it could be sent to the the remote side. Wrapping that in > the BufferedOutputStream eleminates the duplicate packets and improves the > performance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5043) Protobuf server and client are sending multiple packets for a single request
[ https://issues.apache.org/jira/browse/GEODE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5043: - Fix Version/s: 1.7.0 > Protobuf server and client are sending multiple packets for a single request > > > Key: GEODE-5043 > URL: https://issues.apache.org/jira/browse/GEODE-5043 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > While doing some performance testing, we discovered that the protobuf client > and protobuf server are actually sending multiple packets per request and > response based on the the LinuxSystemStats.xmitPackets. The messages are > small enough they should fit in a single packet. > > Looking at the code, it looks like in both the client and the server we are > writing directly to socket.getOutputStream(). As soon as data is written to > that outputstream it could be sent to the the remote side. Wrapping that in > the BufferedOutputStream eleminates the duplicate packets and improves the > performance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5043) Protobuf server and client are sending multiple packets for a single request
[ https://issues.apache.org/jira/browse/GEODE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5043. -- Resolution: Fixed > Protobuf server and client are sending multiple packets for a single request > > > Key: GEODE-5043 > URL: https://issues.apache.org/jira/browse/GEODE-5043 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > While doing some performance testing, we discovered that the protobuf client > and protobuf server are actually sending multiple packets per request and > response based on the the LinuxSystemStats.xmitPackets. The messages are > small enough they should fit in a single packet. > > Looking at the code, it looks like in both the client and the server we are > writing directly to socket.getOutputStream(). As soon as data is written to > that outputstream it could be sent to the the remote side. Wrapping that in > the BufferedOutputStream eleminates the duplicate packets and improves the > performance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443354#comment-16443354 ] ASF subversion and git services commented on GEODE-5103: Commit b4a315e92cf024c2c9beabf982d515f472786187 in geode's branch refs/heads/feature/GEODE-5103 from [~eshu] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b4a315e ] GEODE-5103: When applying transactional update on a replicate, callbacks should be alwasy generated. Currently callbacks is not generated if a region entry is null possibly caused by rebalance etc. We still want the node to generate callbacks for its clients. > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5108) Geode examples should only run gradle tasks
Karen Smoler Miller created GEODE-5108: -- Summary: Geode examples should only run gradle tasks Key: GEODE-5108 URL: https://issues.apache.org/jira/browse/GEODE-5108 Project: Geode Issue Type: Improvement Components: examples Reporter: Karen Smoler Miller Some of the Geode examples have instructions that have the user invoke gfsh commands instead of gradle tasks. This is likely to lead to frustration on the part of the person running an example, as which gfsh is picked up bound to be wrong, or not anywhere within the person's PATH. There's an easy fix for this, because gradle sets the path to the correct gfsh. Change any Geode example's instruction that says $ gfsh run --file=scripts/start.gfsh to instead be $ ../gradlew start And, change any Geode example's instruction that says $ gfsh run --file=scripts/stop.gfsh to instead be $ ../gradlew stop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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 ] Galen O'Sullivan reassigned GEODE-3523: --- Assignee: Addison > 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 >Assignee: Addison >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] [Resolved] (GEODE-5106) CI Failure: ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaojian zhou resolved GEODE-5106.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> CI Failure:
> ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation
> failed with AssertionError
> ---
>
> Key: GEODE-5106
> URL: https://issues.apache.org/jira/browse/GEODE-5106
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/282]
> {noformat}
> org.apache.geode.internal.cache.wan.offheap.ParallelWANConflationOffHeapDUnitTest
> > testParallelPropagationBatchConflation FAILED
> java.lang.AssertionError: Event in secondary queue should be 0 after
> dispatched expected:<0> but was:<11>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5105) Move implementation details from ClusterConfigurationService interface to its implementation.
[ https://issues.apache.org/jira/browse/GEODE-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5105: -- Labels: pull-request-available (was: ) > Move implementation details from ClusterConfigurationService interface to its > implementation. > - > > Key: GEODE-5105 > URL: https://issues.apache.org/jira/browse/GEODE-5105 > Project: Geode > Issue Type: Bug >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > > Unless there are plans to make multiple implementations of the > ClusterConfigurationService (which I believe there are not), then it doesn't > really fit to have default implementations in the interface. These > implementation details should be returned to the > InternalClusterConfigurationService class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5106) CI Failure: ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443312#comment-16443312
]
ASF subversion and git services commented on GEODE-5106:
Commit 62fbcf0ba4f55c32d632142f93f8f250fc24889a in geode's branch
refs/heads/develop from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=62fbcf0 ]
GEODE-5106: when primary queue is drained, the PQRM maybe still on the way.
(#1820)
> CI Failure:
> ParallelWANConflationOffHeapDUnitTest.testParallelPropagationBatchConflation
> failed with AssertionError
> ---
>
> Key: GEODE-5106
> URL: https://issues.apache.org/jira/browse/GEODE-5106
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/282]
> {noformat}
> org.apache.geode.internal.cache.wan.offheap.ParallelWANConflationOffHeapDUnitTest
> > testParallelPropagationBatchConflation FAILED
> java.lang.AssertionError: Event in secondary queue should be 0 after
> dispatched expected:<0> but was:<11>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5103: --- Assignee: Eric Shu > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5103) During rebalance, a client node may miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5103: -- Labels: pull-request-available (was: ) > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5109) Concurrent create lucene reindex ops must fail
nabarun created GEODE-5109: -- Summary: Concurrent create lucene reindex ops must fail Key: GEODE-5109 URL: https://issues.apache.org/jira/browse/GEODE-5109 Project: Geode Issue Type: Bug Components: lucene Reporter: nabarun Concurrent lucene reindex ops originating with same index profile must fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
