[jira] [Assigned] (GEODE-1507) gfsh variable substitution does not work
[
https://issues.apache.org/jira/browse/GEODE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella reassigned GEODE-1507:
---
Assignee: Juan José Ramos Cassella
> gfsh variable substitution does not work
>
>
> Key: GEODE-1507
> URL: https://issues.apache.org/jira/browse/GEODE-1507
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Juan José Ramos Cassella
>Priority: Major
>
> {noformat}
> gfsh>set variable --name=foo --value=bar
> Value for variable foo is now: bar.
> gfsh>echo --string="Hello ${foo}"
> Hello ${foo}
> {noformat}
> The problem has come in with spring-shell and jline replacement.
> {{Gfsh.executeCommand}} was replaced with {{Gfsh.executeScriptLine}} which
> ends up never being called unless a script is executed with {{run --file}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-3635) Echo command does not behave as documented
[
https://issues.apache.org/jira/browse/GEODE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella reassigned GEODE-3635:
---
Assignee: (was: Juan José Ramos Cassella)
> Echo command does not behave as documented
> --
>
> Key: GEODE-3635
> URL: https://issues.apache.org/jira/browse/GEODE-3635
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
>Reporter: Patrick Rhomberg
>Priority: Major
>
> The Set Variable command does appear to set gfsh environment properties, but
> these values are only accessible by Java methods that use them. They do not
> parse in the bash style. For instance:
> {noformat}
> gfsh> set variable --name=FOO --value=bar
> Value for variable FOO is now: bar.
> gfsh> echo --string=${FOO}
> ${FOO}
> {noformat}
> Examining the implementation, there is an explicit special case of
> {noformat}
> gfsh> echo --string=$*
> {noformat}
> which will describe the current gfsh environment. Rather than this special
> case, this may be better suited to a Describe Environment command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-3635) Echo command does not behave as documented
[
https://issues.apache.org/jira/browse/GEODE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella reassigned GEODE-3635:
---
Assignee: Juan José Ramos Cassella
> Echo command does not behave as documented
> --
>
> Key: GEODE-3635
> URL: https://issues.apache.org/jira/browse/GEODE-3635
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
>Reporter: Patrick Rhomberg
>Assignee: Juan José Ramos Cassella
>Priority: Major
>
> The Set Variable command does appear to set gfsh environment properties, but
> these values are only accessible by Java methods that use them. They do not
> parse in the bash style. For instance:
> {noformat}
> gfsh> set variable --name=FOO --value=bar
> Value for variable FOO is now: bar.
> gfsh> echo --string=${FOO}
> ${FOO}
> {noformat}
> Examining the implementation, there is an explicit special case of
> {noformat}
> gfsh> echo --string=$*
> {noformat}
> which will describe the current gfsh environment. Rather than this special
> case, this may be better suited to a Describe Environment command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5531) gfsh echo variable does not work as documented
[
https://issues.apache.org/jira/browse/GEODE-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5531:
--
Labels: pull-request-available (was: )
> gfsh echo variable does not work as documented
> --
>
> Key: GEODE-5531
> URL: https://issues.apache.org/jira/browse/GEODE-5531
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Derek Williams
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: pull-request-available
>
> Variables are [documented
> here|http://geode.apache.org/docs/guide/16/tools_modules/gfsh/useful_gfsh_shell_variables.html]
> to work with gfsh echo, but do not. This applies to both pre-defined shell
> variables and user-defined variables (set variable...).
> For example,
> {code}
> echo --string=$*
> {code}
> will show all shell variables and values, but
> {code}
> echo --string=${SYS_USER}
> {code}
> simply displays ${SYS_USER}
> Indeed,
> [EchoCommand.java|https://github.com/apache/geode/blob/78dcf4b8fa86543e882365e78f1c8e2a623bffde/geode-core/src/main/java/org/apache/geode/management/internal/cli/commands/EchoCommand.java]
> has a special case for `$*`, but does not include the other documented cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-1507) gfsh variable substitution does not work
[
https://issues.apache.org/jira/browse/GEODE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella closed GEODE-1507.
---
The work is done on GEODE-5531.
> gfsh variable substitution does not work
>
>
> Key: GEODE-1507
> URL: https://issues.apache.org/jira/browse/GEODE-1507
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Juan José Ramos Cassella
>Priority: Major
>
> {noformat}
> gfsh>set variable --name=foo --value=bar
> Value for variable foo is now: bar.
> gfsh>echo --string="Hello ${foo}"
> Hello ${foo}
> {noformat}
> The problem has come in with spring-shell and jline replacement.
> {{Gfsh.executeCommand}} was replaced with {{Gfsh.executeScriptLine}} which
> ends up never being called unless a script is executed with {{run --file}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-1507) gfsh variable substitution does not work
[
https://issues.apache.org/jira/browse/GEODE-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella resolved GEODE-1507.
-
Resolution: Duplicate
Duplicate.
> gfsh variable substitution does not work
>
>
> Key: GEODE-1507
> URL: https://issues.apache.org/jira/browse/GEODE-1507
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Juan José Ramos Cassella
>Priority: Major
>
> {noformat}
> gfsh>set variable --name=foo --value=bar
> Value for variable foo is now: bar.
> gfsh>echo --string="Hello ${foo}"
> Hello ${foo}
> {noformat}
> The problem has come in with spring-shell and jline replacement.
> {{Gfsh.executeCommand}} was replaced with {{Gfsh.executeScriptLine}} which
> ends up never being called unless a script is executed with {{run --file}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5549) Flaky test NonBlockingProcessStreamReaderIntegrationTest > processTerminatesWhenDestroyed
Jacob S. Barrett created GEODE-5549:
---
Summary: Flaky test NonBlockingProcessStreamReaderIntegrationTest
> processTerminatesWhenDestroyed
Key: GEODE-5549
URL: https://issues.apache.org/jira/browse/GEODE-5549
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Jacob S. Barrett
{noformat}
> Task :geode-core:integrationTest
org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
> processTerminatesWhenDestroyed FAILED
java.lang.AssertionError:
Expecting:
<0>
to be greater than:
<0>
{noformat}
Failed:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/237
Passed:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/236
Passed:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/235
Failed:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/234
Failing intermittently on pr pipeline as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5549) Flaky test NonBlockingProcessStreamReaderIntegrationTest > processTerminatesWhenDestroyed
[
https://issues.apache.org/jira/browse/GEODE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5549:
Affects Version/s: 1.8.0
> Flaky test NonBlockingProcessStreamReaderIntegrationTest >
> processTerminatesWhenDestroyed
> -
>
> Key: GEODE-5549
> URL: https://issues.apache.org/jira/browse/GEODE-5549
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
> > processTerminatesWhenDestroyed FAILED
> java.lang.AssertionError:
> Expecting:
> <0>
> to be greater than:
> <0>
> {noformat}
> Failed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/237
> Passed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/236
> Passed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/235
> Failed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/234
> Failing intermittently on pr pipeline as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5549) Flaky test NonBlockingProcessStreamReaderIntegrationTest > processTerminatesWhenDestroyed
[
https://issues.apache.org/jira/browse/GEODE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5549:
Labels: flaky swat (was: )
> Flaky test NonBlockingProcessStreamReaderIntegrationTest >
> processTerminatesWhenDestroyed
> -
>
> Key: GEODE-5549
> URL: https://issues.apache.org/jira/browse/GEODE-5549
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
> > processTerminatesWhenDestroyed FAILED
> java.lang.AssertionError:
> Expecting:
> <0>
> to be greater than:
> <0>
> {noformat}
> Failed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/237
> Passed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/236
> Passed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/235
> Failed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/234
> Failing intermittently on pr pipeline as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5550) Flaky test ShorteningExpirationTimeRegressionTest > customEntryTimeToLiveCanBeShortened
Jacob S. Barrett created GEODE-5550:
---
Summary: Flaky test ShorteningExpirationTimeRegressionTest >
customEntryTimeToLiveCanBeShortened
Key: GEODE-5550
URL: https://issues.apache.org/jira/browse/GEODE-5550
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Jacob S. Barrett
{noformat}
> Task :geode-core:integrationTest
org.apache.geode.cache30.ShorteningExpirationTimeRegressionTest >
customEntryTimeToLiveCanBeShortened FAILED
org.junit.ComparisonFailure: expected:<"quickExpire"> but was:
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.cache30.ShorteningExpirationTimeRegressionTest.customEntryTimeToLiveCanBeShortened(ShorteningExpirationTimeRegressionTest.java:100)
{noformat}
Failing:
https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/IntegrationTest/builds/531
Passing:
https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/IntegrationTest/builds/530
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5550) Flaky test ShorteningExpirationTimeRegressionTest > customEntryTimeToLiveCanBeShortened
[
https://issues.apache.org/jira/browse/GEODE-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5550:
Labels: flaky swat (was: )
> Flaky test ShorteningExpirationTimeRegressionTest >
> customEntryTimeToLiveCanBeShortened
> ---
>
> Key: GEODE-5550
> URL: https://issues.apache.org/jira/browse/GEODE-5550
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.cache30.ShorteningExpirationTimeRegressionTest >
> customEntryTimeToLiveCanBeShortened FAILED
> org.junit.ComparisonFailure: expected:<"quickExpire"> but was:
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.cache30.ShorteningExpirationTimeRegressionTest.customEntryTimeToLiveCanBeShortened(ShorteningExpirationTimeRegressionTest.java:100)
> {noformat}
> Failing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/IntegrationTest/builds/531
> Passing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/IntegrationTest/builds/530
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5550) Flaky test ShorteningExpirationTimeRegressionTest > customEntryTimeToLiveCanBeShortened
[
https://issues.apache.org/jira/browse/GEODE-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5550:
Affects Version/s: 1.8.0
> Flaky test ShorteningExpirationTimeRegressionTest >
> customEntryTimeToLiveCanBeShortened
> ---
>
> Key: GEODE-5550
> URL: https://issues.apache.org/jira/browse/GEODE-5550
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.cache30.ShorteningExpirationTimeRegressionTest >
> customEntryTimeToLiveCanBeShortened FAILED
> org.junit.ComparisonFailure: expected:<"quickExpire"> but was:
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.cache30.ShorteningExpirationTimeRegressionTest.customEntryTimeToLiveCanBeShortened(ShorteningExpirationTimeRegressionTest.java:100)
> {noformat}
> Failing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/IntegrationTest/builds/531
> Passing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/IntegrationTest/builds/530
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5551) Flaky test LoginHandlerInterceptorJUnitTest > testHandlerInterceptorThreadSafety
Jacob S. Barrett created GEODE-5551:
---
Summary: Flaky test LoginHandlerInterceptorJUnitTest >
testHandlerInterceptorThreadSafety
Key: GEODE-5551
URL: https://issues.apache.org/jira/browse/GEODE-5551
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Jacob S. Barrett
{noformat}
> Task :geode-web:test
org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest
> testHandlerInterceptorThreadSafety FAILED
junit.framework.AssertionFailedError: expected:<0> but was:<3>
not all expectations were satisfied
expectations:
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameterNames();
returns
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-username");
returns "admin"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-password");
returns "password"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.STAGE");
returns "test"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.GEODE_HOME");
returns "/path/to/gemfire/700"
expected once, already invoked 1 time: securityService.login(not null);
returns a default value
expected once, already invoked 1 time: securityService.logout()
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames();
returns
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username");
returns "admin"
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-password");
returns "password"
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.HOST");
returns "localhost"
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.GEODE_HOME");
returns "/path/to/gemfire/75"
! expected once, never invoked: securityService.login(not null); returns
a default value
! expected once, never invoked: securityService.logout()
what happened before this:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames()
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.HOST")
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.GEODE_HOME")
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username")
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-password")
securityService.login(<{security-username=admin,
security-password=password}>)
securityService.logout()
at
org.jmock.api.ExpectationError.notAllSatisfied(ExpectationError.java:27)
at org.jmock.Mockery.assertIsSatisfied(Mockery.java:213)
at
org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest.tearDown(LoginHandlerInterceptorJUnitTest.java:70)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5551) Flaky test LoginHandlerInterceptorJUnitTest > testHandlerInterceptorThreadSafety
[
https://issues.apache.org/jira/browse/GEODE-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5551:
Labels: flaky swat (was: )
> Flaky test LoginHandlerInterceptorJUnitTest >
> testHandlerInterceptorThreadSafety
>
>
> Key: GEODE-5551
> URL: https://issues.apache.org/jira/browse/GEODE-5551
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> > Task :geode-web:test
> org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest
> > testHandlerInterceptorThreadSafety FAILED
> junit.framework.AssertionFailedError: expected:<0> but was:<3>
> not all expectations were satisfied
> expectations:
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameterNames();
> returns
>
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-username");
> returns "admin"
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-password");
> returns "password"
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.STAGE");
> returns "test"
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.GEODE_HOME");
> returns "/path/to/gemfire/700"
> expected once, already invoked 1 time: securityService.login(not null);
> returns a default value
> expected once, already invoked 1 time: securityService.logout()
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames();
> returns
>
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username");
> returns "admin"
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-password");
> returns "password"
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.HOST");
> returns "localhost"
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.GEODE_HOME");
> returns "/path/to/gemfire/75"
> ! expected once, never invoked: securityService.login(not null);
> returns a default value
> ! expected once, never invoked: securityService.logout()
> what happened before this:
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames()
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.HOST")
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.GEODE_HOME")
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username")
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-password")
> securityService.login(<{security-username=admin,
> security-password=password}>)
> securityService.logout()
> at
> org.jmock.api.ExpectationError.notAllSatisfied(ExpectationError.java:27)
> at org.jmock.Mockery.assertIsSatisfied(Mockery.java:213)
> at
> org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest.tearDown(LoginHandlerInterceptorJUnitTest.java:70)
> {noformat}
> Failing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/Build/builds/558
> Passing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/Build/builds/559
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5551) Flaky test LoginHandlerInterceptorJUnitTest > testHandlerInterceptorThreadSafety
[
https://issues.apache.org/jira/browse/GEODE-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5551:
Affects Version/s: 1.8.0
> Flaky test LoginHandlerInterceptorJUnitTest >
> testHandlerInterceptorThreadSafety
>
>
> Key: GEODE-5551
> URL: https://issues.apache.org/jira/browse/GEODE-5551
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> > Task :geode-web:test
> org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest
> > testHandlerInterceptorThreadSafety FAILED
> junit.framework.AssertionFailedError: expected:<0> but was:<3>
> not all expectations were satisfied
> expectations:
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameterNames();
> returns
>
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-username");
> returns "admin"
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-password");
> returns "password"
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.STAGE");
> returns "test"
> ! expected once, never invoked:
> testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.GEODE_HOME");
> returns "/path/to/gemfire/700"
> expected once, already invoked 1 time: securityService.login(not null);
> returns a default value
> expected once, already invoked 1 time: securityService.logout()
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames();
> returns
>
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username");
> returns "admin"
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-password");
> returns "password"
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.HOST");
> returns "localhost"
> expected once, already invoked 1 time:
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.GEODE_HOME");
> returns "/path/to/gemfire/75"
> ! expected once, never invoked: securityService.login(not null);
> returns a default value
> ! expected once, never invoked: securityService.logout()
> what happened before this:
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames()
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.HOST")
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.GEODE_HOME")
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username")
>
> testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-password")
> securityService.login(<{security-username=admin,
> security-password=password}>)
> securityService.logout()
> at
> org.jmock.api.ExpectationError.notAllSatisfied(ExpectationError.java:27)
> at org.jmock.Mockery.assertIsSatisfied(Mockery.java:213)
> at
> org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest.tearDown(LoginHandlerInterceptorJUnitTest.java:70)
> {noformat}
> Failing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/Build/builds/558
> Passing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/Build/builds/559
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5551) Flaky test LoginHandlerInterceptorJUnitTest > testHandlerInterceptorThreadSafety
[
https://issues.apache.org/jira/browse/GEODE-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5551:
Description:
{noformat}
> Task :geode-web:test
org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest
> testHandlerInterceptorThreadSafety FAILED
junit.framework.AssertionFailedError: expected:<0> but was:<3>
not all expectations were satisfied
expectations:
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameterNames();
returns
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-username");
returns "admin"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-password");
returns "password"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.STAGE");
returns "test"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.GEODE_HOME");
returns "/path/to/gemfire/700"
expected once, already invoked 1 time: securityService.login(not null);
returns a default value
expected once, already invoked 1 time: securityService.logout()
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames();
returns
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username");
returns "admin"
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-password");
returns "password"
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.HOST");
returns "localhost"
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.GEODE_HOME");
returns "/path/to/gemfire/75"
! expected once, never invoked: securityService.login(not null); returns
a default value
! expected once, never invoked: securityService.logout()
what happened before this:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames()
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.HOST")
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameter("vf.gf.env.GEODE_HOME")
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username")
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-password")
securityService.login(<{security-username=admin,
security-password=password}>)
securityService.logout()
at
org.jmock.api.ExpectationError.notAllSatisfied(ExpectationError.java:27)
at org.jmock.Mockery.assertIsSatisfied(Mockery.java:213)
at
org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest.tearDown(LoginHandlerInterceptorJUnitTest.java:70)
{noformat}
Failing:
https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/Build/builds/558
Passing:
https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/Build/builds/559
was:
{noformat}
> Task :geode-web:test
org.apache.geode.management.internal.web.controllers.support.LoginHandlerInterceptorJUnitTest
> testHandlerInterceptorThreadSafety FAILED
junit.framework.AssertionFailedError: expected:<0> but was:<3>
not all expectations were satisfied
expectations:
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameterNames();
returns
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-username");
returns "admin"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getHeader("security-password");
returns "password"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.STAGE");
returns "test"
! expected once, never invoked:
testHandlerInterceptorThreadSafety.HttpServletRequest.1.getParameter("vf.gf.env.GEODE_HOME");
returns "/path/to/gemfire/700"
expected once, already invoked 1 time: securityService.login(not null);
returns a default value
expected once, already invoked 1 time: securityService.logout()
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getParameterNames();
returns
expected once, already invoked 1 time:
testHandlerInterceptorThreadSafety.HttpServletRequest.2.getHeader("security-username");
returns "admin"
expected once, alr
[jira] [Created] (GEODE-5552) Flaky test ConnectCommandWithSSLTest > connectWithJmxSSL
Jacob S. Barrett created GEODE-5552:
---
Summary: Flaky test ConnectCommandWithSSLTest > connectWithJmxSSL
Key: GEODE-5552
URL: https://issues.apache.org/jira/browse/GEODE-5552
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Jacob S. Barrett
{noformat}
> Task :geode-web:distributedTest
org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest >
connectWithJmxSSL FAILED
java.lang.AssertionError:
Expecting:
<"_ __
/ _/ __/ __/ // /
/ / __/ /___ /_ / _ /
/ /__/ / / _/ / // /
/__/_/ /__/_//_/1.8.0-SNAPSHOT
Monitor and Manage Apache Geode
Connecting to Locator at [host=localhost, port=42647] ..
Connection reset
">
to contain:
<"trying to connect a non-SSL-enabled client to an SSL-enabled locator">
at
org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithJmxSSL(ConnectCommandWithSSLTest.java:219)
{noformat}
Failing:
https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/DistributedTest/builds/521
Passing:
https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/DistributedTest/builds/522
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5552) Flaky test ConnectCommandWithSSLTest > connectWithJmxSSL
[
https://issues.apache.org/jira/browse/GEODE-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5552:
Affects Version/s: 1.8.0
> Flaky test ConnectCommandWithSSLTest > connectWithJmxSSL
>
>
> Key: GEODE-5552
> URL: https://issues.apache.org/jira/browse/GEODE-5552
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
>
> {noformat}
> > Task :geode-web:distributedTest
> org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest >
> connectWithJmxSSL FAILED
> java.lang.AssertionError:
> Expecting:
> <"_ __
>/ _/ __/ __/ // /
> / / __/ /___ /_ / _ /
> / /__/ / / _/ / // /
> /__/_/ /__/_//_/1.8.0-SNAPSHOT
>
> Monitor and Manage Apache Geode
> Connecting to Locator at [host=localhost, port=42647] ..
> Connection reset
> ">
> to contain:
> <"trying to connect a non-SSL-enabled client to an SSL-enabled locator">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithJmxSSL(ConnectCommandWithSSLTest.java:219)
> {noformat}
> Failing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/DistributedTest/builds/521
> Passing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/DistributedTest/builds/522
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5552) Flaky test ConnectCommandWithSSLTest > connectWithJmxSSL
[
https://issues.apache.org/jira/browse/GEODE-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-5552:
Labels: flaky swat (was: )
> Flaky test ConnectCommandWithSSLTest > connectWithJmxSSL
>
>
> Key: GEODE-5552
> URL: https://issues.apache.org/jira/browse/GEODE-5552
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> > Task :geode-web:distributedTest
> org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest >
> connectWithJmxSSL FAILED
> java.lang.AssertionError:
> Expecting:
> <"_ __
>/ _/ __/ __/ // /
> / / __/ /___ /_ / _ /
> / /__/ / / _/ / // /
> /__/_/ /__/_//_/1.8.0-SNAPSHOT
>
> Monitor and Manage Apache Geode
> Connecting to Locator at [host=localhost, port=42647] ..
> Connection reset
> ">
> to contain:
> <"trying to connect a non-SSL-enabled client to an SSL-enabled locator">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithJmxSSL(ConnectCommandWithSSLTest.java:219)
> {noformat}
> Failing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/DistributedTest/builds/521
> Passing:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/DistributedTest/builds/522
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5540) add backward compatibility tests to ClientAuthDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575056#comment-16575056 ] ASF subversion and git services commented on GEODE-5540: Commit c90e5034f5a7af99777b5849c1c3e5967ba11d70 in geode's branch refs/heads/develop from jinmeiliao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c90e503 ] GEODE-5540: add backward compatibility to client authentication tests using SecurityManager (#2280) > add backward compatibility tests to ClientAuthDUnitTest > --- > > Key: GEODE-5540 > URL: https://issues.apache.org/jira/browse/GEODE-5540 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: pull-request-available, swat > Time Spent: 20m > Remaining Estimate: 0h > > this test uses SecurityManager to secure the cluster and test client > authentication. Would be nice to use clients of different versions to connect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5534) With oql indexes and compression enabled, memory usage is greater after compression than before
[
https://issues.apache.org/jira/browse/GEODE-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575094#comment-16575094
]
ASF subversion and git services commented on GEODE-5534:
Commit 6ef68c11fdd49e02ded0bfa2bfc072f96f7ab250 in geode's branch
refs/heads/develop from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6ef68c1 ]
GEODE-5534: Forced index key to be a string when a compressed region contains
PDX values
> With oql indexes and compression enabled, memory usage is greater after
> compression than before
> ---
>
> Key: GEODE-5534
> URL: https://issues.apache.org/jira/browse/GEODE-5534
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> A test that shows the behavior is:
> - xml configuration like:
> {noformat}
>
> data-policy="persistent-replicate" disk-store-name="orderDiskStore"
> disk-synchronous="false" cloning-enabled="true">
>
> org.apache.geode.compression.SnappyCompressor
>
>
> expression="index_from.clOrdID" type="range"/>
> expression="index_from.externalOrderID" type="range"/>
> expression="index_from.externalOrderIDSource" type="range"/>
> expression="index_from.orderID" type="range"/>
> expression="index_from.parentOrderID" type="range"/>
>
> {noformat}
> - an Order object defining string fields for clOrdID, externalOrderID,
> orderID and parentOrderID and an enum field for externalOrderIDSource
> Here are some histograms showing the behavior:
> With indexes and no compression:
> {noformat}
> num #instances #bytes class name
> --
> 1: 502136 562132008 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 50 800
> org.apache.geode.internal.cache.PreferBytesCachedDeserializable
> 9: 250680 6016320 java.util.concurrent.ConcurrentSkipListMap$Index
> 10: 80 4196104
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> Total 5474612 739440976
> {noformat}
> With indexes and compression
> {noformat}
> num #instances #bytes class name
> --
> 1: 1003644 643754184 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 250889 6021336 java.util.concurrent.ConcurrentSkipListMap$Index
> 9: 80 4196096
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> 10: 34380 3261936 [C
> Total 5476808 813096488
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5212) Many distributedTest and integrationTest failures on windows
[ https://issues.apache.org/jira/browse/GEODE-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575104#comment-16575104 ] ASF subversion and git services commented on GEODE-5212: Commit e63789464dbce576fcdd6ac5dfc3a2d390426608 in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e637894 ] GEODE-5212: Add windows jobs to develop pipeline (#2284) > Many distributedTest and integrationTest failures on windows > > > Key: GEODE-5212 > URL: https://issues.apache.org/jira/browse/GEODE-5212 > Project: Geode > Issue Type: Task > Components: general, gfsh >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available, windows > Time Spent: 4h 50m > Remaining Estimate: 0h > > Windows regressions currently fail spectacularly. The primary culprits > appear to be based around filesystem I/O and passing the current working > directory to members started by our testing framework. > > The scope of this ticket will be defined by "refactors" as children tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5212) Many distributedTest and integrationTest failures on windows
[ https://issues.apache.org/jira/browse/GEODE-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575113#comment-16575113 ] ASF subversion and git services commented on GEODE-5212: Commit 887faa2e8f5351dc5a9b370fde7386736678368c in geode's branch refs/heads/develop from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=887faa2 ] GEODE-5212: Add windows jobs to develop pipeline fix base.yml to refer to correct job names > Many distributedTest and integrationTest failures on windows > > > Key: GEODE-5212 > URL: https://issues.apache.org/jira/browse/GEODE-5212 > Project: Geode > Issue Type: Task > Components: general, gfsh >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available, windows > Time Spent: 4h 50m > Remaining Estimate: 0h > > Windows regressions currently fail spectacularly. The primary culprits > appear to be based around filesystem I/O and passing the current working > directory to members started by our testing framework. > > The scope of this ticket will be defined by "refactors" as children tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5518) some records in the region are not fetched when executing fetch query
[
https://issues.apache.org/jira/browse/GEODE-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575117#comment-16575117
]
Anthony Baker commented on GEODE-5518:
--
If you remove the {{LIMIT}} clause does the problem go away?
> some records in the region are not fetched when executing fetch query
> -
>
> Key: GEODE-5518
> URL: https://issues.apache.org/jira/browse/GEODE-5518
> Project: Geode
> Issue Type: Bug
> Components: core, querying
>Reporter: yossi reginiano
>Priority: Major
>
> hi all,
> we are using geode 1.4 and facing the following:
> we are starting to adopt the putAll functions which accepts a bulk of records
> and persists them into the region
> we have noticed that the process that fetches the records from the region
> (executing fetch command with bulks of 1000) , from time to time missing a
> record or two , which is causing this records to be left in the region as a
> "Zombie" - because now current index is greater then this record's index
> now this started to happen only when we started to use the putAll function -
> prior to this we did not face any such issue
> also - when we are using putAll with only 1 record at a time it is also
> working fine
> has anybody faced this?
> is there some constraint on the number of records that can be sent to the
> putAll function?
> thanks in advance
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4336) Geode Native C++ Example (OQL)
[ https://issues.apache.org/jira/browse/GEODE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575160#comment-16575160 ] ASF subversion and git services commented on GEODE-4336: Commit db6a3f7468cf260ee93d79aa25c29537c534ca55 in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=db6a3f7 ] GEODE-4336: C++ Remote Query Example, add README.md (#328) > Geode Native C++ Example (OQL) > -- > > Key: GEODE-4336 > URL: https://issues.apache.org/jira/browse/GEODE-4336 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5549) Flaky test NonBlockingProcessStreamReaderIntegrationTest > processTerminatesWhenDestroyed
[
https://issues.apache.org/jira/browse/GEODE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-5549:
Assignee: Dan Smith
> Flaky test NonBlockingProcessStreamReaderIntegrationTest >
> processTerminatesWhenDestroyed
> -
>
> Key: GEODE-5549
> URL: https://issues.apache.org/jira/browse/GEODE-5549
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Assignee: Dan Smith
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
> > processTerminatesWhenDestroyed FAILED
> java.lang.AssertionError:
> Expecting:
> <0>
> to be greater than:
> <0>
> {noformat}
> Failed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/237
> Passed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/236
> Passed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/235
> Failed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/234
> Failing intermittently on pr pipeline as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5548) Adjust available ram in heavy lifters
[ https://issues.apache.org/jira/browse/GEODE-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575159#comment-16575159 ] ASF subversion and git services commented on GEODE-5548: Commit b9d3ff9272693b2f7d3803756e53f4d67772dd9c in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9d3ff9 ] GEODE-5548: Increase upgrade test memory. > Adjust available ram in heavy lifters > - > > Key: GEODE-5548 > URL: https://issues.apache.org/jira/browse/GEODE-5548 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Reduce available memory because we don't need as much. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4336) Geode Native C++ Example (OQL)
[ https://issues.apache.org/jira/browse/GEODE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-4336. Resolution: Fixed Fix Version/s: 1.8.0 > Geode Native C++ Example (OQL) > -- > > Key: GEODE-4336 > URL: https://issues.apache.org/jira/browse/GEODE-4336 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5540) add backward compatibility tests to ClientAuthDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-5540. Resolution: Fixed > add backward compatibility tests to ClientAuthDUnitTest > --- > > Key: GEODE-5540 > URL: https://issues.apache.org/jira/browse/GEODE-5540 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: pull-request-available, swat > Time Spent: 20m > Remaining Estimate: 0h > > this test uses SecurityManager to secure the cluster and test client > authentication. Would be nice to use clients of different versions to connect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5440) SUPERFLAKY PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
[
https://issues.apache.org/jira/browse/GEODE-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao reassigned GEODE-5440:
--
Assignee: Jinmei Liao
> SUPERFLAKY PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
> -
>
> Key: GEODE-5440
> URL: https://issues.apache.org/jira/browse/GEODE-5440
> Project: Geode
> Issue Type: Bug
> Components: querying
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Assignee: Jinmei Liao
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.html
>
>
> Flaky test in CI distributedTest job.
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest >
> testRRPRLocalQueryingWithHetroIndexes FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.partitioned.PRQueryDUnitHelper$36.run in VM 0
> running on Host 2709b168a57a with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
> at
> org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes(PRColocatedEquiJoinDUnitTest.java:873)
> Caused by:
> java.lang.AssertionError: FAILED:SelectResults size is different in
> both the cases. Size1=292 Size2 = 400; failed query=r1.ID = r2.id
> {noformat}
> Artifacts at
> http://files.apachegeode-ci.info/builds/geode-pr-2126/test-artifacts/1531783070/distributedtestcore-geode-pr-2126.tgz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5553) ClassCastException: SerialGatewaySenderQueue cannot be cast to ConcurrentParallelGatewaySenderQueue
[
https://issues.apache.org/jira/browse/GEODE-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-5553:
Assignee: Kirk Lund
> ClassCastException: SerialGatewaySenderQueue cannot be cast to
> ConcurrentParallelGatewaySenderQueue
> ---
>
> Key: GEODE-5553
> URL: https://issues.apache.org/jira/browse/GEODE-5553
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> I introduced a 1-line bug in:
> {noformat}
> commit 3f7c7774956334a6273842a62e3cd9f326130cc8
> Author: Kirk Lund
> Date: Tue Aug 7 15:27:05 2018 -0700
> GEODE-5485: Cleanup AsyncEventQueueFactoryImpl and create unit test
> {noformat}
> This results in some tests failing with:
> java.lang.ClassCastException:
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue cannot be
> cast to
> org.apache.geode.internal.cache.wan.parallel.ConcurrentParallelGatewaySenderQueue
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5553) ClassCastException: SerialGatewaySenderQueue cannot be cast to ConcurrentParallelGatewaySenderQueue
Kirk Lund created GEODE-5553:
Summary: ClassCastException: SerialGatewaySenderQueue cannot be
cast to ConcurrentParallelGatewaySenderQueue
Key: GEODE-5553
URL: https://issues.apache.org/jira/browse/GEODE-5553
Project: Geode
Issue Type: Improvement
Components: wan
Reporter: Kirk Lund
I introduced a 1-line bug in:
{noformat}
commit 3f7c7774956334a6273842a62e3cd9f326130cc8
Author: Kirk Lund
Date: Tue Aug 7 15:27:05 2018 -0700
GEODE-5485: Cleanup AsyncEventQueueFactoryImpl and create unit test
{noformat}
This results in some tests failing with:
java.lang.ClassCastException:
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue cannot be
cast to
org.apache.geode.internal.cache.wan.parallel.ConcurrentParallelGatewaySenderQueue
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5553) ClassCastException: SerialGatewaySenderQueue cannot be cast to ConcurrentParallelGatewaySenderQueue
[
https://issues.apache.org/jira/browse/GEODE-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-5553:
-
Issue Type: Bug (was: Improvement)
> ClassCastException: SerialGatewaySenderQueue cannot be cast to
> ConcurrentParallelGatewaySenderQueue
> ---
>
> Key: GEODE-5553
> URL: https://issues.apache.org/jira/browse/GEODE-5553
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Kirk Lund
>Priority: Major
>
> I introduced a 1-line bug in:
> {noformat}
> commit 3f7c7774956334a6273842a62e3cd9f326130cc8
> Author: Kirk Lund
> Date: Tue Aug 7 15:27:05 2018 -0700
> GEODE-5485: Cleanup AsyncEventQueueFactoryImpl and create unit test
> {noformat}
> This results in some tests failing with:
> java.lang.ClassCastException:
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue cannot be
> cast to
> org.apache.geode.internal.cache.wan.parallel.ConcurrentParallelGatewaySenderQueue
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5554) Standardize naming of example *.md files
Dave Barnes created GEODE-5554: -- Summary: Standardize naming of example *.md files Key: GEODE-5554 URL: https://issues.apache.org/jira/browse/GEODE-5554 Project: Geode Issue Type: Sub-task Components: docs, native client Reporter: Dave Barnes The *.md files describing how to build and run examples do not follow a consistent naming pattern. Current state: * examples/dotnet/README.md describes building examples, refers user to README.md in each example directory for running. * examples/cpp/BUILDING.md describes building examples and running them. Only one individual example has its own README.md file. Problems: * Top-level file in dotnet should have 'BUILD' in its name. * The geode-native distribution has a 'BUILDING.md' in its root directory. Top-level files in both dotnet and cpp should not be named 'BUILDING.md', because it's confusing to the user when both are open on the desktop at the same time. * The cpp examples should follow the dotnet pattern of an individual README.md for each example with instructions for running. Recommendations: * Rename example build instructions to BUILD-EXAMPLES.md for both dotnet and cpp * Add README.md to individual cpp examples * Update all CMake scripts to deploy these *.md files when examples are installed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5553) ClassCastException: SerialGatewaySenderQueue cannot be cast to ConcurrentParallelGatewaySenderQueue
[
https://issues.apache.org/jira/browse/GEODE-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575195#comment-16575195
]
ASF subversion and git services commented on GEODE-5553:
Commit 8584c0cf1b47aa4e314acd87d4cc14ff76884c09 in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8584c0c ]
GEODE-5553: Revert one line in AsyncEventQueueFactoryImpl
Fixes ClassCastException of SerialGatewaySenderQueue to
ConcurrentParallelGatewaySenderQueue in Lucene tests.
> ClassCastException: SerialGatewaySenderQueue cannot be cast to
> ConcurrentParallelGatewaySenderQueue
> ---
>
> Key: GEODE-5553
> URL: https://issues.apache.org/jira/browse/GEODE-5553
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> I introduced a 1-line bug in:
> {noformat}
> commit 3f7c7774956334a6273842a62e3cd9f326130cc8
> Author: Kirk Lund
> Date: Tue Aug 7 15:27:05 2018 -0700
> GEODE-5485: Cleanup AsyncEventQueueFactoryImpl and create unit test
> {noformat}
> This results in some tests failing with:
> java.lang.ClassCastException:
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue cannot be
> cast to
> org.apache.geode.internal.cache.wan.parallel.ConcurrentParallelGatewaySenderQueue
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5554) Standardize naming of Geode Native example *.md files
[ https://issues.apache.org/jira/browse/GEODE-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-5554: --- Summary: Standardize naming of Geode Native example *.md files (was: Standardize naming of example *.md files) > Standardize naming of Geode Native example *.md files > - > > Key: GEODE-5554 > URL: https://issues.apache.org/jira/browse/GEODE-5554 > Project: Geode > Issue Type: Sub-task > Components: docs, native client >Reporter: Dave Barnes >Priority: Major > > The *.md files describing how to build and run examples do not follow a > consistent naming pattern. Current state: > * examples/dotnet/README.md describes building examples, refers user to > README.md in each example directory for running. > * examples/cpp/BUILDING.md describes building examples and running them. > Only one individual example has its own README.md file. > Problems: > * Top-level file in dotnet should have 'BUILD' in its name. > * The geode-native distribution has a 'BUILDING.md' in its root directory. > Top-level files in both dotnet and cpp should not be named 'BUILDING.md', > because it's confusing to the user when both are open on the desktop at the > same time. > * The cpp examples should follow the dotnet pattern of an individual > README.md for each example with instructions for running. > Recommendations: > * Rename example build instructions to BUILD-EXAMPLES.md for both dotnet and > cpp > * Add README.md to individual cpp examples > * Update all CMake scripts to deploy these *.md files when examples are > installed. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5488) Use docker gradle plugin to execute all tests in parallel
[ https://issues.apache.org/jira/browse/GEODE-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-5488. - Resolution: Fixed Fix Version/s: (was: 1.7.0) 1.8.0 > Use docker gradle plugin to execute all tests in parallel > - > > Key: GEODE-5488 > URL: https://issues.apache.org/jira/browse/GEODE-5488 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Adding more test target types to run with Docker. Allows better environment > isolation and parallelism. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1357) Cleanup Category inclusion/exclusion in test.gradle
[ https://issues.apache.org/jira/browse/GEODE-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-1357. - Resolution: Invalid Fix Version/s: 1.8.0 Restructure to use nebula facets rather than JUnit categories renders this a non-issue. > Cleanup Category inclusion/exclusion in test.gradle > --- > > Key: GEODE-1357 > URL: https://issues.apache.org/jira/browse/GEODE-1357 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Kirk Lund >Priority: Major > Fix For: 1.8.0 > > > The file patterns and Category inclusion/exclusion definitions of each test > task in test.gradle should be simplified. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5510) gradle acceptanceTest is running upgradeTest too
[ https://issues.apache.org/jira/browse/GEODE-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-5510. - Resolution: Fixed > gradle acceptanceTest is running upgradeTest too > > > Key: GEODE-5510 > URL: https://issues.apache.org/jira/browse/GEODE-5510 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > A bad dependency in the test tasks. Causes upgradeTests to be executed twice > in concourse -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5477) Gradle distributedTest target fails in parallel
[ https://issues.apache.org/jira/browse/GEODE-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-5477. - Resolution: Fixed Fix Version/s: 1.8.0 > Gradle distributedTest target fails in parallel > --- > > Key: GEODE-5477 > URL: https://issues.apache.org/jira/browse/GEODE-5477 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0, 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Invoking `./gradlew distributedTest --parallel` fails in Tomcat tests, due to > a class not being on the classpath. An archive is being created before its > dependencies have been created. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5516) Docker image used by gradle should run as geode user
[
https://issues.apache.org/jira/browse/GEODE-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg resolved GEODE-5516.
-
Resolution: Fixed
Fix Version/s: 1.7.0
CI launches workers with {{--PdunitDockerUser=geode}}
> Docker image used by gradle should run as geode user
>
>
> Key: GEODE-5516
> URL: https://issues.apache.org/jira/browse/GEODE-5516
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Sean Goller
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5518) some records in the region are not fetched when executing fetch query
[ https://issues.apache.org/jira/browse/GEODE-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575224#comment-16575224 ] Jason Huynh commented on GEODE-5518: What type of map are you using? I don't think put all can maintain the order of the map unless the map itself provides an iterator that is in order. The query would then get a 'snapshot' of whatever is currently in the region. If the putAll was mid process (and random order), you could see some entries and not others. Is the putAll totally complete before the special process begins? > some records in the region are not fetched when executing fetch query > - > > Key: GEODE-5518 > URL: https://issues.apache.org/jira/browse/GEODE-5518 > Project: Geode > Issue Type: Bug > Components: core, querying >Reporter: yossi reginiano >Priority: Major > > hi all, > we are using geode 1.4 and facing the following: > we are starting to adopt the putAll functions which accepts a bulk of records > and persists them into the region > we have noticed that the process that fetches the records from the region > (executing fetch command with bulks of 1000) , from time to time missing a > record or two , which is causing this records to be left in the region as a > "Zombie" - because now current index is greater then this record's index > now this started to happen only when we started to use the putAll function - > prior to this we did not face any such issue > also - when we are using putAll with only 1 record at a time it is also > working fine > has anybody faced this? > is there some constraint on the number of records that can be sent to the > putAll function? > thanks in advance > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5282) Split DistributedTest into multiple tasks to speed up execution
[ https://issues.apache.org/jira/browse/GEODE-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-5282. - Resolution: Fixed Fix Version/s: 1.7.0 > Split DistributedTest into multiple tasks to speed up execution > --- > > Key: GEODE-5282 > URL: https://issues.apache.org/jira/browse/GEODE-5282 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently Geode's Concourse runs the "distributedTest" gradle task as a > monolithic job. Split the job into multiple tasks that execute portions of > the distributedTest task in parallel to reduce execution time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5533) ./gradlew install fails with "Could not publish configuration 'archives'"
[
https://issues.apache.org/jira/browse/GEODE-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg resolved GEODE-5533.
-
Resolution: Fixed
> ./gradlew install fails with "Could not publish configuration 'archives'"
> -
>
> Key: GEODE-5533
> URL: https://issues.apache.org/jira/browse/GEODE-5533
> Project: Geode
> Issue Type: Task
> Components: build
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Some targets changed in gradle 4.8 -> 4.9. The configuration step of
> removing jar inclusion to the publication or the archives was invalidated.
> This step needs to be updated to conform to the new targets.
> {noformat}
> > Task :geode-assembly:install FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geode-assembly:install'.
> > Could not publish configuration 'archives'
>> Cannot publish artifact 'geode-assembly.jar'
> (/Users/prhomberg/workspace/gemfire/open/geode-assembly/build/libs/geode-assembly-1.8.0-SNAPSHOT.jar)
> as it does not exist.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5555) Create `devBuild` build target for typical developer workflow
Patrick Rhomberg created GEODE-:
---
Summary: Create `devBuild` build target for typical developer
workflow
Key: GEODE-
URL: https://issues.apache.org/jira/browse/GEODE-
Project: Geode
Issue Type: Improvement
Reporter: Patrick Rhomberg
A typical developer does not want to run, for instance, {{rat}} or {{javadoc}}
as part of their standard build workflow. A {{devBuild}} target should only
build classes and, likely, also include {{spotlessApply}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5555) Create `devBuild` build target for typical developer workflow
[
https://issues.apache.org/jira/browse/GEODE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg updated GEODE-:
Component/s: build
> Create `devBuild` build target for typical developer workflow
> -
>
> Key: GEODE-
> URL: https://issues.apache.org/jira/browse/GEODE-
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Patrick Rhomberg
>Priority: Major
>
> A typical developer does not want to run, for instance, {{rat}} or
> {{javadoc}} as part of their standard build workflow. A {{devBuild}} target
> should only build classes and, likely, also include {{spotlessApply}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5555) Create `devBuild` build target for typical developer workflow
[
https://issues.apache.org/jira/browse/GEODE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg reassigned GEODE-:
---
Assignee: Patrick Rhomberg
> Create `devBuild` build target for typical developer workflow
> -
>
> Key: GEODE-
> URL: https://issues.apache.org/jira/browse/GEODE-
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
>
> A typical developer does not want to run, for instance, {{rat}} or
> {{javadoc}} as part of their standard build workflow. A {{devBuild}} target
> should only build classes and, likely, also include {{spotlessApply}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5555) Create `devBuild` build target for typical developer workflow
[
https://issues.apache.org/jira/browse/GEODE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg updated GEODE-:
Labels: pull-request-available (was: )
> Create `devBuild` build target for typical developer workflow
> -
>
> Key: GEODE-
> URL: https://issues.apache.org/jira/browse/GEODE-
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
>
> A typical developer does not want to run, for instance, {{rat}} or
> {{javadoc}} as part of their standard build workflow. A {{devBuild}} target
> should only build classes and, likely, also include {{spotlessApply}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5556) Precheckin task only includes :geode-assembly:acceptanceTest
Patrick Rhomberg created GEODE-5556: --- Summary: Precheckin task only includes :geode-assembly:acceptanceTest Key: GEODE-5556 URL: https://issues.apache.org/jira/browse/GEODE-5556 Project: Geode Issue Type: Task Reporter: Patrick Rhomberg When nebula facets were introduced, the scope of acceptanceTest was expanded to beyond geode-assembly. While the pipeline runs each target individually, this should be updated for a correct local precheckin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5556) Precheckin task only includes :geode-assembly:acceptanceTest
[ https://issues.apache.org/jira/browse/GEODE-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg reassigned GEODE-5556: --- Assignee: Patrick Rhomberg > Precheckin task only includes :geode-assembly:acceptanceTest > > > Key: GEODE-5556 > URL: https://issues.apache.org/jira/browse/GEODE-5556 > Project: Geode > Issue Type: Task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > > When nebula facets were introduced, the scope of acceptanceTest was expanded > to beyond geode-assembly. While the pipeline runs each target individually, > this should be updated for a correct local precheckin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5556) Precheckin task only includes :geode-assembly:acceptanceTest
[ https://issues.apache.org/jira/browse/GEODE-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-5556. - Resolution: Fixed Trivial fix addressed in PR for GEODE-. > Precheckin task only includes :geode-assembly:acceptanceTest > > > Key: GEODE-5556 > URL: https://issues.apache.org/jira/browse/GEODE-5556 > Project: Geode > Issue Type: Task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > > When nebula facets were introduced, the scope of acceptanceTest was expanded > to beyond geode-assembly. While the pipeline runs each target individually, > this should be updated for a correct local precheckin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5546) auto-reconnecting member reuses old address including vmViewId
[ https://issues.apache.org/jira/browse/GEODE-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575266#comment-16575266 ] ASF subversion and git services commented on GEODE-5546: Commit 2cda0039a130df6b525adc66fdba1a8ce378184e in geode's branch refs/heads/feature/GEODE-5546 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2cda003 ] GEODE-5546 auto-reconnecting member reuses old address including vmViewId Fixing two unit test failures. > auto-reconnecting member reuses old address including vmViewId > -- > > Key: GEODE-5546 > URL: https://issues.apache.org/jira/browse/GEODE-5546 > Project: Geode > Issue Type: Bug > Components: membership >Affects Versions: 1.6.0 >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > During network-down testing I found that if I restore the network immediately > after all "losing side" servers go into auto-reconnect that sometimes they > receive a view-preparation message from the surviving cluster that holds > their old membership ID. They use this ID instead of waiting for a valid new > ID and end up being shut down as rogue processes. > For instance, this process used to have an identifier with before it > went into auto-reconnect. When it tried to rejoin it ended up using that > same identifier due to receiving a view-preparation message holding it: > [info 2018/07/28 22:17:14.588 PDT > gemfire1_rs-FullRegression29040205a1i3xlarge-hydra-client-18_15643 > tid=0x2d2] Attempting to join the distributed system > through coordinator > 10.32.110.93(gemfire6_rs-FullRegression29040205a1i3xlarge-hydra-client-50_13624:13624:locator):1024 > using address > 10.32.108.125(gemfire1_rs-FullRegression29040205a1i3xlarge-hydra-client-18_15643:15643):1026 > In this run it then proceeded to hang trying to send startup messages to the > cluster. Cluster members rejected all of its attempts to contact them but > were also unsuccessful in getting the rogue process to shut down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5487) Choice of detect read conflict on transaction commit on a per-region basis.
[ https://issues.apache.org/jira/browse/GEODE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575303#comment-16575303 ] Darrel Schneider commented on GEODE-5487: - A new feature should be discussed on the geode user forum. Can you send a proposal to that forum of this feature? It should propose what APIs will change, what the behavior is, and possible alternatives. For example: should this be enabled by a RegionAttribute using api, gfsh, xml, or by a system property? What level should it be at (region, or transaction or connection)? > Choice of detect read conflict on transaction commit on a per-region basis. > --- > > Key: GEODE-5487 > URL: https://issues.apache.org/jira/browse/GEODE-5487 > Project: Geode > Issue Type: Improvement > Components: docs, transactions >Reporter: Eugene Nedzvetsky >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Geode supports detect read conflict(-Dgemfire.detectReadConflicts=true) on > transaction commit(see > https://geode.apache.org/docs/guide/11/developing/transactions/transaction_semantics.html) > This functionality can be enabled only on application level. It can > dramatically decrease application performance. > I propose to add ability to setup this property per region basis. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5487) Choice of detect read conflict on transaction commit on a per-region basis.
[ https://issues.apache.org/jira/browse/GEODE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575310#comment-16575310 ] Darrel Schneider commented on GEODE-5487: - Do you understand what caused your "dramatically decrease application performance"? Have you confirmed that changing it to be at the region level dramatically improved performance? I think it is possible that when read conflicts are detected it could cause concurrent transactions that read the same entry to fail with a conflict exception even though the entry was never written. If this is true then that would be a bug and should be fixed even if this feature request does not happen. > Choice of detect read conflict on transaction commit on a per-region basis. > --- > > Key: GEODE-5487 > URL: https://issues.apache.org/jira/browse/GEODE-5487 > Project: Geode > Issue Type: Improvement > Components: docs, transactions >Reporter: Eugene Nedzvetsky >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Geode supports detect read conflict(-Dgemfire.detectReadConflicts=true) on > transaction commit(see > https://geode.apache.org/docs/guide/11/developing/transactions/transaction_semantics.html) > This functionality can be enabled only on application level. It can > dramatically decrease application performance. > I propose to add ability to setup this property per region basis. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5557) enabling read conflict detection may cause transactions to fail with a conflict on entries that are never written
[ https://issues.apache.org/jira/browse/GEODE-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-5557: Affects Version/s: 1.0.0-incubating > enabling read conflict detection may cause transactions to fail with a > conflict on entries that are never written > - > > Key: GEODE-5557 > URL: https://issues.apache.org/jira/browse/GEODE-5557 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.0.0-incubating >Reporter: Darrel Schneider >Priority: Major > > Read conflict detection can be enabled with > -Dgemfire.detectReadConflicts=true. > If this is done then a transaction can fail because it read an entry that > some one else modified. > But it is possible that this feature will cause your transaction to fail > because some other transaction read an entry that you read or wrote. These > are not valid conflicts. > This bug is caused by the way TXReservationMgr checks for conflicts. It > treats every key sent to it as if it was written and when read confliction > detection is enabled keys we only read are sent to it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5557) enabling read conflict detection may cause transactions to fail with a conflict on entries that are never written
Darrel Schneider created GEODE-5557: --- Summary: enabling read conflict detection may cause transactions to fail with a conflict on entries that are never written Key: GEODE-5557 URL: https://issues.apache.org/jira/browse/GEODE-5557 Project: Geode Issue Type: Bug Components: transactions Reporter: Darrel Schneider Read conflict detection can be enabled with -Dgemfire.detectReadConflicts=true. If this is done then a transaction can fail because it read an entry that some one else modified. But it is possible that this feature will cause your transaction to fail because some other transaction read an entry that you read or wrote. These are not valid conflicts. This bug is caused by the way TXReservationMgr checks for conflicts. It treats every key sent to it as if it was written and when read confliction detection is enabled keys we only read are sent to it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5557) enabling read conflict detection may cause transactions to fail with a conflict on entries that are never written
[ https://issues.apache.org/jira/browse/GEODE-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575398#comment-16575398 ] Darrel Schneider commented on GEODE-5557: - This bug has existed for a long time and is in all geode releases. > enabling read conflict detection may cause transactions to fail with a > conflict on entries that are never written > - > > Key: GEODE-5557 > URL: https://issues.apache.org/jira/browse/GEODE-5557 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.0.0-incubating >Reporter: Darrel Schneider >Priority: Major > > Read conflict detection can be enabled with > -Dgemfire.detectReadConflicts=true. > If this is done then a transaction can fail because it read an entry that > some one else modified. > But it is possible that this feature will cause your transaction to fail > because some other transaction read an entry that you read or wrote. These > are not valid conflicts. > This bug is caused by the way TXReservationMgr checks for conflicts. It > treats every key sent to it as if it was written and when read confliction > detection is enabled keys we only read are sent to it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-5487) Choice of detect read conflict on transaction commit on a per-region basis.
[ https://issues.apache.org/jira/browse/GEODE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575310#comment-16575310 ] Darrel Schneider edited comment on GEODE-5487 at 8/9/18 9:25 PM: - Do you understand what caused your "dramatically decrease application performance"? Have you confirmed that changing it to be at the region level dramatically improved performance? I think it is possible that when read conflicts are detected it could cause concurrent transactions that read the same entry to fail with a conflict exception even though the entry was never written. If this is true then that would be a bug and should be fixed even if this feature request does not happen. See: https://issues.apache.org/jira/browse/GEODE-5557 was (Author: dschneider): Do you understand what caused your "dramatically decrease application performance"? Have you confirmed that changing it to be at the region level dramatically improved performance? I think it is possible that when read conflicts are detected it could cause concurrent transactions that read the same entry to fail with a conflict exception even though the entry was never written. If this is true then that would be a bug and should be fixed even if this feature request does not happen. > Choice of detect read conflict on transaction commit on a per-region basis. > --- > > Key: GEODE-5487 > URL: https://issues.apache.org/jira/browse/GEODE-5487 > Project: Geode > Issue Type: Improvement > Components: docs, transactions >Reporter: Eugene Nedzvetsky >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Geode supports detect read conflict(-Dgemfire.detectReadConflicts=true) on > transaction commit(see > https://geode.apache.org/docs/guide/11/developing/transactions/transaction_semantics.html) > This functionality can be enabled only on application level. It can > dramatically decrease application performance. > I propose to add ability to setup this property per region basis. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5558) DistributedLockServiceDUnitTest.testGrantTokenCleanup should not return early
Galen O'Sullivan created GEODE-5558: --- Summary: DistributedLockServiceDUnitTest.testGrantTokenCleanup should not return early Key: GEODE-5558 URL: https://issues.apache.org/jira/browse/GEODE-5558 Project: Geode Issue Type: Task Components: distributed lock service, tests Reporter: Galen O'Sullivan This test is marked with a TODO to finish the test after an ancient (pre-Geode) bug is fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5549) Flaky test NonBlockingProcessStreamReaderIntegrationTest > processTerminatesWhenDestroyed
[
https://issues.apache.org/jira/browse/GEODE-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5549:
--
Labels: flaky pull-request-available swat (was: flaky swat)
> Flaky test NonBlockingProcessStreamReaderIntegrationTest >
> processTerminatesWhenDestroyed
> -
>
> Key: GEODE-5549
> URL: https://issues.apache.org/jira/browse/GEODE-5549
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Assignee: Dan Smith
>Priority: Major
> Labels: flaky, pull-request-available, swat
>
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
> > processTerminatesWhenDestroyed FAILED
> java.lang.AssertionError:
> Expecting:
> <0>
> to be greater than:
> <0>
> {noformat}
> Failed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/237
> Passed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/236
> Passed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/235
> Failed:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/234
> Failing intermittently on pr pipeline as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3505) NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException
[
https://issues.apache.org/jira/browse/GEODE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-3505.
--
Resolution: Fixed
Fix Version/s: 1.8.0
This latest failure is the same as GEODE-5549.
> NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed
> fails intermittently with ConditionTimeoutException
>
>
> Key: GEODE-3505
> URL: https://issues.apache.org/jira/browse/GEODE-3505
> Project: Geode
> Issue Type: Bug
> Components: gfsh, management, tests
> Environment: AWS
>Reporter: Kirk Lund
>Priority: Major
> Labels: Flaky, swat
> Fix For: 1.8.0
>
>
> {noformat}
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
> > processTerminatesWhenDestroyed FAILED
> org.awaitility.core.ConditionTimeoutException: Condition defined as a
> lambda expression in
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5416) Geode Native C# Example (Put/get domain object using custom DataSerializable)
[ https://issues.apache.org/jira/browse/GEODE-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5416: -- Labels: pull-request-available (was: ) > Geode Native C# Example (Put/get domain object using custom DataSerializable) > - > > Key: GEODE-5416 > URL: https://issues.apache.org/jira/browse/GEODE-5416 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Ivan Godwin >Priority: Major > Labels: pull-request-available > > Create a C# .NET example that puts and gets a domain object that inherits > from DataSerializable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5544) Cleanup AsyncEventQueueImpl
[
https://issues.apache.org/jira/browse/GEODE-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575471#comment-16575471
]
Kirk Lund commented on GEODE-5544:
--
{noformat}
commit 9dbc33c6b06ded8f1a0d5a89fa4ced12e12d0987
Author: Kirk Lund
Date: Wed Aug 8 13:31:55 2018 -0700
GEODE-5544: Cleanup AsyncEventQueueImpl
* Add methods to InternalGatewaySender to prevent type casting
to AbstractGatewaySender
* Create GatewaySenderEventProcessor with method getTotalQueueSize
to use OOP instead of instanceof checks
{noformat}
> Cleanup AsyncEventQueueImpl
> ---
>
> Key: GEODE-5544
> URL: https://issues.apache.org/jira/browse/GEODE-5544
> Project: Geode
> Issue Type: Improvement
> Components: wan
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Fix For: 1.7.0
>
>
> This ticket is meant to address all feedback issues involving
> AsyncEventQueueImpl in the Pull Request for AsyncEventListenerDistributedTest.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5544) Cleanup AsyncEventQueueImpl
[ https://issues.apache.org/jira/browse/GEODE-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5544. -- Resolution: Fixed Fix Version/s: 1.7.0 > Cleanup AsyncEventQueueImpl > --- > > Key: GEODE-5544 > URL: https://issues.apache.org/jira/browse/GEODE-5544 > Project: Geode > Issue Type: Improvement > Components: wan >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Fix For: 1.7.0 > > > This ticket is meant to address all feedback issues involving > AsyncEventQueueImpl in the Pull Request for AsyncEventListenerDistributedTest. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5485) Eclipse complains that AsyncEventListenerDUnitTest $deserializeLambda$(SerializedLambda) is exceeding the 65535 bytes limit
[
https://issues.apache.org/jira/browse/GEODE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575475#comment-16575475
]
Kirk Lund commented on GEODE-5485:
--
{noformat}
commit ef55d80f1b18b1cd6babad2544b223e84bdc546d
Author: Kirk Lund
Date: Tue Aug 7 15:31:08 2018 -0700
GEODE-5485: Explode AsyncEventListenerDUnitTest
Renamed test classes:
* AsyncEventListenerDUnitTest -> AsyncEventListenerDistributedTest
* AsyncEventListenerOffHeapDUnitTest ->
AsyncEventListenerWithOffHeapDistributedTest
New test classes:
* AsyncEventListenerWithCacheLoaderDistributedTest
* AsyncEventListenerWithCacheLoaderAndOffHeapDistributedTest
* AsyncEventListenerWithFilterDistributedTest
* AsyncEventListenerWithFilterAndOffHeapDistributedTest
* ConcurrentAsyncEventListenerDistributedTest
* ConcurrentAsyncEventListenerWithOffHeapDistributedTest
* ParallelAsyncEventListenerDistributedTest
* ParallelAsyncEventListenerWithOffHeapDistributedTest
* SerialEventListenerDistributedTest
* SerialEventListenerWithOffHeapDistributedTest
{noformat}
> Eclipse complains that AsyncEventListenerDUnitTest
> $deserializeLambda$(SerializedLambda) is exceeding the 65535 bytes limit
> ---
>
> Key: GEODE-5485
> URL: https://issues.apache.org/jira/browse/GEODE-5485
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When using Eclipse, the following Error is reported under Problems:
> The code of method $deserializeLambda$(SerializedLambda) is exceeding the
> 65535 bytes limit AsyncEventListenerDUnitTest.java
> /geode-core/src/distributedTest/java/org/apache/geode/internal/cache/wan/asyncqueue
> line 74
> I'd like to fix this so that Geode is easier to work with in Eclipse.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5553) ClassCastException: SerialGatewaySenderQueue cannot be cast to ConcurrentParallelGatewaySenderQueue
[
https://issues.apache.org/jira/browse/GEODE-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-5553.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> ClassCastException: SerialGatewaySenderQueue cannot be cast to
> ConcurrentParallelGatewaySenderQueue
> ---
>
> Key: GEODE-5553
> URL: https://issues.apache.org/jira/browse/GEODE-5553
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.7.0
>
>
> I introduced a 1-line bug in:
> {noformat}
> commit 3f7c7774956334a6273842a62e3cd9f326130cc8
> Author: Kirk Lund
> Date: Tue Aug 7 15:27:05 2018 -0700
> GEODE-5485: Cleanup AsyncEventQueueFactoryImpl and create unit test
> {noformat}
> This results in some tests failing with:
> java.lang.ClassCastException:
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue cannot be
> cast to
> org.apache.geode.internal.cache.wan.parallel.ConcurrentParallelGatewaySenderQueue
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5484) Add Eclipse artifacts bin/ and .metadata to .gitignore
[ https://issues.apache.org/jira/browse/GEODE-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5484. -- > Add Eclipse artifacts bin/ and .metadata to .gitignore > -- > > Key: GEODE-5484 > URL: https://issues.apache.org/jira/browse/GEODE-5484 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add Eclipse artifacts bin/ and .metadata to .gitignore -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5485) Eclipse complains that AsyncEventListenerDUnitTest $deserializeLambda$(SerializedLambda) is exceeding the 65535 bytes limit
[ https://issues.apache.org/jira/browse/GEODE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5485. -- Resolution: Fixed Fix Version/s: 1.7.0 > Eclipse complains that AsyncEventListenerDUnitTest > $deserializeLambda$(SerializedLambda) is exceeding the 65535 bytes limit > --- > > Key: GEODE-5485 > URL: https://issues.apache.org/jira/browse/GEODE-5485 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > When using Eclipse, the following Error is reported under Problems: > The code of method $deserializeLambda$(SerializedLambda) is exceeding the > 65535 bytes limit AsyncEventListenerDUnitTest.java > /geode-core/src/distributedTest/java/org/apache/geode/internal/cache/wan/asyncqueue > line 74 > I'd like to fix this so that Geode is easier to work with in Eclipse. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5416) Geode Native C# Example (Put/get domain object using custom DataSerializable)
[ https://issues.apache.org/jira/browse/GEODE-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575509#comment-16575509 ] ASF subversion and git services commented on GEODE-5416: Commit e11c3bd20e31b220c3a3b244844bad43ceb0cecd in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=e11c3bd ] GEODE-5416: Geode Native C# Example (Put/get domain object using custom DataSerializable) Update README.md (#329) > Geode Native C# Example (Put/get domain object using custom DataSerializable) > - > > Key: GEODE-5416 > URL: https://issues.apache.org/jira/browse/GEODE-5416 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Ivan Godwin >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Create a C# .NET example that puts and gets a domain object that inherits > from DataSerializable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5416) Geode Native C# Example (Put/get domain object using custom DataSerializable)
[ https://issues.apache.org/jira/browse/GEODE-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-5416: -- Assignee: Dave Barnes > Geode Native C# Example (Put/get domain object using custom DataSerializable) > - > > Key: GEODE-5416 > URL: https://issues.apache.org/jira/browse/GEODE-5416 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Ivan Godwin >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Create a C# .NET example that puts and gets a domain object that inherits > from DataSerializable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5416) Geode Native C# Example (Put/get domain object using custom DataSerializable)
[ https://issues.apache.org/jira/browse/GEODE-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575556#comment-16575556 ] Dave Barnes commented on GEODE-5416: Code developed and committed by [~bbender] and [~igodwin] (commit #07bd702) > Geode Native C# Example (Put/get domain object using custom DataSerializable) > - > > Key: GEODE-5416 > URL: https://issues.apache.org/jira/browse/GEODE-5416 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Ivan Godwin >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Create a C# .NET example that puts and gets a domain object that inherits > from DataSerializable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5416) Geode Native C# Example (Put/get domain object using custom DataSerializable)
[ https://issues.apache.org/jira/browse/GEODE-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-5416. Resolution: Fixed Fix Version/s: 1.8.0 > Geode Native C# Example (Put/get domain object using custom DataSerializable) > - > > Key: GEODE-5416 > URL: https://issues.apache.org/jira/browse/GEODE-5416 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Ivan Godwin >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Create a C# .NET example that puts and gets a domain object that inherits > from DataSerializable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5559) RegionVersionHolder.canonicalExceptions is inefficient for large exceptions
Brian Rowe created GEODE-5559: - Summary: RegionVersionHolder.canonicalExceptions is inefficient for large exceptions Key: GEODE-5559 URL: https://issues.apache.org/jira/browse/GEODE-5559 Project: Geode Issue Type: Bug Reporter: Brian Rowe This function will traverse received versions within an exception and add them into the middle of a linked list. With a high enough number of received versions, this can become a bottleneck. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5559) RegionVersionHolder.canonicalExceptions is inefficient for large exceptions
[ https://issues.apache.org/jira/browse/GEODE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Rowe updated GEODE-5559: -- Affects Version/s: 1.7.0 > RegionVersionHolder.canonicalExceptions is inefficient for large exceptions > --- > > Key: GEODE-5559 > URL: https://issues.apache.org/jira/browse/GEODE-5559 > Project: Geode > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Brian Rowe >Priority: Major > > This function will traverse received versions within an exception and add > them into the middle of a linked list. With a high enough number of received > versions, this can become a bottleneck. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5560) member becomes coordinator but then stops when it receives a view
Bruce Schuchardt created GEODE-5560:
---
Summary: member becomes coordinator but then stops when it
receives a view
Key: GEODE-5560
URL: https://issues.apache.org/jira/browse/GEODE-5560
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Bruce Schuchardt
In a test run that aggressively shuts down and restarts locators I saw a member
become the membership coordinator but then receive a new view from the old
coordinator. This caused it to shut down its view-creator thread and give up
the role of coordinator. It stayed in this state for over 5 minutes until the
test was nuked.
{noformat}
[info 2018/08/07 23:21:06.655 PDT peerZoneDgemfire2_host1_28017 tid=0x102] This member is becoming the
membership coordinator with address
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038
[info 2018/08/07 23:21:06.660 PDT peerZoneDgemfire2_host1_28017 tid=0x102] ViewCreator starting
on:rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038
[info 2018/08/07 23:21:06.696 PDT peerZoneDgemfire2_host1_28017 tid=0x102] Member at
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030
gracefully left the distributed cache: shutdown message received
[info 2018/08/07 23:21:06.726 PDT peerZoneDgemfire2_host1_28017 tid=0x323] View Creator thread is starting
[info 2018/08/07 23:21:06.726 PDT peerZoneDgemfire2_host1_28017 tid=0x28]
received new view:
View[rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030|36]
members:
[rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030{lead},
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire1_host1_27947:27947):1033,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire1_host1_27932:27932):1034,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire2_host1_27970:27970):1036,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire2_host1_27959:27959):1035,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire1_host1_27985:27985):1037,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28033:28033):1040]
shutdown:
[rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire1_host1_28001:28001):1039,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire1_host1_27819:27819):1025,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire2_host1_27844:27844):1026,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire2_host1_27834:27834):1027,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire1_host1_27826:27826):1028,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire2_host1_27898:27898):1031,
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire2_host1_27917:27917):1032]
[info 2018/08/07 23:21:07.400 PDT peerZoneDgemfire2_host1_28017
tid=0x311] Connection: shared=false
ordered=true failed to connect to peer
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029
because: java.net.ConnectException: Connection refused
[warning 2018/08/07 23:21:09.400 PDT peerZoneDgemfire2_host1_28017
tid=0x311] Connection: Attempting
reconnect to peer
rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029
{noformat}
The method GMSJoinLeave.installView() needs to perform a check similar to
GMSJoinLeave.processLeaveRequest() and not abdicate its role as coordinator if
the creator of the view is queued up to be removed from membership.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5560) member becomes coordinator but then stops when it receives a view
[
https://issues.apache.org/jira/browse/GEODE-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-5560:
Affects Version/s: 1.6.0
> member becomes coordinator but then stops when it receives a view
> -
>
> Key: GEODE-5560
> URL: https://issues.apache.org/jira/browse/GEODE-5560
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.6.0
>Reporter: Bruce Schuchardt
>Priority: Major
>
> In a test run that aggressively shuts down and restarts locators I saw a
> member become the membership coordinator but then receive a new view from the
> old coordinator. This caused it to shut down its view-creator thread and
> give up the role of coordinator. It stayed in this state for over 5 minutes
> until the test was nuked.
> {noformat}
> [info 2018/08/07 23:21:06.655 PDT peerZoneDgemfire2_host1_28017 Priority Message Processor 21> tid=0x102] This member is becoming the
> membership coordinator with address
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038
> [info 2018/08/07 23:21:06.660 PDT peerZoneDgemfire2_host1_28017 Priority Message Processor 21> tid=0x102] ViewCreator starting
> on:rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038
> [info 2018/08/07 23:21:06.696 PDT peerZoneDgemfire2_host1_28017 Priority Message Processor 21> tid=0x102] Member at
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030
> gracefully left the distributed cache: shutdown message received
> [info 2018/08/07 23:21:06.726 PDT peerZoneDgemfire2_host1_28017 Membership View Creator> tid=0x323] View Creator thread is starting
> [info 2018/08/07 23:21:06.726 PDT peerZoneDgemfire2_host1_28017 receiver,rs-FullRegression08042427a0i3large-hydra-client-104-51513> tid=0x28]
> received new view:
> View[rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030|36]
> members:
> [rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030{lead},
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire1_host1_27947:27947):1033,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire1_host1_27932:27932):1034,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire2_host1_27970:27970):1036,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire2_host1_27959:27959):1035,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire1_host1_27985:27985):1037,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28033:28033):1040]
> shutdown:
> [rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire1_host1_28001:28001):1039,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire1_host1_27819:27819):1025,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire2_host1_27844:27844):1026,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire2_host1_27834:27834):1027,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire1_host1_27826:27826):1028,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire2_host1_27898:27898):1031,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire2_host1_27917:27917):1032]
> [info 2018/08/07 23:21:07.400 PDT peerZoneDgemfire2_host1_28017
> tid=0x311] Connection: shared=false
> ordered=true failed to connect to peer
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029
> because: java.net.ConnectException: Connection refused
> [warning 2018/08/07 23:21:09.400 PDT peerZoneDgemfire2_host1_28017
> tid=0x311] Connection: Attempting
> reconnect to peer
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029
> {noformat}
> The method GMSJoinLeave.installView() needs to perform a check similar to
> GMSJoinLeave.processLeaveRequest() and not abdicate its role as coordinator
> if the creator of the view is queued up to be removed from membership.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5560) member becomes coordinator but then stops when it receives a view
[
https://issues.apache.org/jira/browse/GEODE-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-5560:
Affects Version/s: 1.0.0-incubating
1.1.0
1.1.1
1.3.0
1.2.1
1.4.0
1.5.0
> member becomes coordinator but then stops when it receives a view
> -
>
> Key: GEODE-5560
> URL: https://issues.apache.org/jira/browse/GEODE-5560
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.3.0, 1.2.1, 1.4.0,
> 1.5.0, 1.6.0
>Reporter: Bruce Schuchardt
>Priority: Major
>
> In a test run that aggressively shuts down and restarts locators I saw a
> member become the membership coordinator but then receive a new view from the
> old coordinator. This caused it to shut down its view-creator thread and
> give up the role of coordinator. It stayed in this state for over 5 minutes
> until the test was nuked.
> {noformat}
> [info 2018/08/07 23:21:06.655 PDT peerZoneDgemfire2_host1_28017 Priority Message Processor 21> tid=0x102] This member is becoming the
> membership coordinator with address
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038
> [info 2018/08/07 23:21:06.660 PDT peerZoneDgemfire2_host1_28017 Priority Message Processor 21> tid=0x102] ViewCreator starting
> on:rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038
> [info 2018/08/07 23:21:06.696 PDT peerZoneDgemfire2_host1_28017 Priority Message Processor 21> tid=0x102] Member at
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030
> gracefully left the distributed cache: shutdown message received
> [info 2018/08/07 23:21:06.726 PDT peerZoneDgemfire2_host1_28017 Membership View Creator> tid=0x323] View Creator thread is starting
> [info 2018/08/07 23:21:06.726 PDT peerZoneDgemfire2_host1_28017 receiver,rs-FullRegression08042427a0i3large-hydra-client-104-51513> tid=0x28]
> received new view:
> View[rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030|36]
> members:
> [rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27853:27853):1030{lead},
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire1_host1_27947:27947):1033,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire1_host1_27932:27932):1034,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire2_host1_27970:27970):1036,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneCgemfire2_host1_27959:27959):1035,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire1_host1_27985:27985):1037,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28017:28017):1038,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire2_host1_28033:28033):1040]
> shutdown:
> [rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneDgemfire1_host1_28001:28001):1039,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire1_host1_27819:27819):1025,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire2_host1_27844:27844):1026,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire2_host1_27834:27834):1027,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneAgemfire1_host1_27826:27826):1028,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire2_host1_27898:27898):1031,
>
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire2_host1_27917:27917):1032]
> [info 2018/08/07 23:21:07.400 PDT peerZoneDgemfire2_host1_28017
> tid=0x311] Connection: shared=false
> ordered=true failed to connect to peer
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029
> because: java.net.ConnectException: Connection refused
> [warning 2018/08/07 23:21:09.400 PDT peerZoneDgemfire2_host1_28017
> tid=0x311] Connection: Attempting
> reconnect to peer
> rs-FullRegression08042427a0i3large-hydra-client-104(peerZoneBgemfire1_host1_27876:27876):1029
> {noformat}
> The method GMSJoinLeave.installView() needs to perform a check similar to
> GMSJoinLeave.processLeaveRequest() and not abdicate its role as coordinator
> if the creator of the view is queued up to be removed from membership.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5559) RegionVersionHolder.canonicalExceptions is inefficient for large exceptions
[ https://issues.apache.org/jira/browse/GEODE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5559: -- Labels: pull-request-available (was: ) > RegionVersionHolder.canonicalExceptions is inefficient for large exceptions > --- > > Key: GEODE-5559 > URL: https://issues.apache.org/jira/browse/GEODE-5559 > Project: Geode > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Brian Rowe >Priority: Major > Labels: pull-request-available > > This function will traverse received versions within an exception and add > them into the middle of a linked list. With a high enough number of received > versions, this can become a bottleneck. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
