[jira] [Created] (GEODE-7426) Integration tests segfault on MacOs with geode-native
Jacob Barrett created GEODE-7426: Summary: Integration tests segfault on MacOs with geode-native Key: GEODE-7426 URL: https://issues.apache.org/jira/browse/GEODE-7426 Project: Geode Issue Type: Bug Components: native client Reporter: Jacob Barrett A segfault occurs on MacOS when running any of the integration tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7426) Integration tests segfault on MacOs with geode-native
[ https://issues.apache.org/jira/browse/GEODE-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett reassigned GEODE-7426: Assignee: Jacob Barrett > Integration tests segfault on MacOs with geode-native > - > > Key: GEODE-7426 > URL: https://issues.apache.org/jira/browse/GEODE-7426 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > > A segfault occurs on MacOS when running any of the integration tests. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7425) Ability: can delete index in RESTAPI for Management
Gang Yan created GEODE-7425: --- Summary: Ability: can delete index in RESTAPI for Management Key: GEODE-7425 URL: https://issues.apache.org/jira/browse/GEODE-7425 Project: Geode Issue Type: New Feature Components: management, rest (admin) Reporter: Gang Yan # WHAT 1. endpoint: [DELETE] `management/v1/indexes` 1. parameter: "name", "region", "group" 1. expected result: delete index as specified parameters -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7424) Ability: can create index in RESTAPI for Management
Gang Yan created GEODE-7424: --- Summary: Ability: can create index in RESTAPI for Management Key: GEODE-7424 URL: https://issues.apache.org/jira/browse/GEODE-7424 Project: Geode Issue Type: New Feature Components: management, rest (admin) Reporter: Gang Yan # WHAT 1. endpoint: [POST] `management/v1/indexes` 1. parameter: "name", "expression", "region", "type", "group" 1. expected result: create index by specified parameters -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7423) Ability: can run "configure PDX" [phase1]
Gang Yan created GEODE-7423:
---
Summary: Ability: can run "configure PDX" [phase1]
Key: GEODE-7423
URL: https://issues.apache.org/jira/browse/GEODE-7423
Project: Geode
Issue Type: New Feature
Components: management, rest (admin)
Reporter: Gang Yan
### Why
phase0 and phase1 for PCC
phase2 to level up usability of GemFire PDX
phase0: support configure pdx, "--read-serialized" and "--disk-store"
**phase1: support "ignore-unread-fields" , "auto-serializable-classes" and
"portable-auto-serializable-classes"**
phase2: can run "GFSH configure PDX" when data members are running without
restart
**Notes:**
[1]url
"geode-management/v2/configurations/pdx"
[2]result
```
diskStore: (the specified diskstore)
readSerialized: true
ignoreUnreadFields: false
serializer:
{
"name":"autoSerializer", --> on the future, the customer can specify his own
class
"portable": true|false,
"patterns":""
}
```
[3] request body 1:
```
{
diskStore: (the specified diskstore),
readSerialized: true,
ignoreUnreadFields: false,
serializer:
{
"name":"autoSerializer", --> on the future, the customer can specify his own
class
"portable": true|false,
"patterns":""
}
}
```
[3] request body 2:
```
{
persistent: true, --> diskstore:“DEFAULT” is used
readSerialized: true,
ignoreUnreadFields: false,
serializer:
{
"name":"autoSerializer",
"portable": true|false,
"patterns":""
}
}
```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7422) ReplicatedGetBenchmark with SSL is failing intermittently
Jacob Barrett created GEODE-7422: Summary: ReplicatedGetBenchmark with SSL is failing intermittently Key: GEODE-7422 URL: https://issues.apache.org/jira/browse/GEODE-7422 Project: Geode Issue Type: Bug Components: benchmarks Reporter: Jacob Barrett org.apache.geode.benchmark.tests.ReplicatedGetBenchmark fails intermittently with SSL enabled. The put and get benchmarks show consistently lower performance with SSL enabled between high-water mark and HEAD of develop. Current high-water: 42a0d0d54d5e307837d0b12d87bb288ac7c2493e Current HEAD: cf1aef105853df4455fc19301aa233a99443071d [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/671#L5dbce136:1874] [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/643#L5d980631:1872] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7406) PartitionBenchmarks failures
[
https://issues.apache.org/jira/browse/GEODE-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett resolved GEODE-7406.
--
Fix Version/s: 1.12.0
Resolution: Resolved
> PartitionBenchmarks failures
>
>
> Key: GEODE-7406
> URL: https://issues.apache.org/jira/browse/GEODE-7406
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Mark Hanson
>Assignee: Helena Bales
>Priority: Major
> Fix For: 1.12.0
>
>
> {noformat}
> org.apache.geode.benchmark.tests.ReplicatedPutBenchmark > run() FAILED
> 09:35:17java.util.concurrent.CompletionException:
> java.lang.RuntimeException: java.util.concurrent.CompletionException:
> org.apache.geode.ToDataException: PdxSerializer failed when calling toData on
> class benchmark.geode.data.Portfolio
> 09:35:17
> 09:35:17Caused by:
> 09:35:17java.lang.RuntimeException:
> java.util.concurrent.CompletionException: org.apache.geode.ToDataException:
> PdxSerializer failed when calling toData on class
> benchmark.geode.data.Portfolio
> 09:35:17
> 09:35:17Caused by:
> 09:35:17java.util.concurrent.CompletionException:
> org.apache.geode.ToDataException: PdxSerializer failed when calling toData on
> class benchmark.geode.data.Portfolio
> 09:35:17
> 09:35:17Caused by:
> 09:35:17org.apache.geode.ToDataException: PdxSerializer
> failed when calling toData on class benchmark.geode.data.Portfolio
> 09:35:17
> 09:35:17Caused by:
> 09:35:17org.apache.geode.pdx.PdxSerializationException:
> Serialization error on field aDay for class benchmark.geode.data.Portfolio
> 09:35:17
> 09:35:17Caused by:
> 09:35:17
> org.apache.geode.cache.client.ServerConnectivityException: Pool unexpected
> socket timed out on client connection=Pooled Connection to
> ip-172-31-33-59.us-west-2.compute.internal:41313: Connection[DESTROYED]
> attempt=2). Server unreachable: could not connect after 2 attempts
> 09:36:48
> 09:36:48org.apache.geode.benchmark.tests.ReplicatedGetBenchmark > run() FAILED
> 09:36:48java.util.concurrent.CompletionException:
> java.lang.RuntimeException: java.util.concurrent.CompletionException:
> org.apache.geode.ToDataException: PdxSerializer failed when calling toData on
> class benchmark.geode.data.Portfolio
> 09:36:48
> 09:36:48Caused by:
> 09:36:48java.lang.RuntimeException:
> java.util.concurrent.CompletionException: org.apache.geode.ToDataException:
> PdxSerializer failed when calling toData on class
> benchmark.geode.data.Portfolio
> 09:36:48
> 09:36:48Caused by:
> 09:36:48java.util.concurrent.CompletionException:
> org.apache.geode.ToDataException: PdxSerializer failed when calling toData on
> class benchmark.geode.data.Portfolio
> 09:36:48
> 09:36:48Caused by:
> 09:36:48org.apache.geode.ToDataException: PdxSerializer
> failed when calling toData on class benchmark.geode.data.Portfolio
> 09:36:48
> 09:36:48Caused by:
> 09:36:48org.apache.geode.pdx.PdxSerializationException:
> Serialization error on field aDay for class benchmark.geode.data.Portfolio
> 09:36:48
> 09:36:48Caused by:
> 09:36:48
> org.apache.geode.cache.client.ServerConnectivityException: Pool unexpected
> socket timed out on client connection=Pooled Connection to
> ip-172-31-42-206.us-west-2.compute.internal:42615: Connection[DESTROYED]
> attempt=2). Server unreachable: could not connect after 2 attempts
> 09:38:31
> 09:38:31org.apache.geode.benchmark.tests.PartitionedGetBenchmark > run()
> FAILED
> 09:38:31java.util.concurrent.CompletionException:
> java.lang.RuntimeException: java.util.concurrent.CompletionException:
> org.apache.geode.cache.client.ServerOperationException: remote server on
> ip-172-31-38-145(15378:loner):35558:3c62312d: Region /region putAll at server
> applied partial keys due to exception.
> 09:38:31
> 09:38:31Caused by:
> 09:38:31java.lang.RuntimeException:
> java.util.concurrent.CompletionException:
> org.apache.geode.cache.client.ServerOperationException: remote server on
> ip-172-31-38-145(15378:loner):35558:3c62312d: Region /region putAll at server
> applied partial keys due to exception.
> 09:38:31
> 09:38:31Caused by:
> 09:38:31java.util.concurrent.CompletionException:
> org.apache.geode.cache.client.ServerOperationException: remote server on
> ip-172-31-38-145(15378:loner):35558:3c62312d: Region /region putAll at server
> applied partial keys due to exception.
> 09:38:31
> 09:38:31Caused by:
> 09:38:31
>
[jira] [Commented] (GEODE-7269) PartitionedPutAllBenchmark failure
[
https://issues.apache.org/jira/browse/GEODE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969652#comment-16969652
]
Jacob Barrett commented on GEODE-7269:
--
Please drop a link to any additional CI runs that have this failure and restart
the benchmarks.
> PartitionedPutAllBenchmark failure
> ---
>
> Key: GEODE-7269
> URL: https://issues.apache.org/jira/browse/GEODE-7269
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Mark Hanson
>Assignee: Jacob Barrett
>Priority: Major
>
> Benchmarks failed in
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/607]
>
> {noformat}
> > Task :harness:analyzeRun
> Running analyzer
> Comparing test result at
> /tmp/build/2ea77113/results/benchmarks-apache-develop-main-Benchmark-607-98877/branch/benchmarks_20191002113518
> to baseline at
> /tmp/build/2ea77113/results/benchmarks-apache-develop-main-Benchmark-607-98877/baseline/benchmarks_20191002092613
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark
> average ops/second Baseline:165126.55 Test:163322.19
> Difference: -1.1%
>ops/second standard error Baseline: 481.54 Test: 394.45
> Difference: -18.1%
>ops/second standard deviation Baseline: 8326.61 Test: 6832.03
> Difference: -17.9%
> YS 99th percentile latency Baseline: 1906.00 Test: 1905.00
> Difference: -0.1%
> median latency Baseline:633855.00 Test:630271.00
> Difference: -0.6%
> 90th percentile latency Baseline: 1326079.00 Test: 1367039.00
> Difference: +3.1%
> 99th percentile latency Baseline: 4591615.00 Test: 4644863.00
> Difference: +1.2%
>99.9th percentile latency Baseline: 1535.00 Test: 16809983.00
> Difference: +9.4%
> average latency Baseline:871151.53 Test:880810.13
> Difference: +1.1%
> latency standard deviation Baseline: 1050482.32 Test: 1100814.13
> Difference: +4.8%
> latency standard error Baseline: 149.28 Test: 157.30
> Difference: +5.4%
> org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark
> average ops/second Baseline:459731.05 Test:453392.16
> Difference: -1.4%
>ops/second standard error Baseline: 394.19 Test: 332.85
> Difference: -15.6%
>ops/second standard deviation Baseline: 6816.12 Test: 5765.11
> Difference: -15.4%
> YS 99th percentile latency Baseline: 1405.00 Test: 1405.00
> Difference: +0.0%
> median latency Baseline:449791.00 Test:459519.00
> Difference: +2.2%
> 90th percentile latency Baseline:943615.00 Test:961023.00
> Difference: +1.8%
> 99th percentile latency Baseline: 3616767.00 Test: 3614719.00
> Difference: -0.1%
>99.9th percentile latency Baseline: 10559487.00 Test: 10551295.00
> Difference: -0.1%
> average latency Baseline:625412.03 Test:634121.49
> Difference: +1.4%
> latency standard deviation Baseline:788269.89 Test:788318.28
> Difference: +0.0%
> latency standard error Baseline:67.13 Test:67.60
> Difference: +0.7%
> org.apache.geode.benchmark.tests.PartitionedGetBenchmark
> average ops/second Baseline:841000.72 Test:828146.58
> Difference: -1.5%
>ops/second standard error Baseline: 558.63 Test: 507.87
> Difference: -9.1%
>ops/second standard deviation Baseline: 9659.55 Test: 8781.92
> Difference: -9.1%
> YS 99th percentile latency Baseline: 806.00 Test: 805.00
> Difference: -0.1%
> median latency Baseline:332287.00 Test:339967.00
> Difference: +2.3%
> 90th percentile latency Baseline:443391.00 Test:452351.00
> Difference: +2.0%
> 99th percentile latency Baseline: 2672639.00 Test: 2662399.00
> Difference: -0.4%
>99.9th percentile latency Baseline: 8089599.00 Test: 7974911.00
> Difference: -1.4%
> average latency Baseline:426878.72 Test:433532.06
> Difference: +1.6%
> latency standard deviation Baseline:546763.26 Test:542115.50
> Difference: -0.9%
> latency standard error Baseline:34.43 Test:
[jira] [Created] (GEODE-7421) Ability: can deploy jar by REST API for Management
Gang Yan created GEODE-7421: --- Summary: Ability: can deploy jar by REST API for Management Key: GEODE-7421 URL: https://issues.apache.org/jira/browse/GEODE-7421 Project: Geode Issue Type: New Feature Components: management, rest (admin) Reporter: Gang Yan # WHAT 1. can deploy jar file by REST API 2. from feature point , it will cover current 'gfsh deploy' 3. if two files have same file name, the later wins 4. can recognize version pattern. "filename-version[-label].jar" . filename=[a-zA-Z/-]+, not single "-", not end with "-" version=[0-9/.]*, not single ".", not end with "." label=[a-zA-Z0-9]* such as: -is a later version of , will deploy. -is a same version of , the later wins -is a same version of , the later wins -is an earlier version of , will block it. 5. if there is a version part in the file name, we will deploy them without append "#1" part to the file name 6. can accept "group" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7415) Doc Links Broken
[
https://issues.apache.org/jira/browse/GEODE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes resolved GEODE-7415.
Fix Version/s: 1.12.0
Resolution: Fixed
> Doc Links Broken
>
>
> Key: GEODE-7415
> URL: https://issues.apache.org/jira/browse/GEODE-7415
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.12.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Building the docs, either manually or with the
> {{/dev-tools/docker/docs/build-docs.sh}} script, finishes with the *_Found
> broken links!_* message.
> Attempts to click on any link afterwards while viewing the docs ends up in a
> blank page with the message *_Not Found_*.
> The problem is that, after cutting the new _1.11.0_ release and modifying the
> {{geode-book/config.yml}} file, the {{directory}} property still refers to
> _111_ while the rest of the properties refer to _112_.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7419) Complete info about geode-native integration tests
[ https://issues.apache.org/jira/browse/GEODE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-7419: Labels: pull-request-available (was: ) > Complete info about geode-native integration tests > -- > > Key: GEODE-7419 > URL: https://issues.apache.org/jira/browse/GEODE-7419 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Complete info about the two sets of geode-native integration tests, and the > preference of implementing new tests using GoogleTest. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7415) Doc Links Broken
[
https://issues.apache.org/jira/browse/GEODE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969603#comment-16969603
]
ASF subversion and git services commented on GEODE-7415:
Commit cf1aef105853df4455fc19301aa233a99443071d in geode's branch
refs/heads/develop from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cf1aef1 ]
GEODE-7415: Fix version variable for docs (#4293)
* GEODE-7415: Fix version variable in documentation
> Doc Links Broken
>
>
> Key: GEODE-7415
> URL: https://issues.apache.org/jira/browse/GEODE-7415
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Building the docs, either manually or with the
> {{/dev-tools/docker/docs/build-docs.sh}} script, finishes with the *_Found
> broken links!_* message.
> Attempts to click on any link afterwards while viewing the docs ends up in a
> blank page with the message *_Not Found_*.
> The problem is that, after cutting the new _1.11.0_ release and modifying the
> {{geode-book/config.yml}} file, the {{directory}} property still refers to
> _111_ while the rest of the properties refer to _112_.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7415) Doc Links Broken
[
https://issues.apache.org/jira/browse/GEODE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969602#comment-16969602
]
ASF subversion and git services commented on GEODE-7415:
Commit cf1aef105853df4455fc19301aa233a99443071d in geode's branch
refs/heads/develop from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cf1aef1 ]
GEODE-7415: Fix version variable for docs (#4293)
* GEODE-7415: Fix version variable in documentation
> Doc Links Broken
>
>
> Key: GEODE-7415
> URL: https://issues.apache.org/jira/browse/GEODE-7415
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Building the docs, either manually or with the
> {{/dev-tools/docker/docs/build-docs.sh}} script, finishes with the *_Found
> broken links!_* message.
> Attempts to click on any link afterwards while viewing the docs ends up in a
> blank page with the message *_Not Found_*.
> The problem is that, after cutting the new _1.11.0_ release and modifying the
> {{geode-book/config.yml}} file, the {{directory}} property still refers to
> _111_ while the rest of the properties refer to _112_.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7420) PartitionedIndexedQueryBenchmark failed
Eric Shu created GEODE-7420:
---
Summary: PartitionedIndexedQueryBenchmark failed
Key: GEODE-7420
URL: https://issues.apache.org/jira/browse/GEODE-7420
Project: Geode
Issue Type: Bug
Components: benchmarks
Reporter: Eric Shu
Benchmarks failed in
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/Benchmark/builds/670
{noformat}
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithArgumentsBenchmark
average ops/second Baseline:268375.49 Test:272615.85
Difference: +1.6%
ops/second standard error Baseline: 685.23 Test: 776.55
Difference: +13.3%
ops/second standard deviation Baseline: 11848.76 Test: 13427.87
Difference: +13.3%
YS 99th percentile latency Baseline: 1905.00 Test: 1904.00
Difference: -0.1%
median latency Baseline:731135.00 Test:740351.00
Difference: +1.3%
90th percentile latency Baseline: 1391615.00 Test: 1360895.00
Difference: -2.2%
99th percentile latency Baseline: 319.00 Test: 8429567.00
Difference: -5.2%
99.9th percentile latency Baseline: 25477119.00 Test: 25165823.00
Difference: -1.2%
average latency Baseline: 1071449.63 Test: 1054730.69
Difference: -1.6%
latency standard deviation Baseline: 1745180.39 Test: 1699559.12
Difference: -2.6%
latency standard error Baseline: 194.54 Test: 187.97
Difference: -3.4%
org.apache.geode.benchmark.tests.PartitionedFunctionExecutionWithFiltersBenchmark
average ops/second Baseline:328925.71 Test:342909.21
Difference: +4.3%
ops/second standard error Baseline: 417.23 Test: 435.36
Difference: +4.3%
ops/second standard deviation Baseline: 7214.58 Test: 7528.04
Difference: +4.3%
YS 99th percentile latency Baseline: 20003.00 Test: 20004.00
Difference: +0.0%
median latency Baseline: 1239039.00 Test: 1175551.00
Difference: -5.1%
90th percentile latency Baseline: 2799615.00 Test: 2682879.00
Difference: -4.2%
99th percentile latency Baseline: 12869631.00 Test: 12607487.00
Difference: -2.0%
99.9th percentile latency Baseline: 44466175.00 Test: 42565631.00
Difference: -4.3%
average latency Baseline: 1749256.81 Test: 1677443.51
Difference: -4.1%
latency standard deviation Baseline: 3061797.44 Test: 3044573.18
Difference: -0.6%
latency standard error Baseline: 308.32 Test: 300.25
Difference: -2.6%
org.apache.geode.benchmark.tests.PartitionedGetBenchmark
average ops/second Baseline:987349.37 Test:985697.58
Difference: -0.2%
ops/second standard error Baseline: 1239.47 Test: 1186.89
Difference: -4.2%
ops/second standard deviation Baseline: 21432.43 Test: 20523.24
Difference: -4.2%
YS 99th percentile latency Baseline: 1201.00 Test: 1202.00
Difference: +0.1%
median latency Baseline:589823.00 Test:585215.00
Difference: -0.8%
90th percentile latency Baseline:889855.00 Test:903167.00
Difference: +1.5%
99th percentile latency Baseline: 1374207.00 Test: 1445887.00
Difference: +5.2%
99.9th percentile latency Baseline: 25460735.00 Test: 25100287.00
Difference: -1.4%
average latency Baseline:727486.35 Test:728837.38
Difference: +0.2%
latency standard deviation Baseline: 1544152.30 Test: 1543259.87
Difference: -0.1%
latency standard error Baseline:89.74 Test:89.77
Difference: +0.0%
org.apache.geode.benchmark.tests.PartitionedIndexedQueryBenchmark
average ops/second Baseline: 32309.71 Test: 30390.65
Difference: -5.9%
ops/second standard error Baseline:50.85 Test:37.40
Difference: -26.4%
ops/second standard deviation Baseline: 879.21 Test: 646.71
Difference: -26.4%
YS 99th percentile latency Baseline: 20096.43 Test: 20096.09
Difference: -0.0%
median latency Baseline: 8962047.00 Test: 8634367.00
Difference: -3.7%
90th percentile latency Baseline: 35323903.00 Test: 49414143.00
Difference: +39.9%
99th percentile latency Baseline: 216399871.00 Test: 114360319.00
Difference: -47.2%
99.9th percentile latency Baseline: 258473983.00 Test: 230948863.00
Difference: -10.6%
[jira] [Updated] (GEODE-7419) Complete info about geode-native integration tests
[ https://issues.apache.org/jira/browse/GEODE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-7419: Priority: Minor (was: Major) > Complete info about geode-native integration tests > -- > > Key: GEODE-7419 > URL: https://issues.apache.org/jira/browse/GEODE-7419 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > > Complete info about the two sets of geode-native integration tests, and the > preference of implementing new tests using GoogleTest. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7419) Complete info about geode-native integration tests
[ https://issues.apache.org/jira/browse/GEODE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-7419: --- Assignee: Alberto Bustamante Reyes > Complete info about geode-native integration tests > -- > > Key: GEODE-7419 > URL: https://issues.apache.org/jira/browse/GEODE-7419 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > Complete info about the two sets of geode-native integration tests, and the > preference of implementing new tests using GoogleTest. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7419) Complete info about geode-native integration tests
Alberto Bustamante Reyes created GEODE-7419: --- Summary: Complete info about geode-native integration tests Key: GEODE-7419 URL: https://issues.apache.org/jira/browse/GEODE-7419 Project: Geode Issue Type: Improvement Components: native client Reporter: Alberto Bustamante Reyes Complete info about the two sets of geode-native integration tests, and the preference of implementing new tests using GoogleTest. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7418) Crash in deserialization of JSON Pdx value when PdxReadSerialized=false
Blake Bender created GEODE-7418: --- Summary: Crash in deserialization of JSON Pdx value when PdxReadSerialized=false Key: GEODE-7418 URL: https://issues.apache.org/jira/browse/GEODE-7418 Project: Geode Issue Type: Bug Components: native client Reporter: Blake Bender As a developer, I should be able to put and get JSON Pdx values in a region without any "extra effort" such as registering types or setting PdxReadSerialized to true when creating my cache. Currently if I do this, put a JSON value into a region, and attempt a get, NC will segfault attempting to create a PdxInstanceImpl. Steps to repro: * Build NC from the `*[pdxinstance_json_crash_repro|https://github.com/pdxcodemonkey/geode-native/tree/pdxinstance_json_crash_repro]`* branch of my (pdxcodemonkey) fork * Run NC integration test `PdxInstanceTest.testCreateJsonInstance` Expected result: * test passes Actual result: * test fails with a segfault in NC -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7417) CI checks do not trigger on geode-book changes
[ https://issues.apache.org/jira/browse/GEODE-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols reassigned GEODE-7417: --- Assignee: Owen Nichols > CI checks do not trigger on geode-book changes > -- > > Key: GEODE-7417 > URL: https://issues.apache.org/jira/browse/GEODE-7417 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > due to new branch protection rules, it is now impossible to submit geode-book > changes as the required checks will never fire > we should remove the exclusion so checks can run -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7417) CI checks do not trigger on geode-book changes
[ https://issues.apache.org/jira/browse/GEODE-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-7417. - Fix Version/s: 1.12.0 Resolution: Fixed > CI checks do not trigger on geode-book changes > -- > > Key: GEODE-7417 > URL: https://issues.apache.org/jira/browse/GEODE-7417 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > due to new branch protection rules, it is now impossible to submit geode-book > changes as the required checks will never fire > we should remove the exclusion so checks can run -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-6489) CI Failures with testDistributedDeadlock
[
https://issues.apache.org/jira/browse/GEODE-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-6489:
--
Assignee: Mark Hanson
> CI Failures with testDistributedDeadlock
>
>
> Key: GEODE-6489
> URL: https://issues.apache.org/jira/browse/GEODE-6489
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Lynn Hughes-Godfrey
>Assignee: Mark Hanson
>Priority: Major
>
> In an single CI run, we see 3 failures all related to testDistributedDeadlock:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> {noformat}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/469
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run
> in VM 1 running on Host ceb4d948b5be with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run
> in VM 1 running on Host ceb4d948b5be with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> 137 tests completed, 2 failed
> > Task :geode-web:distributedTest FAILED
> > Task :geode-core:distributedTest
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:201)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-results/distributedTest/1551833386/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-artifacts/1551833386/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0019.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7065) CI Failure in ShowDeadlockOverHttpDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-7065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-7065:
--
Assignee: Mark Hanson
> CI Failure in ShowDeadlockOverHttpDUnitTest
> ---
>
> Key: GEODE-7065
> URL: https://issues.apache.org/jira/browse/GEODE-7065
> Project: Geode
> Issue Type: Test
> Components: gfsh
>Reporter: Owen Nichols
>Assignee: Mark Hanson
>Priority: Major
>
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$64/2112888748.run
> in VM 1 running on Host 41a1a4d5dcf9 with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$64/2112888748.run
> in VM 1 running on Host 41a1a4d5dcf9 with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> 136 tests completed, 2 failed
> {noformat}
> see
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/974]
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0018/test-results/distributedTest/1565293755/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0018/test-artifacts/1565293755/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0018.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6616) Flaky: AutoConnectionSourceDUnitTest > testClientDynamicallyDropsStoppedLocator FAILED
[
https://issues.apache.org/jira/browse/GEODE-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969461#comment-16969461
]
Mark Hanson commented on GEODE-6616:
Mass Test Run failures
testClientDynamicallyDropsStoppedLocator
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1294
testClientDynamicallyDropsStoppedLocator
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1219
testClientDynamicallyDropsStoppedLocator
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1155
> Flaky: AutoConnectionSourceDUnitTest >
> testClientDynamicallyDropsStoppedLocator FAILED
> --
>
> Key: GEODE-6616
> URL: https://issues.apache.org/jira/browse/GEODE-6616
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Mark Hanson
>Priority: Minor
>
> Failed connection..
> {noformat}
> [vm3] [info 2019/04/09 06:48:44.919 UTC
> tid=0x20] Got result: EXCEPTION_OCCURRED
> [vm3] org.apache.geode.cache.client.ServerOperationException: remote server
> on 16f27a14ad79(255:loner):52816:5f2bdb00: : While performing a remote put
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:389)
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:313)
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp$PutOpImpl.attemptReadResponse(PutOp.java:454)
> [vm3] at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:387)
> [vm3] at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:289)
> [vm3] at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:351)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:908)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:172)
> [vm3] at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:130)
> [vm3] at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:792)
> [vm3] at
> org.apache.geode.cache.client.internal.PutOp.execute(PutOp.java:90)
> [vm3] at
> org.apache.geode.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:155)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.serverPut(LocalRegion.java:3070)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3222)
> [vm3] at
> org.apache.geode.internal.cache.map.RegionMapPut.invokeCacheWriter(RegionMapPut.java:230)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutIfPreconditionsSatisified(AbstractRegionMapPut.java:295)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutOnSynchronizedRegionEntry(AbstractRegionMapPut.java:282)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutOnRegionEntryInMap(AbstractRegionMapPut.java:273)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.addRegionEntryToMapAndDoPut(AbstractRegionMapPut.java:251)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPutRetryingIfNeeded(AbstractRegionMapPut.java:216)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doWithIndexInUpdateMode(AbstractRegionMapPut.java:198)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.doPut(AbstractRegionMapPut.java:180)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.runWhileLockedForCacheModification(AbstractRegionMapPut.java:119)
> [vm3] at
> org.apache.geode.internal.cache.map.RegionMapPut.runWhileLockedForCacheModification(RegionMapPut.java:150)
> [vm3] at
> org.apache.geode.internal.cache.map.AbstractRegionMapPut.put(AbstractRegionMapPut.java:169)
> [vm3] at
> org.apache.geode.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2044)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5695)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:162)
> [vm3] at
> org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5123)
> [vm3] at
>
[jira] [Commented] (GEODE-7417) CI checks do not trigger on geode-book changes
[ https://issues.apache.org/jira/browse/GEODE-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969460#comment-16969460 ] ASF subversion and git services commented on GEODE-7417: Commit 411bd30b713f262d065b97f7fa1fd4216547d0aa in geode's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=411bd30 ] GEODE-7417: never skip triggering of PR checks, since branch protection requires them always now (#4295) > CI checks do not trigger on geode-book changes > -- > > Key: GEODE-7417 > URL: https://issues.apache.org/jira/browse/GEODE-7417 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > due to new branch protection rules, it is now impossible to submit geode-book > changes as the required checks will never fire > we should remove the exclusion so checks can run -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6499) PersistentColocatedPartitionedRegionDUnitTest: Timed out waiting 60000 milliseconds for AsyncInvocation to complete.
[
https://issues.apache.org/jira/browse/GEODE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969459#comment-16969459
]
Mark Hanson commented on GEODE-6499:
And a few more from mass test runs...
testMultipleColocatedChildPRsMissingWithSequencedStart
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1442
testMultipleColocatedChildPRsMissingWithSequencedStart
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1305
testMultipleColocatedChildPRsMissingWithSequencedStart
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1272
> PersistentColocatedPartitionedRegionDUnitTest: Timed out waiting 6
> milliseconds for AsyncInvocation to complete.
>
>
> Key: GEODE-6499
> URL: https://issues.apache.org/jira/browse/GEODE-6499
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Attachments: PersistentColocatedPartitionedRegionDUnitTest.tgz
>
>
> {noformat}
>
> Task :geode-core:distributedTest
>
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest
> > testHierarchyOfColocatedChildPRsMissingGrandchild FAILED
> java.util.concurrent.TimeoutException: Timed out waiting 6 milliseconds
> for AsyncInvocation to complete.
> at
> org.apache.geode.test.dunit.AsyncInvocation.timeoutIfAlive(AsyncInvocation.java:462)
> at org.apache.geode.test.dunit.AsyncInvocation.get(AsyncInvocation.java:412)
> at
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.testHierarchyOfColocatedChildPRsMissingGrandchild(PersistentColocatedPartitionedRegionDUnitTest.java:979)
>
>
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest
> > testMultipleColocatedChildPRsMissingWithSequencedStart FAILED
> java.util.concurrent.TimeoutException: Timed out waiting 6 milliseconds
> for AsyncInvocation to complete.
> at
> org.apache.geode.test.dunit.AsyncInvocation.timeoutIfAlive(AsyncInvocation.java:462)
> at org.apache.geode.test.dunit.AsyncInvocation.get(AsyncInvocation.java:412)
> at
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.testMultipleColocatedChildPRsMissingWithSequencedStart(PersistentColocatedPartitionedRegionDUnitTest.java:865)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6499) PersistentColocatedPartitionedRegionDUnitTest: Timed out waiting 60000 milliseconds for AsyncInvocation to complete.
[
https://issues.apache.org/jira/browse/GEODE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969458#comment-16969458
]
Mark Hanson commented on GEODE-6499:
A few more occurrences from mass test runs.
testHierarchyOfColocatedChildPRsMissingGrandchild
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1305
testHierarchyOfColocatedChildPRsMissingGrandchild
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1272
testHierarchyOfColocatedChildPRsMissingGrandchild
https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1197
> PersistentColocatedPartitionedRegionDUnitTest: Timed out waiting 6
> milliseconds for AsyncInvocation to complete.
>
>
> Key: GEODE-6499
> URL: https://issues.apache.org/jira/browse/GEODE-6499
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Attachments: PersistentColocatedPartitionedRegionDUnitTest.tgz
>
>
> {noformat}
>
> Task :geode-core:distributedTest
>
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest
> > testHierarchyOfColocatedChildPRsMissingGrandchild FAILED
> java.util.concurrent.TimeoutException: Timed out waiting 6 milliseconds
> for AsyncInvocation to complete.
> at
> org.apache.geode.test.dunit.AsyncInvocation.timeoutIfAlive(AsyncInvocation.java:462)
> at org.apache.geode.test.dunit.AsyncInvocation.get(AsyncInvocation.java:412)
> at
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.testHierarchyOfColocatedChildPRsMissingGrandchild(PersistentColocatedPartitionedRegionDUnitTest.java:979)
>
>
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest
> > testMultipleColocatedChildPRsMissingWithSequencedStart FAILED
> java.util.concurrent.TimeoutException: Timed out waiting 6 milliseconds
> for AsyncInvocation to complete.
> at
> org.apache.geode.test.dunit.AsyncInvocation.timeoutIfAlive(AsyncInvocation.java:462)
> at org.apache.geode.test.dunit.AsyncInvocation.get(AsyncInvocation.java:412)
> at
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.testMultipleColocatedChildPRsMissingWithSequencedStart(PersistentColocatedPartitionedRegionDUnitTest.java:865)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-5407) CI failure: JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator and testLocalBeans_MaintainServerAndCrashLocator
[ https://issues.apache.org/jira/browse/GEODE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reassigned GEODE-5407: -- Assignee: Mark Hanson > CI failure: > JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator > and testLocalBeans_MaintainServerAndCrashLocator > - > > Key: GEODE-5407 > URL: https://issues.apache.org/jira/browse/GEODE-5407 > Project: Geode > Issue Type: Bug > Components: ci, jmx, management >Reporter: Jinmei Liao >Assignee: Mark Hanson >Priority: Major > Labels: flaky, swat > Attachments: Test results - Class > org.apache.geode.management.JMXMBeanReconnectDUnitTest.html > > Time Spent: 2h 20m > Remaining Estimate: 0h > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:249] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:250] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:251] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:252] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:253] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:254] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:255] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:256] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:257] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testLocalBeans_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:260] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:261] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:262] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:263] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:264] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:265] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:112) > > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:268] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-5407) CI failure: JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator and testLocalBeans_MaintainServerAndCrashLocator
[ https://issues.apache.org/jira/browse/GEODE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-5407: --- Component/s: ci > CI failure: > JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator > and testLocalBeans_MaintainServerAndCrashLocator > - > > Key: GEODE-5407 > URL: https://issues.apache.org/jira/browse/GEODE-5407 > Project: Geode > Issue Type: Bug > Components: ci, jmx, management >Reporter: Jinmei Liao >Priority: Major > Labels: flaky, swat > Attachments: Test results - Class > org.apache.geode.management.JMXMBeanReconnectDUnitTest.html > > Time Spent: 2h 20m > Remaining Estimate: 0h > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:249] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:250] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:251] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:252] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:253] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:254] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:255] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:256] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:257] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testLocalBeans_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:260] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:261] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:262] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:263] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:264] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:265] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:112) > > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:268] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-5407) CI failure: JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator and testLocalBeans_MaintainServerAndCrashLocator
[ https://issues.apache.org/jira/browse/GEODE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969453#comment-16969453 ] Mark Hanson commented on GEODE-5407: More failures: testLocalBeans_MaintainServerAndCrashLocator https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1273 testLocalBeans_MaintainLocatorAndCrashServer https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1433 testLocalBeans_MaintainLocatorAndCrashServer https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1282 testLocalBeans_MaintainLocatorAndCrashServer https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1255 > CI failure: > JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator > and testLocalBeans_MaintainServerAndCrashLocator > - > > Key: GEODE-5407 > URL: https://issues.apache.org/jira/browse/GEODE-5407 > Project: Geode > Issue Type: Bug > Components: jmx, management >Reporter: Jinmei Liao >Priority: Major > Labels: flaky, swat > Attachments: Test results - Class > org.apache.geode.management.JMXMBeanReconnectDUnitTest.html > > Time Spent: 2h 20m > Remaining Estimate: 0h > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:249] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:250] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:251] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:252] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:253] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:254] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:255] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:256] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:257] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testLocalBeans_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:260] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:261] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:262] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:263] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:264] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ >
[jira] [Created] (GEODE-7417) CI checks do not trigger on geode-book changes
Owen Nichols created GEODE-7417: --- Summary: CI checks do not trigger on geode-book changes Key: GEODE-7417 URL: https://issues.apache.org/jira/browse/GEODE-7417 Project: Geode Issue Type: Bug Components: ci Reporter: Owen Nichols due to new branch protection rules, it is now impossible to submit geode-book changes as the required checks will never fire we should remove the exclusion so checks can run -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7229) v2 rest api should make it easier to use the pdx ReflectionBasedAutoSerializer
[ https://issues.apache.org/jira/browse/GEODE-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969417#comment-16969417 ] Darrel Schneider commented on GEODE-7229: - To make it easier to configure a ReflectionBasedAutoSerializer, an "autoSerializer" attribute will be added to the "Pdx" configuration class. The autoSerializer will have two attributes of its own: "portable" is true or false; "patterns" is a list of regex used to match the classes. When creating a pdx config with an autoSerializer the only requirement will be that the autoSerializer has at least one pattern. It is an error to specify both an "autoSerializer" and a "pdxSerializer" on the Pdx. Also the "persistent" attribute will be removed from the Pdx configuration class since it is implied by the "diskStoreName" attribute. > v2 rest api should make it easier to use the pdx ReflectionBasedAutoSerializer > -- > > Key: GEODE-7229 > URL: https://issues.apache.org/jira/browse/GEODE-7229 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > > gfsh configure pdx makes it somewhat easy to configure the > ReflectionBasedAutoSerializer. All you need to do is give say > --auto-serializable-classes=PATTERN and any classes that match PATTERN will > be auto serialized with pdx. > Currently the v2 api requires that you set the Pdx.setPdxSerializer to a > ClassName instance whose name is > "org.apache.geode.pdx.ReflectionBasedAutoSerializer" and whose Properties > contain one with the key "classes" and the value PATTERN. > The v2 rest api should make it at least as easy as gfsh and it could probably > make it even easier. We should consider making the auto serializer the > default if pdx is being configured. The only issue with this is the auto > serializer needs to know which classes it should serialize and which it > should leave alone. So just giving it the pattern ".*" could cause jdk and > other framework classes to be serialized as pdx instead of just the domain > classes. > Another thing that makes it more complicated with gfsh is it has two options; > one for auto-serializable-classes and another for > "--portable-auto-serializable-classes". This makes the command line look more > complicated then it should be. I think we could instead just have the auto > serializer pattern and then another boolean attribute that says if the auto > serializer should check that the classes are portable. The whole portable > thing has to do with making sure all the fields can be converted to the > native client. Perhaps we don't need to expose this boolean if we now thing > it should always be true or false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7416) region.create(k, v) doesn't throw EntryExistsException for PROXY region
[ https://issues.apache.org/jira/browse/GEODE-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charlie Black resolved GEODE-7416. -- Resolution: Invalid This sounds like it is working as designed. The put is checked against the memory of the actor that is doing the put. In the case of a client doing the put that has a proxy region `create` will always work since there is no data. If the client is caching proxy it may or may not return the right answer since the "key" that was doing the put could be in the system from another actor in the distributed system. If you are looking for something more strict putIfAbsent() will check and see if a key exists in the system and only do the put if there isn't a key there already. I am going to close this ticket as the system is working as intended. If you would like to change behavior lets work with the community and open a proposal for change on the dev list. > region.create(k, v) doesn't throw EntryExistsException for PROXY region > --- > > Key: GEODE-7416 > URL: https://issues.apache.org/jira/browse/GEODE-7416 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Heng Yan >Priority: Major > > When an entry exists in the cache server, region.create(k, v) from client > doesn't throw EntryExistsException if client region is *PROXY*. It updates > the existing value instead of throwing exception. If the client region is > *CACHING_PROXY*, it works as expected. > Testing environment: > Client: Geode 1.6 > Server: Geode 1.7 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (GEODE-7416) region.create(k, v) doesn't throw EntryExistsException for PROXY region
[ https://issues.apache.org/jira/browse/GEODE-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charlie Black updated GEODE-7416: - Comment: was deleted (was: This sounds like it is working as designed. The put is checked against the memory of the actor that is doing the put. In the case of a client doing the put that has a proxy region `create` will always work since there is no data. If the client is caching proxy it may or may not return the right answer since the "key" that was doing the put could be in the system from another actor in the distributed system. If you are looking for something more strict putIfAbsent() will check and see if a key exists in the system and only do the put if there isn't a key there already. I am going to close this ticket as the system is working as intended. If you would like to change behavior lets work with the community and open a proposal for change on the dev list.) > region.create(k, v) doesn't throw EntryExistsException for PROXY region > --- > > Key: GEODE-7416 > URL: https://issues.apache.org/jira/browse/GEODE-7416 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Heng Yan >Priority: Major > > When an entry exists in the cache server, region.create(k, v) from client > doesn't throw EntryExistsException if client region is *PROXY*. It updates > the existing value instead of throwing exception. If the client region is > *CACHING_PROXY*, it works as expected. > Testing environment: > Client: Geode 1.6 > Server: Geode 1.7 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7416) region.create(k, v) doesn't throw EntryExistsException for PROXY region
[ https://issues.apache.org/jira/browse/GEODE-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969382#comment-16969382 ] Charlie Black commented on GEODE-7416: -- This sounds like it is working as designed. The put is checked against the memory of the actor that is doing the put. In the case of a client doing the put that has a proxy region `create` will always work since there is no data. If the client is caching proxy it may or may not return the right answer since the "key" that was doing the put could be in the system from another actor in the distributed system. If you are looking for something more strict putIfAbsent() will check and see if a key exists in the system and only do the put if there isn't a key there already. I am going to close this ticket as the system is working as intended. If you would like to change behavior lets work with the community and open a proposal for change on the dev list. > region.create(k, v) doesn't throw EntryExistsException for PROXY region > --- > > Key: GEODE-7416 > URL: https://issues.apache.org/jira/browse/GEODE-7416 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Heng Yan >Priority: Major > > When an entry exists in the cache server, region.create(k, v) from client > doesn't throw EntryExistsException if client region is *PROXY*. It updates > the existing value instead of throwing exception. If the client region is > *CACHING_PROXY*, it works as expected. > Testing environment: > Client: Geode 1.6 > Server: Geode 1.7 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7416) region.create(k, v) doesn't throw EntryExistsException for PROXY region
[ https://issues.apache.org/jira/browse/GEODE-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charlie Black updated GEODE-7416: - Description: When an entry exists in the cache server, region.create(k, v) from client doesn't throw EntryExistsException if client region is *PROXY*. It updates the existing value instead of throwing exception. If the client region is *CACHING_PROXY*, it works as expected. Testing environment: Client: Geode 1.6 Server: Geode 1.7 was: When an entry exists in the cache server, region.create(k, v) from client doesn't throw EntryExistsException if client region is *PROXY*. It updates the existing value instead of throwing exception. If the client region is *CACHING_PROXY*, it works as expected. Testing environment: Client: Geode 1.6 Server: Geode 1.7 (GemFire 9.6.2) > region.create(k, v) doesn't throw EntryExistsException for PROXY region > --- > > Key: GEODE-7416 > URL: https://issues.apache.org/jira/browse/GEODE-7416 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Heng Yan >Priority: Major > > When an entry exists in the cache server, region.create(k, v) from client > doesn't throw EntryExistsException if client region is *PROXY*. It updates > the existing value instead of throwing exception. If the client region is > *CACHING_PROXY*, it works as expected. > Testing environment: > Client: Geode 1.6 > Server: Geode 1.7 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7416) region.create(k, v) doesn't throw EntryExistsException for PROXY region
Heng Yan created GEODE-7416: --- Summary: region.create(k, v) doesn't throw EntryExistsException for PROXY region Key: GEODE-7416 URL: https://issues.apache.org/jira/browse/GEODE-7416 Project: Geode Issue Type: Bug Components: client/server Reporter: Heng Yan When an entry exists in the cache server, region.create(k, v) from client doesn't throw EntryExistsException if client region is *PROXY*. It updates the existing value instead of throwing exception. If the client region is *CACHING_PROXY*, it works as expected. Testing environment: Client: Geode 1.6 Server: Geode 1.7 (GemFire 9.6.2) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7415) Doc Links Broken
[
https://issues.apache.org/jira/browse/GEODE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos updated GEODE-7415:
--
Labels: GeodeCommons (was: )
> Doc Links Broken
>
>
> Key: GEODE-7415
> URL: https://issues.apache.org/jira/browse/GEODE-7415
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
>
> Building the docs, either manually or with the
> {{/dev-tools/docker/docs/build-docs.sh}} script, finishes with the *_Found
> broken links!_* message.
> Attempts to click on any link afterwards while viewing the docs ends up in a
> blank page with the message *_Not Found_*.
> The problem is that, after cutting the new _1.11.0_ release and modifying the
> {{geode-book/config.yml}} file, the {{directory}} property still refers to
> _111_ while the rest of the properties refer to _112_.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7415) Doc Links Broken
[
https://issues.apache.org/jira/browse/GEODE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos reassigned GEODE-7415:
-
Assignee: Juan Ramos
> Doc Links Broken
>
>
> Key: GEODE-7415
> URL: https://issues.apache.org/jira/browse/GEODE-7415
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Juan Ramos
>Assignee: Juan Ramos
>Priority: Major
>
> Building the docs, either manually or with the
> {{/dev-tools/docker/docs/build-docs.sh}} script, finishes with the *_Found
> broken links!_* message.
> Attempts to click on any link afterwards while viewing the docs ends up in a
> blank page with the message *_Not Found_*.
> The problem is that, after cutting the new _1.11.0_ release and modifying the
> {{geode-book/config.yml}} file, the {{directory}} property still refers to
> _111_ while the rest of the properties refer to _112_.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7415) Doc Links Broken
Juan Ramos created GEODE-7415:
-
Summary: Doc Links Broken
Key: GEODE-7415
URL: https://issues.apache.org/jira/browse/GEODE-7415
Project: Geode
Issue Type: Bug
Components: docs
Reporter: Juan Ramos
Building the docs, either manually or with the
{{/dev-tools/docker/docs/build-docs.sh}} script, finishes with the *_Found
broken links!_* message.
Attempts to click on any link afterwards while viewing the docs ends up in a
blank page with the message *_Not Found_*.
The problem is that, after cutting the new _1.11.0_ release and modifying the
{{geode-book/config.yml}} file, the {{directory}} property still refers to
_111_ while the rest of the properties refer to _112_.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7414) SSL ClientHello server_name extension
[
https://issues.apache.org/jira/browse/GEODE-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivanac reassigned GEODE-7414:
---
Assignee: Mario Ivanac
> SSL ClientHello server_name extension
> -
>
> Key: GEODE-7414
> URL: https://issues.apache.org/jira/browse/GEODE-7414
> Project: Geode
> Issue Type: Improvement
> Components: security
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
>
> {color:#172b4d}We propose to add the {color}*server_name extension to the
> ClientHello message*{color:#172b4d}. The extension would hold the distributed
> system ID of the site where the connection originated from.{color}
> {color:#172b4d}This will be used to determine internal geode communication,
> and communication between geode sites.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7414) SSL ClientHello server_name extension
Mario Ivanac created GEODE-7414:
---
Summary: SSL ClientHello server_name extension
Key: GEODE-7414
URL: https://issues.apache.org/jira/browse/GEODE-7414
Project: Geode
Issue Type: Improvement
Components: security
Reporter: Mario Ivanac
{color:#172b4d}We propose to add the {color}*server_name extension to the
ClientHello message*{color:#172b4d}. The extension would hold the distributed
system ID of the site where the connection originated from.{color}
{color:#172b4d}This will be used to determine internal geode communication, and
communication between geode sites.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
