[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16581309#comment-16581309
]
ASF subversion and git services commented on GEODE-5560:
Commit 7299dd84fcda8e2b7e475c63b094c22948112bd4 in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7299dd8 ]
GEODE-5560 member becomes coordinator but then stops when it receives a view
Upgraded the check to see if the receiver of a new membership view should
become the coordinator. If we've received a Leave message from the coordinator
or the coordinator is scheduled to be kicked out of the system we take over
the role of coordinator if necessary.
This closes #2299
> 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
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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=0x
[jira] [Resolved] (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 resolved GEODE-5560.
-
Resolution: Fixed
Fix Version/s: 1.7.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
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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] [Commented] (GEODE-5530) Extract shared test code from test in to frameworks
[
https://issues.apache.org/jira/browse/GEODE-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581349#comment-16581349
]
ASF subversion and git services commented on GEODE-5530:
Commit 846a58cb02914c2b18c357ff556df285eb78981c in geode's branch
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=846a58c ]
GEODE-5530: Add geode-core project to distributedTestRuntimeOnly (#2322)
* AnalyzeSerializablesJUnitTest should be an integrationTest
> Extract shared test code from test in to frameworks
> ---
>
> Key: GEODE-5530
> URL: https://issues.apache.org/jira/browse/GEODE-5530
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: pull-request-available
> Time Spent: 8h
> Remaining Estimate: 0h
>
> Many tests between modules share code. Move this code into common frameworks,
> {{geode-junit}} and {{geode-dunit}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5439) Remove CliCommandTestBase and parameterize tests in CommandOverHttpDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helena Bales resolved GEODE-5439. - Resolution: Fixed Assignee: Helena Bales Fix Version/s: 1.8.0 Fixed as part of GEODE-3530 > Remove CliCommandTestBase and parameterize tests in CommandOverHttpDUnitTest > > > Key: GEODE-5439 > URL: https://issues.apache.org/jira/browse/GEODE-5439 > Project: Geode > Issue Type: Task >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Labels: swat > Fix For: 1.7.0, 1.8.0 > > > Remove the CliCommandTestBase. > Parameterize the DUnit tests listed in CommandOverHttpDUnitTest to run over > both JMX and Http. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5438) Add a test helper for executing multiple threads
[ https://issues.apache.org/jira/browse/GEODE-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581361#comment-16581361 ] ASF subversion and git services commented on GEODE-5438: Commit 5e790c8b99d510525f0954a6d0f3bf10aa9478c1 in geode's branch refs/heads/develop from [~balesh2] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5e790c8 ] GEODE-5438: Add rule for running threads in tests Signed-off-by Brian Rowe > Add a test helper for executing multiple threads > > > Key: GEODE-5438 > URL: https://issues.apache.org/jira/browse/GEODE-5438 > Project: Geode > Issue Type: Task >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Labels: pull-request-available, swat > Time Spent: 1.5h > Remaining Estimate: 0h > > Add a test helper for tests that start multiple threads and wait for them to > complete. Run a list of Runnables or a list of Callables, with or without a > given timeout and collect the results of the threads. If exceptions are > thrown, provide those exceptions. Return the results from the Callables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5438) Add a test helper for executing multiple threads
[ https://issues.apache.org/jira/browse/GEODE-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helena Bales resolved GEODE-5438. - Resolution: Fixed Fix Version/s: 1.8.0 > Add a test helper for executing multiple threads > > > Key: GEODE-5438 > URL: https://issues.apache.org/jira/browse/GEODE-5438 > Project: Geode > Issue Type: Task >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Add a test helper for tests that start multiple threads and wait for them to > complete. Run a list of Runnables or a list of Callables, with or without a > given timeout and collect the results of the threads. If exceptions are > thrown, provide those exceptions. Return the results from the Callables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5414) Create a geode-example for WAN replication
[ https://issues.apache.org/jira/browse/GEODE-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581367#comment-16581367 ] ASF subversion and git services commented on GEODE-5414: Commit d9f888e1583510b049b41da8d93f2848ae26d884 in geode-examples's branch refs/heads/develop from [~dhardman] [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=d9f888e ] GEODE-5414: Adding WAN example. > Create a geode-example for WAN replication > -- > > Key: GEODE-5414 > URL: https://issues.apache.org/jira/browse/GEODE-5414 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Diane Hardman >Assignee: Diane Hardman >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > Create a simple example for implementing WAN replication between 2 Geode > clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5421) Creating region with gateway sender immediately after creating the gateway sender in gfsh unexpectedly fails.
[ https://issues.apache.org/jira/browse/GEODE-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581368#comment-16581368 ] ASF subversion and git services commented on GEODE-5421: Commit 0868e1d5255639242a06b4b5a123ea84d431037a in geode-examples's branch refs/heads/develop from [~dhardman] [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=0868e1d ] Updated start.gfsh to remove list members commands and add 5 sec sleep between creating clusters and adding region to workaround GEODE-5421 > Creating region with gateway sender immediately after creating the gateway > sender in gfsh unexpectedly fails. > - > > Key: GEODE-5421 > URL: https://issues.apache.org/jira/browse/GEODE-5421 > Project: Geode > Issue Type: Bug > Components: gfsh, wan >Affects Versions: 1.6.0 >Reporter: Diane Hardman >Priority: Major > Attachments: start-ln.gfsh > > > In the attached gfsh script I am attempting to start up a single cluster that > includes gateway senders and receivers on each server for the example-region. > After starting the locator and 2 servers, I create the gateway receivers and > senders. If I then try to create the region 'example-region' and associated > it with the gateway sender, I get the following error: > There are no GatewaySenders defined currently in the system. > If I create the region in a different script, it works. This is unexpected > and I would like to have this all in a single startup script. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5414) Create a geode-example for WAN replication
[ https://issues.apache.org/jira/browse/GEODE-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581370#comment-16581370 ] ASF subversion and git services commented on GEODE-5414: Commit 872f70ff14ed33bf040dc54cc9c66d29eb82a5c7 in geode-examples's branch refs/heads/develop from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=872f70f ] Merge pull request #66 from dihardman/feature/GEODE-5414-2 GEODE-5414 Updated WAN example with sleep added to start.gfsh to pass runAll > Create a geode-example for WAN replication > -- > > Key: GEODE-5414 > URL: https://issues.apache.org/jira/browse/GEODE-5414 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Diane Hardman >Assignee: Diane Hardman >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > Create a simple example for implementing WAN replication between 2 Geode > clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5414) Create a geode-example for WAN replication
[ https://issues.apache.org/jira/browse/GEODE-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581369#comment-16581369 ] ASF subversion and git services commented on GEODE-5414: Commit 872f70ff14ed33bf040dc54cc9c66d29eb82a5c7 in geode-examples's branch refs/heads/develop from [~ukohlmeyer] [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=872f70f ] Merge pull request #66 from dihardman/feature/GEODE-5414-2 GEODE-5414 Updated WAN example with sleep added to start.gfsh to pass runAll > Create a geode-example for WAN replication > -- > > Key: GEODE-5414 > URL: https://issues.apache.org/jira/browse/GEODE-5414 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Diane Hardman >Assignee: Diane Hardman >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > Create a simple example for implementing WAN replication between 2 Geode > clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3780) suspected member is never watched again after passing final check
[ https://issues.apache.org/jira/browse/GEODE-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581375#comment-16581375 ] ASF subversion and git services commented on GEODE-3780: Commit cd3f372906501f0f936ba96d6907d972d5c2d478 in geode's branch refs/heads/develop from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=cd3f372 ] GEODE-3780 suspected member is never watched again after passing final check Consolidated "unsuspect" processing into a memberUnsuspected() method. Modified "final check" method to not unsuspect a member that fails the check. > suspected member is never watched again after passing final check > - > > Key: GEODE-3780 > URL: https://issues.apache.org/jira/browse/GEODE-3780 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.4.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In a network-down test we saw a node on the losing side of the network > partition perform final checks on members on the winning side. One of the > final checks mysteriously succeeded > [info 2017/09/17 12:24:45.552 PDT > gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 Detection thread 4> tid=0x128] Final check failed but detected recent message > traffic for suspect member > 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135):1026 > [info 2017/09/17 12:24:45.552 PDT > gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 Detection thread 4> tid=0x128] Final check passed for suspect member > 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135):1026 > After this the suspected member was never checked again and the losing side > failed to shut down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3780) suspected member is never watched again after passing final check
[ https://issues.apache.org/jira/browse/GEODE-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-3780. - Resolution: Fixed Fix Version/s: (was: 1.4.0) 1.7.0 commit cd3f372906501f0f936ba96d6907d972d5c2d478 (HEAD -> develop, origin/develop) Author: Bruce Schuchardt Date: Wed Aug 15 10:17:38 2018 -0700 GEODE-3780 suspected member is never watched again after passing final check Consolidated "unsuspect" processing into a memberUnsuspected() method. Modified "final check" method to not unsuspect a member that fails the check. > suspected member is never watched again after passing final check > - > > Key: GEODE-3780 > URL: https://issues.apache.org/jira/browse/GEODE-3780 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > In a network-down test we saw a node on the losing side of the network > partition perform final checks on members on the winning side. One of the > final checks mysteriously succeeded > [info 2017/09/17 12:24:45.552 PDT > gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 Detection thread 4> tid=0x128] Final check failed but detected recent message > traffic for suspect member > 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135):1026 > [info 2017/09/17 12:24:45.552 PDT > gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 Detection thread 4> tid=0x128] Final check passed for suspect member > 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135):1026 > After this the suspected member was never checked again and the losing side > failed to shut down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5583) ManagementAdapterTest should use concurrency rule
Helena Bales created GEODE-5583: --- Summary: ManagementAdapterTest should use concurrency rule Key: GEODE-5583 URL: https://issues.apache.org/jira/browse/GEODE-5583 Project: Geode Issue Type: Test Reporter: Helena Bales ManagementAdapterTest has an overly complicated implementation of threading that used to not wait for results. Given that the concurrency rule has now been added, this test should use that rule instead of providing its own implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5583) ManagementAdapterTest should use concurrency rule
[ https://issues.apache.org/jira/browse/GEODE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helena Bales reassigned GEODE-5583: --- Assignee: Helena Bales > ManagementAdapterTest should use concurrency rule > - > > Key: GEODE-5583 > URL: https://issues.apache.org/jira/browse/GEODE-5583 > Project: Geode > Issue Type: Test >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Labels: swat > > ManagementAdapterTest has an overly complicated implementation of threading > that used to not wait for results. Given that the concurrency rule has now > been added, this test should use that rule instead of providing its own > implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5583) ManagementAdapterTest should use concurrency rule
[ https://issues.apache.org/jira/browse/GEODE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5583: -- Labels: pull-request-available swat (was: swat) > ManagementAdapterTest should use concurrency rule > - > > Key: GEODE-5583 > URL: https://issues.apache.org/jira/browse/GEODE-5583 > Project: Geode > Issue Type: Test >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Labels: pull-request-available, swat > > ManagementAdapterTest has an overly complicated implementation of threading > that used to not wait for results. Given that the concurrency rule has now > been added, this test should use that rule instead of providing its own > implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5584) Switch concourse template generation from spruce to jinja
Finn Southerland created GEODE-5584: --- Summary: Switch concourse template generation from spruce to jinja Key: GEODE-5584 URL: https://issues.apache.org/jira/browse/GEODE-5584 Project: Geode Issue Type: Task Reporter: Finn Southerland The meta scripts currently use spruce to assemble the other pipeline templates. They should use jinja, because it is more readable and will be easier to extend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5585) ConcurrencyRule: Make sure that threads are run
Helena Bales created GEODE-5585: --- Summary: ConcurrencyRule: Make sure that threads are run Key: GEODE-5585 URL: https://issues.apache.org/jira/browse/GEODE-5585 Project: Geode Issue Type: Improvement Reporter: Helena Bales With the concurrency rule it is still possible to forget to run the submitted threads. Add a check to the after() for the rule to make sure that threads are run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5585) ConcurrencyRule: Make sure that threads are run
[ https://issues.apache.org/jira/browse/GEODE-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helena Bales reassigned GEODE-5585: --- Assignee: Helena Bales > ConcurrencyRule: Make sure that threads are run > --- > > Key: GEODE-5585 > URL: https://issues.apache.org/jira/browse/GEODE-5585 > Project: Geode > Issue Type: Improvement >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Labels: swat > > With the concurrency rule it is still possible to forget to run the submitted > threads. Add a check to the after() for the rule to make sure that threads > are run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5584) Switch concourse template generation from spruce to jinja
[ https://issues.apache.org/jira/browse/GEODE-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5584: -- Labels: pull-request-available (was: ) > Switch concourse template generation from spruce to jinja > - > > Key: GEODE-5584 > URL: https://issues.apache.org/jira/browse/GEODE-5584 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > > The meta scripts currently use spruce to assemble the other pipeline > templates. They should use jinja, because it is more readable and will be > easier to extend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5584) Switch concourse template generation from spruce to jinja
[ https://issues.apache.org/jira/browse/GEODE-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581421#comment-16581421 ] ASF subversion and git services commented on GEODE-5584: Commit bac62ee74c9e076ce9e61456f402e6791d46f84b in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bac62ee ] GEODE-5584: Converts all pipelines to Jinja2 templates (#2331) - Created new Jinja2 templates to generate pipeline. - Deleted old spruce templates. - Images updated to include Jinja and remove spruce. Co-authored-by: Robert Houghton Co-authored-by: Finn Southerland Co-authored-by: Patrick Rhomberg Co-authored-by: Jake Barrett > Switch concourse template generation from spruce to jinja > - > > Key: GEODE-5584 > URL: https://issues.apache.org/jira/browse/GEODE-5584 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The meta scripts currently use spruce to assemble the other pipeline > templates. They should use jinja, because it is more readable and will be > easier to extend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5585) ConcurrencyRule: Make sure that threads are run
[ https://issues.apache.org/jira/browse/GEODE-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5585: -- Labels: pull-request-available swat (was: swat) > ConcurrencyRule: Make sure that threads are run > --- > > Key: GEODE-5585 > URL: https://issues.apache.org/jira/browse/GEODE-5585 > Project: Geode > Issue Type: Improvement >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Labels: pull-request-available, swat > > With the concurrency rule it is still possible to forget to run the submitted > threads. Add a check to the after() for the rule to make sure that threads > are run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5584) Switch concourse template generation from spruce to jinja
[ https://issues.apache.org/jira/browse/GEODE-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581443#comment-16581443 ] ASF subversion and git services commented on GEODE-5584: Commit 1cbd41e293fb1d8e691e5aa3ee2ca9f0a9c74df4 in geode's branch refs/heads/develop from Jake Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1cbd41e ] GEODE-5584: Fixes branch path. Co-authored-by: Finn Southerland Co-authored-by: Jake Barrett > Switch concourse template generation from spruce to jinja > - > > Key: GEODE-5584 > URL: https://issues.apache.org/jira/browse/GEODE-5584 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The meta scripts currently use spruce to assemble the other pipeline > templates. They should use jinja, because it is more readable and will be > easier to extend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5571) Pulse Data Browser queries should be saved in history before they are executed in case they don't return
[ https://issues.apache.org/jira/browse/GEODE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581452#comment-16581452 ] ASF subversion and git services commented on GEODE-5571: Commit 636d783daffba8ca6d133a8ff3aac0e7c3b2ac4e in geode's branch refs/heads/feature/GEODE-5571 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=636d783 ] GEODE-5571: Force CI to re-run > Pulse Data Browser queries should be saved in history before they are > executed in case they don't return > > > Key: GEODE-5571 > URL: https://issues.apache.org/jira/browse/GEODE-5571 > Project: Geode > Issue Type: Bug > Components: pulse >Reporter: Barry Oglesby >Assignee: Barry Oglesby >Priority: Major > Labels: pull-request-available, swat > Time Spent: 10m > Remaining Estimate: 0h > > Data Browser queries that throw exceptions or do not return at all are not > saved in the PULSE_QueryHistory.json file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3720) SUPERFLAKY: ConnectCommandWithSSLTest failed
[ https://issues.apache.org/jira/browse/GEODE-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581461#comment-16581461 ] Mark Hanson commented on GEODE-3720: Failed again in [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/259] > SUPERFLAKY: ConnectCommandWithSSLTest failed > > > Key: GEODE-3720 > URL: https://issues.apache.org/jira/browse/GEODE-3720 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.2.1 >Reporter: Jinmei Liao >Priority: Major > Labels: ci, pull-request-available, swat > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.html > > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > 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.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSL(ConnectCommandWithSSLTest.java:198) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > 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.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithNoSSL(ConnectCommandWithSSLTest.java:177) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterAndJmxSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > 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.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterAndJmxSSL(ConnectCommandWithSSLTest.java:309) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSLAndThenWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > 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.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSLAndThenWithNoSSL(ConnectCommandWithSSLTest.java:320) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithHttpSSLAndSkipSSLValidation FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > 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.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithHttpSSLAndSkipSSLValidation(ConnectCommandWithSSLTest.java:286) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > 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.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterSSL(ConnectCommandWithSSLTest.java:246) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithJm
[jira] [Commented] (GEODE-5584) Switch concourse template generation from spruce to jinja
[ https://issues.apache.org/jira/browse/GEODE-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581462#comment-16581462 ] ASF subversion and git services commented on GEODE-5584: Commit 425debc3cbdd87e32dcbc8a87e4e0b22d2a93f87 in geode's branch refs/heads/develop from [~fsoutherland] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=425debc ] GEODE-5584: Fixes pipeline prefix. Co-authored-by: Finn Southerland Co-authored-by: Jake Barrett > Switch concourse template generation from spruce to jinja > - > > Key: GEODE-5584 > URL: https://issues.apache.org/jira/browse/GEODE-5584 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The meta scripts currently use spruce to assemble the other pipeline > templates. They should use jinja, because it is more readable and will be > easier to extend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5586) Use the ConcurrencyRule in tests that use threads
Helena Bales created GEODE-5586: --- Summary: Use the ConcurrencyRule in tests that use threads Key: GEODE-5586 URL: https://issues.apache.org/jira/browse/GEODE-5586 Project: Geode Issue Type: Task Reporter: Helena Bales Refactor tests that provide their own implementation of submitting and waiting for threads to run to use the ConcurrencyRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5584) Switch concourse template generation from spruce to jinja
[ https://issues.apache.org/jira/browse/GEODE-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581476#comment-16581476 ] ASF subversion and git services commented on GEODE-5584: Commit 4ae979875a6764356b4ed7db608d883376b365b4 in geode's branch refs/heads/develop from [~fsoutherland] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4ae9798 ] GEODE-5584: Fixes image path on PR Co-authored-by: Finn Southerland Co-authored-by: Jake Barrett > Switch concourse template generation from spruce to jinja > - > > Key: GEODE-5584 > URL: https://issues.apache.org/jira/browse/GEODE-5584 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The meta scripts currently use spruce to assemble the other pipeline > templates. They should use jinja, because it is more readable and will be > easier to extend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5587) Randomize internal http service working directory
Jens Deppe created GEODE-5587:
-
Summary: Randomize internal http service working directory
Key: GEODE-5587
URL: https://issues.apache.org/jira/browse/GEODE-5587
Project: Geode
Issue Type: Improvement
Components: pulse, rest (admin), rest (dev)
Reporter: Jens Deppe
When starting the http service a given webapp is extracted into a working
directory of the form: {{__}}. As part of shutdown this
directory is cleaned up. However the directory is only completely removed when
the JVM exits.
Occasionally subsequent tests will request to use the same port. This results
in the same working directory being used. On Windows this will fail as the
directory does not let itself be cleaned up before the webapp is redeployed to
the same location as before.
We can randomize the working directory a bit more by adding a short sequence of
random chars as part of the directory name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5587) Randomize internal http service working directory
[
https://issues.apache.org/jira/browse/GEODE-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe reassigned GEODE-5587:
-
Assignee: Jens Deppe
> Randomize internal http service working directory
> -
>
> Key: GEODE-5587
> URL: https://issues.apache.org/jira/browse/GEODE-5587
> Project: Geode
> Issue Type: Improvement
> Components: pulse, rest (admin), rest (dev)
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> When starting the http service a given webapp is extracted into a working
> directory of the form: {{__}}. As part of shutdown this
> directory is cleaned up. However the directory is only completely removed
> when the JVM exits.
> Occasionally subsequent tests will request to use the same port. This results
> in the same working directory being used. On Windows this will fail as the
> directory does not let itself be cleaned up before the webapp is redeployed
> to the same location as before.
> We can randomize the working directory a bit more by adding a short sequence
> of random chars as part of the directory name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5587) Randomize internal http service working directory
[
https://issues.apache.org/jira/browse/GEODE-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-5587:
--
Issue Type: Bug (was: Improvement)
> Randomize internal http service working directory
> -
>
> Key: GEODE-5587
> URL: https://issues.apache.org/jira/browse/GEODE-5587
> Project: Geode
> Issue Type: Bug
> Components: pulse, rest (admin), rest (dev)
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> When starting the http service a given webapp is extracted into a working
> directory of the form: {{__}}. As part of shutdown this
> directory is cleaned up. However the directory is only completely removed
> when the JVM exits.
> Occasionally subsequent tests will request to use the same port. This results
> in the same working directory being used. On Windows this will fail as the
> directory does not let itself be cleaned up before the webapp is redeployed
> to the same location as before.
> We can randomize the working directory a bit more by adding a short sequence
> of random chars as part of the directory name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5587) Randomize internal http service working directory
[
https://issues.apache.org/jira/browse/GEODE-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5587:
--
Labels: pull-request-available (was: )
> Randomize internal http service working directory
> -
>
> Key: GEODE-5587
> URL: https://issues.apache.org/jira/browse/GEODE-5587
> Project: Geode
> Issue Type: Bug
> Components: pulse, rest (admin), rest (dev)
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> When starting the http service a given webapp is extracted into a working
> directory of the form: {{__}}. As part of shutdown this
> directory is cleaned up. However the directory is only completely removed
> when the JVM exits.
> Occasionally subsequent tests will request to use the same port. This results
> in the same working directory being used. On Windows this will fail as the
> directory does not let itself be cleaned up before the webapp is redeployed
> to the same location as before.
> We can randomize the working directory a bit more by adding a short sequence
> of random chars as part of the directory name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5584) Switch concourse template generation from spruce to jinja
[ https://issues.apache.org/jira/browse/GEODE-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581489#comment-16581489 ] ASF subversion and git services commented on GEODE-5584: Commit 691573bd1cad8190e900be04d1a3c2ca9b604e08 in geode's branch refs/heads/develop from Jake Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=691573b ] GEODE-5584: make meta pipeline dependent on shared resources Co-authored-by: Finn Southerland Co-authored-by: Jake Barrett > Switch concourse template generation from spruce to jinja > - > > Key: GEODE-5584 > URL: https://issues.apache.org/jira/browse/GEODE-5584 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The meta scripts currently use spruce to assemble the other pipeline > templates. They should use jinja, because it is more readable and will be > easier to extend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5584) Switch concourse template generation from spruce to jinja
[ https://issues.apache.org/jira/browse/GEODE-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581492#comment-16581492 ] ASF subversion and git services commented on GEODE-5584: Commit a279aefc71d6a1aa67ae02f14744fdb7b53aabb1 in geode's branch refs/heads/develop from [~fsoutherland] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a279aef ] GEODE-5584: dash removed from image path Co-authored-by: Finn Southerland Co-authored-by: Jake Barrett > Switch concourse template generation from spruce to jinja > - > > Key: GEODE-5584 > URL: https://issues.apache.org/jira/browse/GEODE-5584 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The meta scripts currently use spruce to assemble the other pipeline > templates. They should use jinja, because it is more readable and will be > easier to extend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5588) MemberStarterRule.withHttpService does not always work
Jens Deppe created GEODE-5588:
-
Summary: MemberStarterRule.withHttpService does not always work
Key: GEODE-5588
URL: https://issues.apache.org/jira/browse/GEODE-5588
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Jens Deppe
This method does not work as expected under some situations. For example, this
code fails to start the http service:
{noformat}
@Rule
public GfshCommandRule gfsh = new GfshCommandRule();
@Test
public void sanity() throws Exception {
lRule.withJMXManager().withHttpService()
.startLocator();
gfsh.connectAndVerify(lRule.getHttpPort(), GfshCommandRule.PortType.http);
}
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5588) MemberStarterRule.withHttpService does not always work
[
https://issues.apache.org/jira/browse/GEODE-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe reassigned GEODE-5588:
-
Assignee: Jens Deppe
> MemberStarterRule.withHttpService does not always work
> --
>
> Key: GEODE-5588
> URL: https://issues.apache.org/jira/browse/GEODE-5588
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> This method does not work as expected under some situations. For example,
> this code fails to start the http service:
> {noformat}
> @Rule
> public GfshCommandRule gfsh = new GfshCommandRule();
> @Test
> public void sanity() throws Exception {
> lRule.withJMXManager().withHttpService()
> .startLocator();
> gfsh.connectAndVerify(lRule.getHttpPort(), GfshCommandRule.PortType.http);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5588) MemberStarterRule.withHttpService does not always work
[
https://issues.apache.org/jira/browse/GEODE-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5588:
--
Labels: pull-request-available (was: )
> MemberStarterRule.withHttpService does not always work
> --
>
> Key: GEODE-5588
> URL: https://issues.apache.org/jira/browse/GEODE-5588
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> This method does not work as expected under some situations. For example,
> this code fails to start the http service:
> {noformat}
> @Rule
> public GfshCommandRule gfsh = new GfshCommandRule();
> @Test
> public void sanity() throws Exception {
> lRule.withJMXManager().withHttpService()
> .startLocator();
> gfsh.connectAndVerify(lRule.getHttpPort(), GfshCommandRule.PortType.http);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5536) Parallelize unit tests
[ https://issues.apache.org/jira/browse/GEODE-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5536: -- Labels: pull-request-available (was: ) > Parallelize unit tests > -- > > Key: GEODE-5536 > URL: https://issues.apache.org/jira/browse/GEODE-5536 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > > Unit tests should run in parallel within subprojects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5541) A create followed by a destroy of the same key in a transaction invokes cache listener on remote node
[ https://issues.apache.org/jira/browse/GEODE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581602#comment-16581602 ] ASF subversion and git services commented on GEODE-5541: Commit bc77954ddce4c1d21dbaef696c3507db983ef242 in geode's branch refs/heads/develop from eshu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bc77954 ] Revert "GEODE-5541: A create followed by a destroy of the same key will not invoke cache listener on remote nodes. (#2282)" This reverts commit 6f8de005b0026b3e365cb577d07119e0d53c6ed4. > A create followed by a destroy of the same key in a transaction invokes cache > listener on remote node > - > > Key: GEODE-5541 > URL: https://issues.apache.org/jira/browse/GEODE-5541 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > A create followed by a destroy of the same key in a transaction is treated as > a no op on the near side (transaction host), and no destroy event is invoked > on the transaction host. The destroy operation is distributed to remote nodes > (far side). The intend is to make sure a normal region can destroy the key if > it exists (far side). > Currently a destroy event is invoked for this no op on remote node even > though the node does not have the key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-5541) A create followed by a destroy of the same key in a transaction invokes cache listener on remote node
[ https://issues.apache.org/jira/browse/GEODE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reopened GEODE-5541: - revert this checkin as it does not handle rebalance case. > A create followed by a destroy of the same key in a transaction invokes cache > listener on remote node > - > > Key: GEODE-5541 > URL: https://issues.apache.org/jira/browse/GEODE-5541 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > A create followed by a destroy of the same key in a transaction is treated as > a no op on the near side (transaction host), and no destroy event is invoked > on the transaction host. The destroy operation is distributed to remote nodes > (far side). The intend is to make sure a normal region can destroy the key if > it exists (far side). > Currently a destroy event is invoked for this no op on remote node even > though the node does not have the key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5440) SUPERFLAKY PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
[
https://issues.apache.org/jira/browse/GEODE-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5440:
--
Labels: pull-request-available swat (was: swat)
> 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: pull-request-available, 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] [Created] (GEODE-5589) lastResultReceived is set to true well before the last message is sent
nabarun created GEODE-5589: -- Summary: lastResultReceived is set to true well before the last message is sent Key: GEODE-5589 URL: https://issues.apache.org/jira/browse/GEODE-5589 Project: Geode Issue Type: Bug Components: functions Reporter: nabarun *+Issue+*: - In the method lastResult we immediately set the lastResultReceived to be true. - If an exception occurs after the flag is set and before the message is sent (like security exception) - Then this exception will never be sent to the client because the lastResultReceived is set and clients will be stuck waiting for the function results. *+Solution+*: - set the flag after the message is sent. *+Affected code+* : - ServerToClientFunctionResultSender65.java - ServerToClientFunctionResultSender.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5589) lastResultReceived is set to true well before the last message is sent
[ https://issues.apache.org/jira/browse/GEODE-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun reassigned GEODE-5589: -- Assignee: nabarun > lastResultReceived is set to true well before the last message is sent > -- > > Key: GEODE-5589 > URL: https://issues.apache.org/jira/browse/GEODE-5589 > Project: Geode > Issue Type: Bug > Components: functions >Reporter: nabarun >Assignee: nabarun >Priority: Major > > *+Issue+*: > - In the method lastResult we immediately set the lastResultReceived to be > true. > - If an exception occurs after the flag is set and before the message is sent > (like security exception) > - Then this exception will never be sent to the client because the > lastResultReceived is set and clients will be stuck waiting for the function > results. > *+Solution+*: > - set the flag after the message is sent. > *+Affected code+* : > - ServerToClientFunctionResultSender65.java > - ServerToClientFunctionResultSender.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5590) CI Failure: PutCommandWithJsonTest > putWithJsonString Fails intermittently
Helena Bales created GEODE-5590:
---
Summary: CI Failure: PutCommandWithJsonTest > putWithJsonString
Fails intermittently
Key: GEODE-5590
URL: https://issues.apache.org/jira/browse/GEODE-5590
Project: Geode
Issue Type: Bug
Reporter: Helena Bales
{code:java}
org.apache.geode.management.internal.cli.commands.PutCommandWithJsonTest >
putWithJsonString FAILED
org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
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.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:117)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:135)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:106)
at
org.apache.geode.management.internal.cli.commands.PutCommandWithJsonTest.putWithJsonString(PutCommandWithJsonTest.java:55)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5589) lastResultReceived is set to true well before the last message is sent
[ https://issues.apache.org/jira/browse/GEODE-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5589: -- Labels: pull-request-available (was: ) > lastResultReceived is set to true well before the last message is sent > -- > > Key: GEODE-5589 > URL: https://issues.apache.org/jira/browse/GEODE-5589 > Project: Geode > Issue Type: Bug > Components: functions >Reporter: nabarun >Assignee: nabarun >Priority: Major > Labels: pull-request-available > > *+Issue+*: > - In the method lastResult we immediately set the lastResultReceived to be > true. > - If an exception occurs after the flag is set and before the message is sent > (like security exception) > - Then this exception will never be sent to the client because the > lastResultReceived is set and clients will be stuck waiting for the function > results. > *+Solution+*: > - set the flag after the message is sent. > *+Affected code+* : > - ServerToClientFunctionResultSender65.java > - ServerToClientFunctionResultSender.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5583) ManagementAdapterTest should use concurrency rule
[ https://issues.apache.org/jira/browse/GEODE-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581720#comment-16581720 ] ASF subversion and git services commented on GEODE-5583: Commit cfc30ebef382165c94e80533054a5cc8b8cc946d in geode's branch refs/heads/develop from [~balesh2] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=cfc30eb ] GEODE-5583: Use the ConcurrencyRule to run threads (#2330) Use the concurrency rule to run threads instead of providing a custom implementation that may or may not be correct. > ManagementAdapterTest should use concurrency rule > - > > Key: GEODE-5583 > URL: https://issues.apache.org/jira/browse/GEODE-5583 > Project: Geode > Issue Type: Test >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Labels: pull-request-available, swat > Time Spent: 0.5h > Remaining Estimate: 0h > > ManagementAdapterTest has an overly complicated implementation of threading > that used to not wait for results. Given that the concurrency rule has now > been added, this test should use that rule instead of providing its own > implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5588) MemberStarterRule.withHttpService does not always work
[
https://issues.apache.org/jira/browse/GEODE-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581730#comment-16581730
]
ASF subversion and git services commented on GEODE-5588:
Commit ac56a494f6908a0d8e28164a1dbc4ef25759e935 in geode's branch
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ac56a49 ]
GEODE-5588: MemberStarterRule.withHttpService fails in some situations (#2336)
> MemberStarterRule.withHttpService does not always work
> --
>
> Key: GEODE-5588
> URL: https://issues.apache.org/jira/browse/GEODE-5588
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This method does not work as expected under some situations. For example,
> this code fails to start the http service:
> {noformat}
> @Rule
> public GfshCommandRule gfsh = new GfshCommandRule();
> @Test
> public void sanity() throws Exception {
> lRule.withJMXManager().withHttpService()
> .startLocator();
> gfsh.connectAndVerify(lRule.getHttpPort(), GfshCommandRule.PortType.http);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5591) GatewayReceiverImpl.start() retry logic is dependent on JDK's underlying C runtime
Sean Goller created GEODE-5591: -- Summary: GatewayReceiverImpl.start() retry logic is dependent on JDK's underlying C runtime Key: GEODE-5591 URL: https://issues.apache.org/jira/browse/GEODE-5591 Project: Geode Issue Type: Bug Components: wan Reporter: Sean Goller org/apache/geode/internal/cache/wan/GatewayReceiverImpl.java:66 denotes a string comparison that relies on the specific C runtime that the JDK is run on top of. This code will misbehave on Alpine Linux (A popular linux distribution for containers) because it is based on the musl libc, not the GNU libc. The intent of the code is to throw an exception if the receiver cannot bind to the requested address. This will not occur if the JDK is compiled against musl libc. As an aside, the entire retry logic seems suspicious as it only retries in situations that are static and should not change, so the reason for the code should be re-evaluated and made more robust and not dependent on native os information. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5591) GatewayReceiverImpl.start() retry logic is dependent on JDK's underlying C runtime
[
https://issues.apache.org/jira/browse/GEODE-5591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Goller updated GEODE-5591:
---
Description:
{{org/apache/geode/internal/cache/wan/GatewayReceiverImpl.java:66}} denotes a
string comparison that relies on the specific C runtime that the JDK is run on
top of. This code will misbehave on Alpine Linux (A popular linux distribution
for containers) because it is based on the musl libc, not the GNU libc. The
intent of the code is to throw an exception if the receiver cannot bind to the
requested address. This will not occur if the JDK is compiled against musl
libc. As an aside, the entire retry logic seems suspicious as it only retries
in situations that are static and should not change, so the reason for the code
should be re-evaluated and made more robust and not dependent on native os
information. (was:
org/apache/geode/internal/cache/wan/GatewayReceiverImpl.java:66 denotes a
string comparison that relies on the specific C runtime that the JDK is run on
top of. This code will misbehave on Alpine Linux (A popular linux distribution
for containers) because it is based on the musl libc, not the GNU libc. The
intent of the code is to throw an exception if the receiver cannot bind to the
requested address. This will not occur if the JDK is compiled against musl
libc. As an aside, the entire retry logic seems suspicious as it only retries
in situations that are static and should not change, so the reason for the code
should be re-evaluated and made more robust and not dependent on native os
information.)
> GatewayReceiverImpl.start() retry logic is dependent on JDK's underlying C
> runtime
> --
>
> Key: GEODE-5591
> URL: https://issues.apache.org/jira/browse/GEODE-5591
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Sean Goller
>Priority: Major
>
> {{org/apache/geode/internal/cache/wan/GatewayReceiverImpl.java:66}} denotes a
> string comparison that relies on the specific C runtime that the JDK is run
> on top of. This code will misbehave on Alpine Linux (A popular linux
> distribution for containers) because it is based on the musl libc, not the
> GNU libc. The intent of the code is to throw an exception if the receiver
> cannot bind to the requested address. This will not occur if the JDK is
> compiled against musl libc. As an aside, the entire retry logic seems
> suspicious as it only retries in situations that are static and should not
> change, so the reason for the code should be re-evaluated and made more
> robust and not dependent on native os information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5394) ClientServerMiscBCDUnitTest.testRegionClose failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-5394:
Assignee: (was: Dan Smith)
> ClientServerMiscBCDUnitTest.testRegionClose failed in CI
>
>
> Key: GEODE-5394
> URL: https://issues.apache.org/jira/browse/GEODE-5394
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: pull-request-available, swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.html
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This test failed in a recent CI run on
> 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
>
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
> testRegionClose[3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest$$Lambda$111/993337154.run
> in VM 2 running on Host fe6abf8a5e6f with 5 VMs
> Caused by:
> java.lang.AssertionError: Event never occurred after 4 ms: null
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3839) log warning when --cache-xml-file is used with cluster config
[
https://issues.apache.org/jira/browse/GEODE-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581821#comment-16581821
]
ASF subversion and git services commented on GEODE-3839:
Commit 152701b4f51b1a6f00179327e2e72df046a85e00 in geode's branch
refs/heads/develop from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=152701b ]
GEODE-3839: Warning when cache xml is used (#2271)
* Additional logs added when cache-xml file is used in start server
gfsh command.
* A warning is logged mentioning that cluster config will take
precedence over the cache-xml file provided in the command.
* start server command help updated with the above information.
> log warning when --cache-xml-file is used with cluster config
> -
>
> Key: GEODE-3839
> URL: https://issues.apache.org/jira/browse/GEODE-3839
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When a server started using {{gfsh>start server --cache-xml-file=file.xml}}
> the contents of cache.xml are overridden with contents of cluster config. For
> example:
> * When I specify --server-port=0 the default cache server port is used. An
> ephemeral port is never created.
> * Changing a region type from REPLICATE (cluster config) to PARTITION
> (cache.xml) retains the region as REPLICATE.
> * Changing the persistence mode of a region retains the original setting;
> i.e. what is set in cluster config.
> When a user tries to start a server using cache.xml file, we should log a
> warning message saying that cluster xml is going to take precedence over
> contents of cache.xml. We should also change the gfsh help message to reflect
> this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-3839) log warning when --cache-xml-file is used with cluster config
[
https://issues.apache.org/jira/browse/GEODE-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun closed GEODE-3839.
--
> log warning when --cache-xml-file is used with cluster config
> -
>
> Key: GEODE-3839
> URL: https://issues.apache.org/jira/browse/GEODE-3839
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When a server started using {{gfsh>start server --cache-xml-file=file.xml}}
> the contents of cache.xml are overridden with contents of cluster config. For
> example:
> * When I specify --server-port=0 the default cache server port is used. An
> ephemeral port is never created.
> * Changing a region type from REPLICATE (cluster config) to PARTITION
> (cache.xml) retains the region as REPLICATE.
> * Changing the persistence mode of a region retains the original setting;
> i.e. what is set in cluster config.
> When a user tries to start a server using cache.xml file, we should log a
> warning message saying that cluster xml is going to take precedence over
> contents of cache.xml. We should also change the gfsh help message to reflect
> this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3839) log warning when --cache-xml-file is used with cluster config
[
https://issues.apache.org/jira/browse/GEODE-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun resolved GEODE-3839.
Resolution: Fixed
Fix Version/s: 1.7.0
> log warning when --cache-xml-file is used with cluster config
> -
>
> Key: GEODE-3839
> URL: https://issues.apache.org/jira/browse/GEODE-3839
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When a server started using {{gfsh>start server --cache-xml-file=file.xml}}
> the contents of cache.xml are overridden with contents of cluster config. For
> example:
> * When I specify --server-port=0 the default cache server port is used. An
> ephemeral port is never created.
> * Changing a region type from REPLICATE (cluster config) to PARTITION
> (cache.xml) retains the region as REPLICATE.
> * Changing the persistence mode of a region retains the original setting;
> i.e. what is set in cluster config.
> When a user tries to start a server using cache.xml file, we should log a
> warning message saying that cluster xml is going to take precedence over
> contents of cache.xml. We should also change the gfsh help message to reflect
> this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5587) Randomize internal http service working directory
[
https://issues.apache.org/jira/browse/GEODE-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581863#comment-16581863
]
ASF subversion and git services commented on GEODE-5587:
Commit f0feda4c0032e5675a8d000571f57a9446888a54 in geode's branch
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f0feda4 ]
GEODE-5587: Randomize HTTP service working directory (#2333)
> Randomize internal http service working directory
> -
>
> Key: GEODE-5587
> URL: https://issues.apache.org/jira/browse/GEODE-5587
> Project: Geode
> Issue Type: Bug
> Components: pulse, rest (admin), rest (dev)
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When starting the http service a given webapp is extracted into a working
> directory of the form: {{__}}. As part of shutdown this
> directory is cleaned up. However the directory is only completely removed
> when the JVM exits.
> Occasionally subsequent tests will request to use the same port. This results
> in the same working directory being used. On Windows this will fail as the
> directory does not let itself be cleaned up before the webapp is redeployed
> to the same location as before.
> We can randomize the working directory a bit more by adding a short sequence
> of random chars as part of the directory name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5248) The gfsh list gateways command can show non-0 Sender Count when there are no senders connected
[
https://issues.apache.org/jira/browse/GEODE-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581895#comment-16581895
]
ASF subversion and git services commented on GEODE-5248:
Commit 5e73f062a1fca05bb9002f7a7ef9ad8b9265e49f in geode's branch
refs/heads/develop from Juan Jose Ramos Cassella
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5e73f06 ]
GEODE-5248: Fixes in GatewayReceiverMBeanBridge
The class `GatewayReceiverMBeanBridge` uses the `MBeanStatsMonitor` to
retrieve the amount of senders currently connected. This statistic
tends to be out of date and heavily depends on the `HostStatSampler`
class to run periodically and update the data. Whenever a receiver is
stopped its stats are also closed and, as such, the
`clientConnectionCount` is not updated anymore, resulting in a wrong
gateway-sender connected count reported.
- Fixed some minor warnings.
- Added tests to verify the accuracy of the current gateway-senders
connected.
- Renamed `WanCommandListDUnitTest` to `ListGatewaysCommandDUnitTest`.
- Modified the `GatewayReceiverMBeanBridge` to retrieve the current
client connection count from the underlying acceptor instead of
the `MBeanStatsMonitor` class.
> The gfsh list gateways command can show non-0 Sender Count when there are no
> senders connected
> --
>
> Key: GEODE-5248
> URL: https://issues.apache.org/jira/browse/GEODE-5248
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> With three members in each site, the gfsh list gateways command shows
> something like this for the receiving site members:
> {noformat}
> Member | Port | Sender Count | Senders Connected
> - | | |
> ---
> 192.168.2.13(ny-1:90963):1026 | 5317 | 8 |
> 192.168.2.13(ln-1:91017):1029, 192.168.2.13(ln-2:91027):1030,
> 192.168.2.13(ln-3:91037):1031
> 192.168.2.13(ny-2:90979):1027 | 5232 | 8 |
> 192.168.2.13(ln-1:91017):1029, 192.168.2.13(ln-3:91037):1031,
> 192.168.2.13(ln-2:91027):1030
> 192.168.2.13(ny-3:90996):1028 | 5403 | 8 |
> 192.168.2.13(ln-1:91017):1029, 192.168.2.13(ln-2:91027):1030,
> 192.168.2.13(ln-3:91037):1031
> {noformat}
> If two of the receivers are stopped like this then the senders will connect
> to the remaining receiver:
> {noformat}
> stop gateway-receiver --member=ny-1
> Member | Result | Message
> - | -- |
> --
> 192.168.2.13(ny-1:90963):1026 | OK | GatewayReceiver is stopped on member
> 192.168.2.13(ny-1:90963):1026
> stop gateway-receiver --member=ny-2
> Member | Result | Message
> - | -- |
> --
> 192.168.2.13(ny-2:90979):1027 | OK | GatewayReceiver is stopped on member
> 192.168.2.13(ny-2:90979):1027
> {noformat}
> The list gateways command for the receiving site will show all the senders
> connected to the one remaining receiver like:
> {noformat}
> Member | Port | Sender Count | Senders Connected
> - | | |
> ---
> 192.168.2.13(ny-1:90963):1026 | 5317 | 8 |
> 192.168.2.13(ny-2:90979):1027 | 5232 | 8 |
> 192.168.2.13(ny-3:90996):1028 | 5403 | 18 |
> 192.168.2.13(ln-1:91017):1029, 192.168.2.13(ln-2:91027):1030,
> 192.168.2.13(ln-3:91037):1031
> {noformat}
> But it doesn't 0 out the Sender Count for the two members whose receiver was
> stopped. It still shows 8 even though senders are no longer connected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5530) Extract shared test code from test in to frameworks
[
https://issues.apache.org/jira/browse/GEODE-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581953#comment-16581953
]
ASF subversion and git services commented on GEODE-5530:
Commit aadc520cf36f5714ce976a7d0f965a9b436483c1 in geode's branch
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=aadc520 ]
GEODE-5530 Refactors shared test source between geode-web and geode-core.
(#2325)
Co-authored-by: Robert Houghton
Co-authored-by: Jacob Barrett
> Extract shared test code from test in to frameworks
> ---
>
> Key: GEODE-5530
> URL: https://issues.apache.org/jira/browse/GEODE-5530
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: pull-request-available
> Time Spent: 8h 20m
> Remaining Estimate: 0h
>
> Many tests between modules share code. Move this code into common frameworks,
> {{geode-junit}} and {{geode-dunit}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5530) Extract shared test code from test in to frameworks
[
https://issues.apache.org/jira/browse/GEODE-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581966#comment-16581966
]
ASF subversion and git services commented on GEODE-5530:
Commit 29ef1880109b515c6e6de219bca6810908823767 in geode's branch
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=29ef1880 ]
GEODE-5530: Removes geode-web-test since it is empty.
> Extract shared test code from test in to frameworks
> ---
>
> Key: GEODE-5530
> URL: https://issues.apache.org/jira/browse/GEODE-5530
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: pull-request-available
> Time Spent: 8h 20m
> Remaining Estimate: 0h
>
> Many tests between modules share code. Move this code into common frameworks,
> {{geode-junit}} and {{geode-dunit}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5530) Extract shared test code from test in to frameworks
[
https://issues.apache.org/jira/browse/GEODE-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581999#comment-16581999
]
ASF subversion and git services commented on GEODE-5530:
Commit 00fd7b2355244b2506bd530250880b561540f5ac in geode's branch
refs/heads/develop from [~rhoughton]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=00fd7b2 ]
GEODE-5530 move common pulse test framework into new sub-project
Co-authored-by: Robert Houghton
Co-authored-by: Jacob Barrett
> Extract shared test code from test in to frameworks
> ---
>
> Key: GEODE-5530
> URL: https://issues.apache.org/jira/browse/GEODE-5530
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Reporter: Jacob S. Barrett
>Priority: Major
> Labels: pull-request-available
> Time Spent: 8h 20m
> Remaining Estimate: 0h
>
> Many tests between modules share code. Move this code into common frameworks,
> {{geode-junit}} and {{geode-dunit}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5579) `./gradlew :test` target should be able to be repeated without using `clean` or `--rerun-tasks`
[
https://issues.apache.org/jira/browse/GEODE-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582013#comment-16582013
]
ASF subversion and git services commented on GEODE-5579:
Commit 0283a68a7cc6e58489d5e78874dbe10d9ca4440e in geode's branch
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0283a68 ]
GEODE-5579: Add -PforceTest property to :test tasks (#2318)
* Auto-format whitespace adjustments.
* Streamline and Unify test facet configuration
* Separate exclusion of FlakyTest to own configuration block. *DO* run
FlakyTest on UI, Acceptance, and Upgrade tests.
> `./gradlew :test` target should be able to be repeated without using `clean`
> or `--rerun-tasks`
> ---
>
> Key: GEODE-5579
> URL: https://issues.apache.org/jira/browse/GEODE-5579
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The unit-test target {{:test}} is able to be UP-TO-DATE to reduce the time
> cost of {{:build}}. However, developers may wish to rerun {{:test}} without
> fully compiling and rebuilding the source, as would occur with both {{clean}}
> and {{--rerun-tasks}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
