[jira] [Assigned] (GEODE-10445) [Geode Main] Migrate distributedTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10445: --- Assignee: Sai Boorlagadda > [Geode Main] Migrate distributedTest to GHA > --- > > Key: GEODE-10445 > URL: https://issues.apache.org/jira/browse/GEODE-10445 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10445) [Geode Main] Migrate distributedTest to GHA
Sai Boorlagadda created GEODE-10445: --- Summary: [Geode Main] Migrate distributedTest to GHA Key: GEODE-10445 URL: https://issues.apache.org/jira/browse/GEODE-10445 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10442. - Resolution: Fixed > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GEODE-10440) Add support for Micrometer Observation
[ https://issues.apache.org/jira/browse/GEODE-10440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705779#comment-17705779 ] Sai Boorlagadda commented on GEODE-10440: - [~marcingrzejszczak] thanks for reaching out. The community is kind of a reset since both supported companies have recently withdrawn their support. But I am more than happy to learn about this new feature from micrometer and would be willing to review the PR and merge it. > Add support for Micrometer Observation > -- > > Key: GEODE-10440 > URL: https://issues.apache.org/jira/browse/GEODE-10440 > Project: Geode > Issue Type: New Feature >Reporter: Marcin Grzejszczak >Priority: Major > > I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together > with Tommy Ludwig and Jonatan Ivanov). > [Micrometer Observation|https://micrometer.io/docs/observation] is coming as > part of the Micrometer 1.10 release and [Micrometer > Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of > Micrometer Observation is that you instrument code once but you get multiple > benefits out of it - e.g. you can get tracing, metrics, logging or whatever > you see fit). > Since this project already supports Micrometer I was curious if there's > interest in adding Micrometer Observation support so that automatically (when > on classpath) except for metrics, spans could be created and tracing context > propagation could happen too. In other words metrics and tracing of this > project could be created + if there are Micrometer Observation compatible > projects, then they will join the whole graph (e.g. whole Spring Framework 6 > is, Apache Dubbo, Resilience4j etc.). > If there's interest in adding that feature, I can provide a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10442: --- Assignee: Sai Boorlagadda > [Geode Main] Migrate acceptanceTest to GHA > -- > > Key: GEODE-10442 > URL: https://issues.apache.org/jira/browse/GEODE-10442 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10442) [Geode Main] Migrate acceptanceTest to GHA
Sai Boorlagadda created GEODE-10442: --- Summary: [Geode Main] Migrate acceptanceTest to GHA Key: GEODE-10442 URL: https://issues.apache.org/jira/browse/GEODE-10442 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10441. - Resolution: Fixed > [Geode Main] Migrate integrationTest to GHA > --- > > Key: GEODE-10441 > URL: https://issues.apache.org/jira/browse/GEODE-10441 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
[ https://issues.apache.org/jira/browse/GEODE-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10441: --- Assignee: Sai Boorlagadda > [Geode Main] Migrate integrationTest to GHA > --- > > Key: GEODE-10441 > URL: https://issues.apache.org/jira/browse/GEODE-10441 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10441) [Geode Main] Migrate integrationTest to GHA
Sai Boorlagadda created GEODE-10441: --- Summary: [Geode Main] Migrate integrationTest to GHA Key: GEODE-10441 URL: https://issues.apache.org/jira/browse/GEODE-10441 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10434. - Resolution: Fixed > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10439) [Geode Kafka Connector] Upgrade Github actions to latest versions
[ https://issues.apache.org/jira/browse/GEODE-10439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10439: --- Assignee: Sai Boorlagadda > [Geode Kafka Connector] Upgrade Github actions to latest versions > - > > Key: GEODE-10439 > URL: https://issues.apache.org/jira/browse/GEODE-10439 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10439) [Geode Kafka Connector] Upgrade Github actions to latest versions
Sai Boorlagadda created GEODE-10439: --- Summary: [Geode Kafka Connector] Upgrade Github actions to latest versions Key: GEODE-10439 URL: https://issues.apache.org/jira/browse/GEODE-10439 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10438) [Geode Benchmarks] Migrate to GH Actions
[ https://issues.apache.org/jira/browse/GEODE-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10438. - Resolution: Fixed > [Geode Benchmarks] Migrate to GH Actions > > > Key: GEODE-10438 > URL: https://issues.apache.org/jira/browse/GEODE-10438 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10434) [Geode Main] Migrate to GH Action build & unit-test pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-10434: Summary: [Geode Main] Migrate to GH Action build & unit-test pipeline (was: [Geode Main] Build a GH Action build & unit tests pipeline) > [Geode Main] Migrate to GH Action build & unit-test pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10434) [Geode Main] Build a GH Action build & unit tests pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10434: --- Assignee: Sai Boorlagadda > [Geode Main] Build a GH Action build & unit tests pipeline > -- > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10433) Migrate to new CI
[ https://issues.apache.org/jira/browse/GEODE-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10433: --- Assignee: Sai Boorlagadda > Migrate to new CI > - > > Key: GEODE-10433 > URL: https://issues.apache.org/jira/browse/GEODE-10433 > Project: Geode > Issue Type: New Feature > Components: build, ci >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > > Migrating Geode CI onto Apache Infra Jenkins from sponsored Concourse infra. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GEODE-10438) [Geode Benchmarks] Migrate to GH Actions
[ https://issues.apache.org/jira/browse/GEODE-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-10438: --- Assignee: Sai Boorlagadda > [Geode Benchmarks] Migrate to GH Actions > > > Key: GEODE-10438 > URL: https://issues.apache.org/jira/browse/GEODE-10438 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10435) [Geode Examples] Migrate to GH Actions
[ https://issues.apache.org/jira/browse/GEODE-10435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10435. - Resolution: Fixed > [Geode Examples] Migrate to GH Actions > -- > > Key: GEODE-10435 > URL: https://issues.apache.org/jira/browse/GEODE-10435 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10435) [Geode Examples] Migrate to GH Actions
[ https://issues.apache.org/jira/browse/GEODE-10435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-10435: Summary: [Geode Examples] Migrate to GH Actions (was: [Geode Examples] Build a GH Action runAll pipeline) > [Geode Examples] Migrate to GH Actions > -- > > Key: GEODE-10435 > URL: https://issues.apache.org/jira/browse/GEODE-10435 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10438) [Geode Benchmarks] Migrate to GH Actions
Sai Boorlagadda created GEODE-10438: --- Summary: [Geode Benchmarks] Migrate to GH Actions Key: GEODE-10438 URL: https://issues.apache.org/jira/browse/GEODE-10438 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-10437) [Geode Site] Migrate to GH Action
[ https://issues.apache.org/jira/browse/GEODE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-10437. - Resolution: Fixed > [Geode Site] Migrate to GH Action > - > > Key: GEODE-10437 > URL: https://issues.apache.org/jira/browse/GEODE-10437 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10437) [Geode Site] Migrate to GH Action
Sai Boorlagadda created GEODE-10437: --- Summary: [Geode Site] Migrate to GH Action Key: GEODE-10437 URL: https://issues.apache.org/jira/browse/GEODE-10437 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10436) [Geode Examples] Fix develop to use 1.16.0 artifacts
Sai Boorlagadda created GEODE-10436: --- Summary: [Geode Examples] Fix develop to use 1.16.0 artifacts Key: GEODE-10436 URL: https://issues.apache.org/jira/browse/GEODE-10436 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10434) [Geode Main] Build a GH Action build & unit tests pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-10434: Summary: [Geode Main] Build a GH Action build & unit tests pipeline (was: [Geode Main Repo] Build an GH Action build & unit tests pipeline) > [Geode Main] Build a GH Action build & unit tests pipeline > -- > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10435) [Geode Examples] Build a GH Action runAll pipeline
[ https://issues.apache.org/jira/browse/GEODE-10435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-10435: Summary: [Geode Examples] Build a GH Action runAll pipeline (was: [Geode Examples] Build GH Action runAll pipeline) > [Geode Examples] Build a GH Action runAll pipeline > -- > > Key: GEODE-10435 > URL: https://issues.apache.org/jira/browse/GEODE-10435 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10435) [Geode Examples] Build GH Action runAll pipeline
Sai Boorlagadda created GEODE-10435: --- Summary: [Geode Examples] Build GH Action runAll pipeline Key: GEODE-10435 URL: https://issues.apache.org/jira/browse/GEODE-10435 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10434) [Geode Main Repo] Build an GH Action build & unit tests pipeline
[ https://issues.apache.org/jira/browse/GEODE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-10434: Summary: [Geode Main Repo] Build an GH Action build & unit tests pipeline (was: Simple build Pipeline for develop) > [Geode Main Repo] Build an GH Action build & unit tests pipeline > > > Key: GEODE-10434 > URL: https://issues.apache.org/jira/browse/GEODE-10434 > Project: Geode > Issue Type: Sub-task >Reporter: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GEODE-10433) Migrate to new CI
[ https://issues.apache.org/jira/browse/GEODE-10433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-10433: Summary: Migrate to new CI (was: Migrate to Jenkins CI) > Migrate to new CI > - > > Key: GEODE-10433 > URL: https://issues.apache.org/jira/browse/GEODE-10433 > Project: Geode > Issue Type: New Feature > Components: build, ci >Reporter: Sai Boorlagadda >Priority: Major > > Migrating Geode CI onto Apache Infra Jenkins from sponsored Concourse infra. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10434) Simple build Pipeline for develop
Sai Boorlagadda created GEODE-10434: --- Summary: Simple build Pipeline for develop Key: GEODE-10434 URL: https://issues.apache.org/jira/browse/GEODE-10434 Project: Geode Issue Type: Sub-task Reporter: Sai Boorlagadda -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-10433) Migrate to Jenkins CI
Sai Boorlagadda created GEODE-10433: --- Summary: Migrate to Jenkins CI Key: GEODE-10433 URL: https://issues.apache.org/jira/browse/GEODE-10433 Project: Geode Issue Type: New Feature Components: build, ci Reporter: Sai Boorlagadda Migrating Geode CI onto Apache Infra Jenkins from sponsored Concourse infra. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GEODE-7018) Enable hostname validation for SSL over NIO
[ https://issues.apache.org/jira/browse/GEODE-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-7018. Fix Version/s: 1.10.0 Resolution: Fixed > Enable hostname validation for SSL over NIO > --- > > Key: GEODE-7018 > URL: https://issues.apache.org/jira/browse/GEODE-7018 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Sai Boorlagadda >Priority: Major > Fix For: 1.10.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Consider `ssl-endpoint-identification-enabled` configuration during NIO > handshake. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7018) Enable hostname validation for SSL over NIO
Sai Boorlagadda created GEODE-7018: -- Summary: Enable hostname validation for SSL over NIO Key: GEODE-7018 URL: https://issues.apache.org/jira/browse/GEODE-7018 Project: Geode Issue Type: Improvement Components: membership Reporter: Sai Boorlagadda Consider `ssl-endpoint-identification-enabled` configuration during NIO handshake. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (GEODE-6980) Improve logging when CCS is disabled
[ https://issues.apache.org/jira/browse/GEODE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6980: --- Labels: GoodForNewContributors first (was: ) > Improve logging when CCS is disabled > > > Key: GEODE-6980 > URL: https://issues.apache.org/jira/browse/GEODE-6980 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Sai Boorlagadda >Priority: Major > Labels: GoodForNewContributors, first > > When cluster configuration service is disabled. Server do log saying no ccs > found > > [info 2019/07/09 12:40:58.057 EDT tid=0x1] No locator(s) found with > cluster configuration service > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (GEODE-6980) Improve logging when CCS is disabled
[ https://issues.apache.org/jira/browse/GEODE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6980: --- Labels: GoodForNewContributors (was: GoodForNewContributors first) > Improve logging when CCS is disabled > > > Key: GEODE-6980 > URL: https://issues.apache.org/jira/browse/GEODE-6980 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Sai Boorlagadda >Priority: Major > Labels: GoodForNewContributors > > When cluster configuration service is disabled. Server do log saying no ccs > found > > [info 2019/07/09 12:40:58.057 EDT tid=0x1] No locator(s) found with > cluster configuration service > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (GEODE-6980) Improve logging when CCS is disabled
Sai Boorlagadda created GEODE-6980: -- Summary: Improve logging when CCS is disabled Key: GEODE-6980 URL: https://issues.apache.org/jira/browse/GEODE-6980 Project: Geode Issue Type: Improvement Components: logging Reporter: Sai Boorlagadda When cluster configuration service is disabled. Server do log saying no ccs found [info 2019/07/09 12:40:58.057 EDT tid=0x1] No locator(s) found with cluster configuration service -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (GEODE-3948) Improve CQ performance under flaky network conditions
[ https://issues.apache.org/jira/browse/GEODE-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818322#comment-16818322 ] Sai Boorlagadda commented on GEODE-3948: Cherry-picked to 1.9.0 > Improve CQ performance under flaky network conditions > - > > Key: GEODE-3948 > URL: https://issues.apache.org/jira/browse/GEODE-3948 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Galen O'Sullivan >Assignee: Bruce Schuchardt >Priority: Minor > Labels: pull-request-available > Fix For: 1.9.0, 1.10.0 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > Client CQ connections occasionally stop receiving messages and become blocked > indefinitely. > This can be caused by a server that hangs or dies without sending a close > message, or by some firewalls. > The client already gets ping messages from the server, but currently ignores > them. Let's use those messages to detect a failed connection and close it. > Probably the client should follow the same logic and send ping messages if it > has sent no acks for a while, so that the server can also detect and close a > broken connection. > The timeout could be specified as a number and time interval, the ping > interval and the number of missed pings after which to fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3948) Improve CQ performance under flaky network conditions
[ https://issues.apache.org/jira/browse/GEODE-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-3948: --- Fix Version/s: 1.9.0 > Improve CQ performance under flaky network conditions > - > > Key: GEODE-3948 > URL: https://issues.apache.org/jira/browse/GEODE-3948 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Galen O'Sullivan >Assignee: Bruce Schuchardt >Priority: Minor > Labels: pull-request-available > Fix For: 1.9.0, 1.10.0 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > Client CQ connections occasionally stop receiving messages and become blocked > indefinitely. > This can be caused by a server that hangs or dies without sending a close > message, or by some firewalls. > The client already gets ping messages from the server, but currently ignores > them. Let's use those messages to detect a failed connection and close it. > Probably the client should follow the same logic and send ping messages if it > has sent no acks for a while, so that the server can also detect and close a > broken connection. > The timeout could be specified as a number and time interval, the ping > interval and the number of missed pings after which to fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6648) wrong import of assertEquals in geode-example/functions
[ https://issues.apache.org/jira/browse/GEODE-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-6648. Resolution: Fixed Assignee: Sai Boorlagadda Fix Version/s: 1.10.0 > wrong import of assertEquals in geode-example/functions > --- > > Key: GEODE-6648 > URL: https://issues.apache.org/jira/browse/GEODE-6648 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Fix For: 1.10.0 > > > It was wrongly imported to use org.jgroups.util.Util.assertEquals > -import static org.jgroups.util.Util.assertEquals; > +import static org.junit.Assert.assertEquals; > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6648) wrong import of assertEquals in geode-example/functions
Sai Boorlagadda created GEODE-6648: -- Summary: wrong import of assertEquals in geode-example/functions Key: GEODE-6648 URL: https://issues.apache.org/jira/browse/GEODE-6648 Project: Geode Issue Type: Bug Components: examples Reporter: Sai Boorlagadda It was wrongly imported to use org.jgroups.util.Util.assertEquals -import static org.jgroups.util.Util.assertEquals; +import static org.junit.Assert.assertEquals; -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6195) putIfAbsent may get a returned value caused by the same operation due to retry
[ https://issues.apache.org/jira/browse/GEODE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6195: --- Fix Version/s: (was: 1.9.0) > putIfAbsent may get a returned value caused by the same operation due to retry > -- > > Key: GEODE-6195 > URL: https://issues.apache.org/jira/browse/GEODE-6195 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > A server which does not store the entry will try the putIfAbsent operation to > host member. Currently product treats this as a failed op even though it is > due to retried operation. If it does the operation on behalf of client (and > client never failed over to another server), this could leads to client > server data inconsistency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets
[
https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6472:
---
Fix Version/s: (was: 1.10.0)
(was: 1.9.0)
(was: 1.8.0)
> cachePerfStats:gets is double incremented on partitioned region gets
>
>
> Key: GEODE-6472
> URL: https://issues.apache.org/jira/browse/GEODE-6472
> Project: Geode
> Issue Type: Bug
> Components: statistics
>Reporter: Jacob S. Barrett
>Priority: Major
>
> The cache level stats, cachePerfStats, shows double the gets for portioned
> region stats.
> If a client does 1000 gets/second on a partitioned region and you examine the
> servers stats archive you will see {{cachePerfStats:gets}} will show 2000
> (and change) gets/second while {{RegionStats-partitioned:gets}} will show
> 1000 gets/second.
> Other region/cache stats, like put, may also be effected similarly.
> May effect versions older than 1.8.
> A test should be written to assert that region and cache stats are relatively
> the same for cases where only one region is being accessed on the cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5407) org.apache.geode.management.JMXMBeanReconnectDUnitTest > testRemoteBeanKnowledge_MaintainServerAndCrashLocator and testLocalBeans_MaintainServerAndCrashLocator FAILED
[ https://issues.apache.org/jira/browse/GEODE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-5407: --- Fix Version/s: (was: 1.9.0) > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator and > testLocalBeans_MaintainServerAndCrashLocator FAILED > -- > > Key: GEODE-5407 > URL: https://issues.apache.org/jira/browse/GEODE-5407 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available, 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 (v7.6.3#76005)
[jira] [Updated] (GEODE-5817) CI Failure: StopServerAcceptanceTest.canStopServerByNameWhenConnectedOverHttp
[
https://issues.apache.org/jira/browse/GEODE-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-5817:
---
Fix Version/s: (was: 1.9.0)
> CI Failure: StopServerAcceptanceTest.canStopServerByNameWhenConnectedOverHttp
> -
>
> Key: GEODE-5817
> URL: https://issues.apache.org/jira/browse/GEODE-5817
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Brian Rowe
>Assignee: Kenneth Howe
>Priority: Major
> Labels: swat
>
> This appears to be the same issue as GEODE-5601, however, this is still
> occurring even when the acceptanceTests are being run serially (or at least,
> run with the fix for 5601).
> Example failures:
> from
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/47
> {noformat}org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest
> > canStopServerByNameWhenConnectedOverHttp 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.GfshExecution.awaitTermination(GfshExecution.java:124)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest.startCluster(StopServerAcceptanceTest.java:32){noformat}
> from
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/53
> {noformat}org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest
> > classMethod 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.GfshExecution.awaitTermination(GfshExecution.java:124)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest.classSetup(StatusServerExitCodeAcceptanceTest.java:66){noformat}
> Looking at the logs for these failures, we see the following in standard
> error:
> {noformat}
> The Cache Server process terminated unexpectedly with exit status 1. Please
> refer to the log file in
> /tmp/junit5496177071859309076/member-controller/server-lock-better-iota for
> full details.
> Exception in thread "main" java.lang.RuntimeException: An IO error occurred
> while starting a Server in
> /tmp/junit5496177071859309076/member-controller/server-lock-better-iota on
> develop-acceptancetest-53.c.apachegeode-ci.internal[40404]: Network is
> unreachable; port (40404) is not available on localhost.
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:816)
> at
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:704)
> at
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:224)
> Caused by: java.net.BindException: Network is unreachable; port (40404) is
> not available on localhost.
> at
> org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:129)
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:761)
> ... 2 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6631) CI Failure: DeprecatedCacheServerLauncherIntegrationTest. testStartStatusStop
Sai Boorlagadda created GEODE-6631: -- Summary: CI Failure: DeprecatedCacheServerLauncherIntegrationTest. testStartStatusStop Key: GEODE-6631 URL: https://issues.apache.org/jira/browse/GEODE-6631 Project: Geode Issue Type: Bug Components: ci Reporter: Sai Boorlagadda org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest > testStartStatusStop FAILED java.lang.AssertionError: Timed out waiting for output "CacheServer pid: \\d+ status: running" after 12 ms. Output: Starting CacheServer with pid: 0 at org.junit.Assert.fail(Assert.java:88) at org.apache.geode.test.process.ProcessWrapper.waitForOutputToMatch(ProcessWrapper.java:240) at org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.execAndValidate(DeprecatedCacheServerLauncherIntegrationTest.java:451) at org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.testStartStatusStop(DeprecatedCacheServerLauncherIntegrationTest.java:173) 4501 tests completed, 1 failed, 79 skipped =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-results/integrationTest/1554927104/*] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-artifacts/1554927104/integrationtestfiles-OpenJDK11-1.9.0-SNAPSHOT.0024.tgz*] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6619) CI Failure: ClientServerTransactionFailoverDistributedTest.clientLongTransactionDoesNotLoseOperationsAfterFailoverDirectlyToTransactionHost
[ https://issues.apache.org/jira/browse/GEODE-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6619: --- Description: Failed on release/1.9.0 branch: org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest > clientLongTransactionDoesNotLoseOperationsAfterFailoverDirectlyToTransactionHost FAILED org.apache.geode.cache.TransactionDataNodeHasDepartedException: Could not find transaction host for TXId: 172.17.0.3(1:loner):36440:ef5fb9fe:1 8382 tests completed, 1 failed, 500 skipped =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-results/distributedTest/1554757843/*] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-artifacts/1554757843/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0024.tgz*] was: org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest > clientLongTransactionDoesNotLoseOperationsAfterFailoverDirectlyToTransactionHost FAILED org.apache.geode.cache.TransactionDataNodeHasDepartedException: Could not find transaction host for TXId: 172.17.0.3(1:loner):36440:ef5fb9fe:1 8382 tests completed, 1 failed, 500 skipped =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-results/distributedTest/1554757843/*] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-artifacts/1554757843/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0024.tgz*] > CI Failure: > ClientServerTransactionFailoverDistributedTest.clientLongTransactionDoesNotLoseOperationsAfterFailoverDirectlyToTransactionHost > --- > > Key: GEODE-6619 > URL: https://issues.apache.org/jira/browse/GEODE-6619 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sai Boorlagadda >Priority: Major > > Failed on release/1.9.0 branch: > org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest > > > clientLongTransactionDoesNotLoseOperationsAfterFailoverDirectlyToTransactionHost > FAILED > org.apache.geode.cache.TransactionDataNodeHasDepartedException: Could > not find transaction host for TXId: 172.17.0.3(1:loner):36440:ef5fb9fe:1 > 8382 tests completed, 1 failed, 500 skipped > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-results/distributedTest/1554757843/*] > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-artifacts/1554757843/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0024.tgz*] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6619) CI Failure: ClientServerTransactionFailoverDistributedTest.clientLongTransactionDoesNotLoseOperationsAfterFailoverDirectlyToTransactionHost
Sai Boorlagadda created GEODE-6619: -- Summary: CI Failure: ClientServerTransactionFailoverDistributedTest.clientLongTransactionDoesNotLoseOperationsAfterFailoverDirectlyToTransactionHost Key: GEODE-6619 URL: https://issues.apache.org/jira/browse/GEODE-6619 Project: Geode Issue Type: Bug Components: ci Reporter: Sai Boorlagadda org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest > clientLongTransactionDoesNotLoseOperationsAfterFailoverDirectlyToTransactionHost FAILED org.apache.geode.cache.TransactionDataNodeHasDepartedException: Could not find transaction host for TXId: 172.17.0.3(1:loner):36440:ef5fb9fe:1 8382 tests completed, 1 failed, 500 skipped =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-results/distributedTest/1554757843/*] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0024/test-artifacts/1554757843/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0024.tgz*] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-5407) org.apache.geode.management.JMXMBeanReconnectDUnitTest > testRemoteBeanKnowledge_MaintainServerAndCrashLocator and testLocalBeans_MaintainServerAndCrashLocator FAILED
[ https://issues.apache.org/jira/browse/GEODE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reopened GEODE-5407: Failed on release/1.9.0 branch =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0023/test-results/distributedTest/1553892502/*] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0023/test-artifacts/1553892502/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0023.tgz*] > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator and > testLocalBeans_MaintainServerAndCrashLocator FAILED > -- > > Key: GEODE-5407 > URL: https://issues.apache.org/jira/browse/GEODE-5407 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Helena Bales >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.9.0 > > 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 >
[jira] [Commented] (GEODE-3458) Failure in SerialWANPropagationDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent due to loss of quorum
[
https://issues.apache.org/jira/browse/GEODE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16813692#comment-16813692
]
Sai Boorlagadda commented on GEODE-3458:
Failed in release/1.9.0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0021/test-results/distributedTest/1553807276/*]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0021/test-artifacts/1553807276/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0021.tgz*]
> Failure in
> SerialWANPropagationDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
> due to loss of quorum
> --
>
> Key: GEODE-3458
> URL: https://issues.apache.org/jira/browse/GEODE-3458
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Dan Smith
>Priority: Major
>
> This test failed in a private build with
> bc655eb9b3683282705e7449f0f7a720c1a6243d
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagationDUnitTest >
> testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
> FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2776
> [fatal 2017/08/16 00:34:19.721 UTC
> tid=0xf5] Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.8(179):32771]
> {noformat}
> Looking at the test, I think what is going on is that we create a WAN site
> with only 2 members. When the test tears down the VMs, it closes the first
> member and I think the second member is then deciding that is has lost quorum.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6376) PersistentRecoveryOrderDUnitTest > testCrashDuringPreparePersistentId FAILED
[
https://issues.apache.org/jira/browse/GEODE-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812904#comment-16812904
]
Sai Boorlagadda commented on GEODE-6376:
Failed on 1.9.0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0023/test-results/distributedTest/1554152498/*]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0023/test-artifacts/1554152498/distributedtestfiles-OpenJDK11-1.9.0-SNAPSHOT.0023.tgz*]
> PersistentRecoveryOrderDUnitTest > testCrashDuringPreparePersistentId FAILED
>
>
> Key: GEODE-6376
> URL: https://issues.apache.org/jira/browse/GEODE-6376
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
>
> Failure Link
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/373
> Log Archives:
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0412/test-results/distributedTest/1549403523/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0412/test-artifacts/1549403523/distributedtestfiles-OpenJDK11-1.9.0-SNAPSHOT.0412.tgz
> Stack Trace:
> {code}
> java.lang.RuntimeException: java.lang.IllegalStateException: Disk store
> PersistentRecoveryOrderDUnitTest_testCrashDuringPreparePersistentIdRegion not
> found
> at
> org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:194)
> at
> org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:180)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1325)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
> at
>
[jira] [Commented] (GEODE-1703) SUPERFLAKY: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812903#comment-16812903
]
Sai Boorlagadda commented on GEODE-1703:
Failed on 1.9.0
{noquote}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0023/test-results/distributedTest/1554152498/*]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[*http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0023/test-artifacts/1554152498/distributedtestfiles-OpenJDK11-1.9.0-SNAPSHOT.0023.tgz*]
{noquote}
> SUPERFLAKY:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: regions, tests
>Reporter: Kirk Lund
>Assignee: Mark Hanson
>Priority: Minor
> Labels: CI, flaky, pull-request-available, swat
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6487) OsStatistics should use PID for the numericId
[
https://issues.apache.org/jira/browse/GEODE-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6487:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> OsStatistics should use PID for the numericId
> -
>
> Key: GEODE-6487
> URL: https://issues.apache.org/jira/browse/GEODE-6487
> Project: Geode
> Issue Type: Improvement
> Components: statistics
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.9.0
>
>
> OsStatistics (created by HostStatHelper) uses getHostSystemId() for the
> numericId:
> {noformat}
> /**
>* Generate a systemid based off of the ip address of the host. This
> duplicates the common
>* implementation of long gethostid(void) . Punt on the ipv6
> case and just use the
>* same algorithm.
>*
>* @return a psuedo unique id based on the ip address
>*/
> private static long getHostSystemId() {
> long id = 0L;
> try {
> InetAddress host = SocketCreator.getLocalHost();
> byte[] addr = host.getAddress();
> id = (addr[1] & 0xFFL) << 24 | (addr[0] & 0xFFL) << 16 | (addr[3] &
> 0xFFL) << 8
> | (addr[2] & 0xFFL) << 0;
> } catch (UnknownHostException uhe) {
> }
> return id;
> }
> {noformat}
> I think it would be more useful to change the numericId to be the PID which
> will be consistent with all other statistics instances.
> We could then add a new long stat to OsStatistics to contain the value of
> getHostSystemId() -- I'm not sure this value is actually valuable when
> reviewing stats though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6459) Add option to `create jdbc-mapping` where user can specify the file containing the PDX class
[
https://issues.apache.org/jira/browse/GEODE-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6459:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> Add option to `create jdbc-mapping` where user can specify the file
> containing the PDX class
>
>
> Key: GEODE-6459
> URL: https://issues.apache.org/jira/browse/GEODE-6459
> Project: Geode
> Issue Type: New Feature
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> **As a** user
> **I want to** tell gfsh with `create jdbc-mapping` the file containing the
> PDX class for my domain object
> **so that I can** create the mapping without deploying the domain class to
> the server.
> Use gfsh option name: {{--pdx-class-file}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6447) In CI, Windows Acceptance and Integration tests should not run in parallel
[ https://issues.apache.org/jira/browse/GEODE-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6447: --- Fix Version/s: (was: 1.10.0) 1.9.0 > In CI, Windows Acceptance and Integration tests should not run in parallel > -- > > Key: GEODE-6447 > URL: https://issues.apache.org/jira/browse/GEODE-6447 > Project: Geode > Issue Type: Test > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > As we don't have docker isolation for Windows, these tests should not run in > parallel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6517) Race condition exists that a node failed to be shutdown as it is stuck on PRHARedundancyProvider.waitForPersistentBucketRecovery()
[
https://issues.apache.org/jira/browse/GEODE-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6517:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> Race condition exists that a node failed to be shutdown as it is stuck on
> PRHARedundancyProvider.waitForPersistentBucketRecovery()
> --
>
> Key: GEODE-6517
> URL: https://issues.apache.org/jira/browse/GEODE-6517
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.1.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The hang thread stack:
> "Shutdown Disconnector1" #93 prio=10 os_prio=0 tid=0x7f84b8002800
> nid=0x6875 waiting on condition [0x7f844ee31000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0xf14f0490> (a
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at
> org.apache.geode.internal.cache.PRHARedundancyProvider.waitForPersistentBucketRecovery(PRHARedundancyProvider.java:2019)
> at
> org.apache.geode.internal.cache.PartitionedRegion.postDestroyRegion(PartitionedRegion.java:7536)
> at
> org.apache.geode.internal.cache.LocalRegion.recursiveDestroyRegion(LocalRegion.java:2707)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6308)
> at
> org.apache.geode.internal.cache.LocalRegion.handleCacheClose(LocalRegion.java:7387)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2281)
> - locked <0xf0abeb00> (a java.lang.Class for
> org.apache.geode.internal.cache.GemFireCacheImpl)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1593)
> - locked <0xf0abeb00> (a java.lang.Class for
> org.apache.geode.internal.cache.GemFireCacheImpl)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1255)
> at
> org.apache.geode.management.internal.cli.functions.ShutDownFunction.lambda$disconnectInNonDaemonThread$0(ShutDownFunction.java:78)
> at
> org.apache.geode.management.internal.cli.functions.ShutDownFunction$$Lambda$94/665093117.run(Unknown
> Source)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> The race occurs during recoverPersistentBuckets, between following latch is
> created and then nulled out, shutdown thread could get hold of the reference
> of latch and wait for countDown forever.
> allBucketsRecoveredFromDisk = new CountDownLatch(proxyBucketArray.length);
> try {
> if (proxyBucketArray.length > 0) {
> this.redundancyLogger = new RedundancyLogger(this);
> Thread loggingThread = new LoggingThread(
> "RedundancyLogger for region " + this.prRegion.getName(), false,
> this.redundancyLogger);
> loggingThread.start();
> }
> } catch (RuntimeException e) {
> allBucketsRecoveredFromDisk = null;
> throw e;
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6196) Remove TypedJson
[ https://issues.apache.org/jira/browse/GEODE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6196: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Remove TypedJson > > > Key: GEODE-6196 > URL: https://issues.apache.org/jira/browse/GEODE-6196 > Project: Geode > Issue Type: Sub-task > Components: gfsh >Reporter: Anilkumar Gingade >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Once we move to use Jackson, we should remove TypedJson from product and > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6513) Geode README and BUILD documents need revision
[ https://issues.apache.org/jira/browse/GEODE-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6513: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Geode README and BUILD documents need revision > -- > > Key: GEODE-6513 > URL: https://issues.apache.org/jira/browse/GEODE-6513 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Robert Houghton >Assignee: Robert Houghton >Priority: Major > Fix For: 1.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The Build-status badge points to stale travis build. The build-in-intellij > directions are out-of-date for rebuilding the generated sources from antlr > and protobuf. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6497) GII provider should send failure message to requester when processing RequestImageMessage during shutdown
[ https://issues.apache.org/jira/browse/GEODE-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6497: --- Fix Version/s: (was: 1.10.0) 1.9.0 > GII provider should send failure message to requester when processing > RequestImageMessage during shutdown > - > > Key: GEODE-6497 > URL: https://issues.apache.org/jira/browse/GEODE-6497 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > GII requester sends PrepareNewPersistentMemberMessage to other members and > then request GII to a provider. Currently the provider would not processing > PrepareNewPersistentMemberMessage if it is being shutdown but send a regular > reply message to requester. However, provider would process the image > request. This causes that requester persists its new id, but provider does > not. And this will prevent the requester to be restarted due to > ConflictingPersistentDataException. > The fix is to send a failed message when processing image request, thus > prevent the request to persist its new id. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6458) Support profiling benchmarks
[ https://issues.apache.org/jira/browse/GEODE-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6458: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Support profiling benchmarks > > > Key: GEODE-6458 > URL: https://issues.apache.org/jira/browse/GEODE-6458 > Project: Geode > Issue Type: Improvement > Components: benchmarks >Reporter: Jacob S. Barrett >Assignee: Helena Bales >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add support for profiling benchmarks. > * Upload profiler dependencies > * Download profiler output > * Pass profiler arguments to JVMs > * Configure which JVMs get profiler arguments > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6502) Update benchmark readme
[ https://issues.apache.org/jira/browse/GEODE-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6502: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Update benchmark readme > --- > > Key: GEODE-6502 > URL: https://issues.apache.org/jira/browse/GEODE-6502 > Project: Geode > Issue Type: Improvement > Components: benchmarks >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update benchmark readme to reflect all recent changes to AWS benchmark scripts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6434) Change version & ordinal variables to GEODE_MAJOR_MINOR_PATCH
[ https://issues.apache.org/jira/browse/GEODE-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6434: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Change version & ordinal variables to GEODE_MAJOR_MINOR_PATCH > - > > Key: GEODE-6434 > URL: https://issues.apache.org/jira/browse/GEODE-6434 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Sai Boorlagadda >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, variables to ordinals and versions follow GEODE_XYZ format for a > release x.y.z. But starting from version 1.10.0 it becomes > GEODE_1100_ORDINAL, which seems little weird after GEODE_190_ORDINAL. Also, > backward compatibility methods already use pattern GEODE_X_Y_Z, so changing > the version & ordinal variables also to be GEODE_X_Y_Z pattern. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6424) Reduce overhead of stats storage
[
https://issues.apache.org/jira/browse/GEODE-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6424:
---
Fix Version/s: (was: 1.10.0)
> Reduce overhead of stats storage
>
>
> Key: GEODE-6424
> URL: https://issues.apache.org/jira/browse/GEODE-6424
> Project: Geode
> Issue Type: Improvement
> Components: statistics
>Reporter: Jacob S. Barrett
>Priority: Major
> Fix For: 1.9.0
>
> Attachments: 32-thread.png, image.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The current stats storage system is based on a very old and complicated
> implementation of a thread striped counter. See {{Atomic50StatisticsImpl}}.
> This implementation makes now incorrect assumptions about certain performance
> characteristics of volatile memory access. Combined with it's complexity it
> is causing large variances in performance numbers on the function benchmarks.
> Runs can differ by as much as 45%.
> Replace this implementation with one based on the Java 8 {{LongAdder}}, which
> is a modern and JDK maintained implementation of a striped counter. Also use
> {{DoubleAdder}} to support doubles, which the {{Atomic50StatisticsImpl}} does
> not support.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6456) CI Failure SystemAdminDUnitTest > testPrintStacks
[
https://issues.apache.org/jira/browse/GEODE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6456:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> CI Failure SystemAdminDUnitTest > testPrintStacks
> -
>
> Key: GEODE-6456
> URL: https://issues.apache.org/jira/browse/GEODE-6456
> Project: Geode
> Issue Type: Bug
>Reporter: Dale Emery
>Priority: Major
> Labels: ci, flaky
> Fix For: 1.9.0
>
>
> No build or artifacts available.
> {noformat}
> java.lang.AssertionError: Expecting:
> --- dump of stack for member 172.17.0.16(105:locator):41000
> --
> "unused AsyncSocketCloser" tid=0x4a
> java.lang.Thread.State: TIMED_WAITING
> at sun.misc.Unsafe.park(Native Method)
> - waiting on java.util.concurrent.ForkJoinPool@1d44207a
> at java.util.concurrent.ForkJoinPool.awaitWork(ForkJoinPool.java:1824)
> at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1693)
> at
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
> "main" tid=0x1
> java.lang.Thread.State: TIMED_WAITING
> at java.lang.Thread.sleep(Native Method)
> at org.apache.geode.test.dunit.internal.ChildVM.main(ChildVM.java:65)
> "disconnect thread for 0d7f10cd6a88(1:admin):41001" tid=0x4b
> java.lang.Thread.State: TIMED_WAITING
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$destroyMember$2(GMSMembershipManager.java:1987)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager$$Lambda$122/1126132791.run(Unknown
> Source)
> at java.lang.Thread.run(Thread.java:748)
> "Signal Dispatcher" tid=0x4
> java.lang.Thread.State: RUNNABLE
> "Reference Handler" tid=0x2
> java.lang.Thread.State: WAITING
> at java.lang.Object.wait(Native Method)
> - waiting on java.lang.ref.Reference$Lock@46e59e5a
> at java.lang.Object.wait(Object.java:502)
> at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)
> "Management Task1" tid=0x41
> java.lang.Thread.State: RUNNABLE
> at java.lang.Double.doubleToRawLongBits(Native Method)
> at java.lang.Double.doubleToLongBits(Double.java:836)
> at java.lang.Double.equals(Double.java:799)
> at
> org.apache.geode.management.internal.FederationComponent.refreshObjectState(FederationComponent.java:186)
> at
> org.apache.geode.management.internal.LocalManager$ManagementTask.run(LocalManager.java:332)
> - locked java.lang.Object@51ba4571
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Number of locked synchronizers = 1
> - java.util.concurrent.ThreadPoolExecutor$Worker@5e83356d
> "Finalizer" tid=0x3
> java.lang.Thread.State: WAITING
> at java.lang.Object.wait(Native Method)
> - waiting on java.lang.ref.ReferenceQueue$Lock@3f91675a
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:216)
> to not contain:
> Management Task
> but found:
> "Management Task1" tid=0x41
> at
> org.apache.geode.test.assertj.internal.AbstractLogFileAssert.assertDoesNotContain(AbstractLogFileAssert.java:157)
> at
> org.apache.geode.test.assertj.internal.AbstractLogFileAssert.doesNotContain(AbstractLogFileAssert.java:60)
> at
> org.apache.geode.distributed.SystemAdminDUnitTest.checkStackDumps(SystemAdminDUnitTest.java:100)
> at
> org.apache.geode.distributed.SystemAdminDUnitTest.testPrintStacks(SystemAdminDUnitTest.java:91)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
[jira] [Updated] (GEODE-6440) race condition in StripedStatisticsImpl sets and gets
[
https://issues.apache.org/jira/browse/GEODE-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6440:
---
Fix Version/s: (was: 1.10.0)
> race condition in StripedStatisticsImpl sets and gets
> -
>
> Key: GEODE-6440
> URL: https://issues.apache.org/jira/browse/GEODE-6440
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.9.0, 1.10.0
>Reporter: Helena Bales
>Assignee: Helena Bales
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> A race condition exists in {{StripedStatisticsImpl}} when used for gauge
> statistics that can cause gets to read partial updates. Calling {{set}}
> concurrently could result in multiple cells containing the set value, when
> only one cell should have a value, or none of the cells containing the new
> value when read by {{get}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6519) Purge CreateGatewaySenderCommand Boolean Parameters
[
https://issues.apache.org/jira/browse/GEODE-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6519:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> Purge CreateGatewaySenderCommand Boolean Parameters
> ---
>
> Key: GEODE-6519
> URL: https://issues.apache.org/jira/browse/GEODE-6519
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Several of the {{CreateGatewaySenderCommand}} {{boolean}} parameters are left
> as {{null}} / {{false}} even when they are set through the command line
> without a value, this is extremely counter intuitive.
> As an example, as a user I would expect the command {{gfsh create
> gateway-sender --enable-persistence}} to create a persistent
> {{gateway-sender}} but, instead, it creates a non-persistent one.
> This ticket is to sanitate the following parameters, configuring them as
> {{true}} by default whenever they are specified in the command line without
> any value:
> * parallel
> * disk-synchronous
> * enable-persistence
> * enable-batch-conflation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5013) Replace org.json with Jackson in GfJsonObject
[ https://issues.apache.org/jira/browse/GEODE-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-5013: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Replace org.json with Jackson in GfJsonObject > - > > Key: GEODE-5013 > URL: https://issues.apache.org/jira/browse/GEODE-5013 > Project: Geode > Issue Type: Sub-task > Components: gfsh >Reporter: Jens Deppe >Assignee: Bruce Schuchardt >Priority: Major > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6438) Windows CI images to not consider administrators_authorized_keys
[ https://issues.apache.org/jira/browse/GEODE-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6438: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Windows CI images to not consider administrators_authorized_keys > > > Key: GEODE-6438 > URL: https://issues.apache.org/jira/browse/GEODE-6438 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Fix For: 1.9.0 > > Time Spent: 10m > Remaining Estimate: 0h > > sshd builds on windows-server seems to be failing to accept a connection as > the service would look into authorized keys in a specific location > `__PROGRAMDATA__/ssh/administrators_authorized_keys` whereas packer script > creates the file in C:\Users\geode\.ssh. > So comment these two lines in sshd_config so the service fallback to > $HOME/.ssh/authorized_keys. > For more information: https://github.com/PowerShell/Win32-OpenSSH/issues/1306 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6436) CI Failure: RebalanceOperationDUnitTest. testRecoverRedundancyBalancing
[
https://issues.apache.org/jira/browse/GEODE-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6436:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> CI Failure: RebalanceOperationDUnitTest. testRecoverRedundancyBalancing
> ---
>
> Key: GEODE-6436
> URL: https://issues.apache.org/jira/browse/GEODE-6436
> Project: Geode
> Issue Type: Bug
>Reporter: Patrick Rhomberg
>Assignee: Helena Bales
>Priority: Major
> Fix For: 1.9.0
>
>
> {noformat}
> org.apache.geode.internal.cache.control.RebalanceOperationDUnitTest >
> testRecoverRedundancyBalancing FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.control.RebalanceOperationDUnitTest$35.run in
> VM 1 running on Host b422b7fbcaf6 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.control.RebalanceOperationDUnitTest.recoverRedundancyBalancing(RebalanceOperationDUnitTest.java:985)
> at
> org.apache.geode.internal.cache.control.RebalanceOperationDUnitTest.testRecoverRedundancyBalancing(RebalanceOperationDUnitTest.java:883)
> Caused by:
> java.lang.AssertionError: expected:<1> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at
> org.apache.geode.internal.cache.control.RebalanceOperationDUnitTest$35.run(RebalanceOperationDUnitTest.java:979){noformat}
> Find CI failure here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/414
> Find test results here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0458/test-results/distributedTest/1550643578/index.html
> Find artifacts here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0458/test-artifacts/1550643578/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0458.tgz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6412) Improve concurrency for PartitionedIndex.getBucketIndex method
[ https://issues.apache.org/jira/browse/GEODE-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6412: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Improve concurrency for PartitionedIndex.getBucketIndex method > -- > > Key: GEODE-6412 > URL: https://issues.apache.org/jira/browse/GEODE-6412 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 2h > Remaining Estimate: 0h > > The method getBucketIndex is used when querying against a region with a > partitioned index. Currently it is synchronized. We can probably improve > this by either removing the synchronization (try/catching expected > exceptions) or some other mechanism to prevent iterator.next() and/or get(0) > from failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6421) CI failure: org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators failed with AssertionError
[ https://issues.apache.org/jira/browse/GEODE-6421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6421: --- Fix Version/s: (was: 1.10.0) 1.9.0 > CI failure: > org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators failed > with AssertionError > - > > Key: GEODE-6421 > URL: https://issues.apache.org/jira/browse/GEODE-6421 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Assignee: Bruce Schuchardt >Priority: Major > Fix For: 1.9.0 > > > org.apache.geode.distributed.LocatorDUnitTest > testStartTwoLocators FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host > f44e8e23cdaf with 6 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:393) > at > org.apache.geode.distributed.LocatorDUnitTest.startVerifyAndStopLocator(LocatorDUnitTest.java:1799) > at > org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators(LocatorDUnitTest.java:317) > Caused by: > java.lang.AssertionError: expected:<2> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.distributed.LocatorDUnitTest.expectSystemToContainThisManyMembers(LocatorDUnitTest.java:139) > at > org.apache.geode.distributed.LocatorDUnitTest.lambda$startVerifyAndStopLocator$2ba733bc$1(LocatorDUnitTest.java:1800) > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/405 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6414) PdxInstanceFactory uses too much memory when it creates a PdxInstance
[ https://issues.apache.org/jira/browse/GEODE-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6414: --- Fix Version/s: (was: 1.10.0) 1.9.0 > PdxInstanceFactory uses too much memory when it creates a PdxInstance > - > > Key: GEODE-6414 > URL: https://issues.apache.org/jira/browse/GEODE-6414 > Project: Geode > Issue Type: Bug >Reporter: Jianxia Chen >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Two causes of using too much memory have been identified: > 1. PdxInstanceFactory.create() will register a duplicate PdxType when there > is already an identical PdxType in the type registry. It should reuse the > PdxType that is already in the type registry instead. > 2. The HeapByteBuffer may have extra unused memory in it. A ByteBuffer of the > size needed can be allocated and the byte from the larger one copied into it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6486) StatSamplerStats should use PID for its numericId
[ https://issues.apache.org/jira/browse/GEODE-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6486: --- Fix Version/s: (was: 1.10.0) 1.9.0 > StatSamplerStats should use PID for its numericId > - > > Key: GEODE-6486 > URL: https://issues.apache.org/jira/browse/GEODE-6486 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > While reviewing the changes for GEODE-6442, we discovered that the > StatSamplerStats currently use DistributedSystem.getId() for the numericId. > All other statistics instances use the PID for the numericId. We believe that > it would be much better if the StatSamplerStats also used the PID. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6479) Add username to keypair when creating AWS instances for benchmarks
[ https://issues.apache.org/jira/browse/GEODE-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6479: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Add username to keypair when creating AWS instances for benchmarks > -- > > Key: GEODE-6479 > URL: https://issues.apache.org/jira/browse/GEODE-6479 > Project: Geode > Issue Type: Improvement > Components: benchmarks >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Fix For: 1.9.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Add the current system username to AWS keypairs when creating instances for > running benchmark tests, to help reduce the number of instances that are left > running with no clear owners. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6348) CI Failure: PersistentPartitionedRegionDUnitTest.cacheIsClosedWhenConflictingPersistentDataExceptionIsThrown
[
https://issues.apache.org/jira/browse/GEODE-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6348:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> CI Failure:
> PersistentPartitionedRegionDUnitTest.cacheIsClosedWhenConflictingPersistentDataExceptionIsThrown
>
>
> Key: GEODE-6348
> URL: https://issues.apache.org/jira/browse/GEODE-6348
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This test failed for me in a StressNewTest run:
> {noformat}
> org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionDistributedTest
> > cacheIsClosedWhenConflictingPersistentDataExceptionIsThrown FAILED
>
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
>
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
>
> ---
>
> Found suspect string in log4j at line 1535
>
>
> [error 2019/01/31 20:14:19.857 UTC
> tid=5135]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> {noformat}
> Looking into the code, it looks like the issue is that the test triggered a
> cache close to happen in a background thread (due to the
> ConflictingPersistentDataException), but it didn't wait for the close to
> complete. The next operation the test tries to do fails because the cache is
> in the process of shutting down.
> Results URL:
> http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-3136/test-results/repeatTest/1548966963/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6379) There is a race that transaction lock could be held for a departed member and causes no other transactions can operate on the key due to commit conflict
[ https://issues.apache.org/jira/browse/GEODE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6379: --- Fix Version/s: (was: 1.10.0) 1.9.0 > There is a race that transaction lock could be held for a departed member and > causes no other transactions can operate on the key due to commit conflict > > > Key: GEODE-6379 > URL: https://issues.apache.org/jira/browse/GEODE-6379 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Currently, all transactional distributed lock held by a departed member will > be released during member departed event. However, there is a race that a > thread could execute an in-flight lock request after above mentioned event. > This will cause some keys being locked but no one would release these locks - > blocking further operations on the keys by other transactions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6473) Create a test which utilizes the geode-management.jar
[ https://issues.apache.org/jira/browse/GEODE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6473: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Create a test which utilizes the geode-management.jar > - > > Key: GEODE-6473 > URL: https://issues.apache.org/jira/browse/GEODE-6473 > Project: Geode > Issue Type: Test > Components: configuration, management, tests >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Fix For: 1.9.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > This test should exercise the new ClusterManagementService as a plain Java > client - i.e. not something that includes geode-core on the classpath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6540) Allow the cache XSD to be resolvable through HTTPS
[
https://issues.apache.org/jira/browse/GEODE-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6540:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> Allow the cache XSD to be resolvable through HTTPS
> --
>
> Key: GEODE-6540
> URL: https://issues.apache.org/jira/browse/GEODE-6540
> Project: Geode
> Issue Type: Improvement
> Components: configuration
>Affects Versions: 1.8.0
>Reporter: John Blum
>Assignee: Jacob S. Barrett
>Priority: Critical
> Labels: CacheXML, HTTP, HTTPS, XSD
> Fix For: 1.9.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, when configuring Apache Geode with {{cache.xml}}, the {{cache}}
> declaration can be specified using...
> {code:xml}
>
> http://geode.apache.org/schema/cache;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://geode.apache.org/schema/cache
> https://geode.apache.org/schema/cache/cache-1.0.xsd;
> version="1.0">
> ...
> {code}
> Notice the use of the HTTPS protocol to resolve the XSD for the namespace
> (URI) {{"http://geode.apache.org/schema/cache"}}.
> However, when starting a Geode node (e.g. server) with this {{cache.xml}},
> the following Exception is thrown...
> {code:java}
> ...
> Caused by: org.apache.geode.cache.CacheXmlException: Error while parsing XML,
> caused by org.xml.sax.SAXParseException; lineNumber: 5; columnNumber: 19;
> cvc-elt.1: Cannot find the declaration of element 'cache'.
> at
> org.apache.geode.internal.cache.xmlcache.CacheXml.error(CacheXml.java:896)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser$DefaultHandlerDelegate.error(CacheXmlParser.java:3454)
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:137)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:284)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1901)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:741)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:613)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3132)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:852)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.parse(CacheXmlParser.java:223)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4273)
> at
> org.springframework.data.gemfire.CacheFactoryBean.lambda$loadCacheXml$10(CacheFactoryBean.java:518)
> at java.util.Optional.ifPresent(Optional.java:159)
> at
> org.springframework.data.gemfire.CacheFactoryBean.loadCacheXml(CacheFactoryBean.java:515)
> at
> org.springframework.data.gemfire.CacheFactoryBean.postProcess(CacheFactoryBean.java:491)
> at
> org.springframework.data.gemfire.CacheFactoryBean.init(CacheFactoryBean.java:269)
> ... 55 more
> Caused by:
[jira] [Updated] (GEODE-6433) Fix assembly tests after upgrading to 1.10.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/GEODE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6433: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Fix assembly tests after upgrading to 1.10.0-SNAPSHOT > - > > Key: GEODE-6433 > URL: https://issues.apache.org/jira/browse/GEODE-6433 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Fix For: 1.9.0 > > > As per release steps we need to update > geode-assembly/src/integrationTest/resources/dependency_classpath.txt and > geode-assembly/src/integrationTest/resources/assembly_content.txt with the > new version (say 1.10.0-SNAPSHOT). So both *AssemblyContentsIntegrationTest* > and *GeodeDependencyJarIntegrationTest* are broken after bumping release > version to 1.10.0-SNAPSHOT. > Looks like these tests are not specifically looking at the version rather > just focusing on the actual contents. See GEODE-6075 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6457) gfsh create jdbc-mapping should find the pdx class if deployed by gfsh
[
https://issues.apache.org/jira/browse/GEODE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6457:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> gfsh create jdbc-mapping should find the pdx class if deployed by gfsh
> --
>
> Key: GEODE-6457
> URL: https://issues.apache.org/jira/browse/GEODE-6457
> Project: Geode
> Issue Type: Improvement
> Components: extensions
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, gfsh {{create jdbc-mapping}} only finds the PDX class in the
> classpath. It does not search the files deployed using 'gfsh deploy'. It
> should search the files deployed by gfsh.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6503) Move Redis apapter to geode-redis module
[ https://issues.apache.org/jira/browse/GEODE-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6503: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Move Redis apapter to geode-redis module > > > Key: GEODE-6503 > URL: https://issues.apache.org/jira/browse/GEODE-6503 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > There have been a few attempts at doing this (See GEODE-2449) but we closed > those issues without ever finishing the move. > We should get this done to reduce the number of dependencies and the size of > geode-core. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6510) update benchmark scripts for changes to key locations
[ https://issues.apache.org/jira/browse/GEODE-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6510: --- Fix Version/s: (was: 1.10.0) 1.9.0 > update benchmark scripts for changes to key locations > - > > Key: GEODE-6510 > URL: https://issues.apache.org/jira/browse/GEODE-6510 > Project: Geode > Issue Type: Bug > Components: benchmarks >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update the benchmark scripts for copying to cluster and running on cluster to > look for generated aws keys in the ~/.geode-benchmarks directory instead of > in ~/.ssh, to reflect recent changes to create cluster script. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6464) Pin OpenSSH in Windows images to version 7.7.2.1
[ https://issues.apache.org/jira/browse/GEODE-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6464: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Pin OpenSSH in Windows images to version 7.7.2.1 > > > Key: GEODE-6464 > URL: https://issues.apache.org/jira/browse/GEODE-6464 > Project: Geode > Issue Type: Test > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Fix For: 1.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The Windows images were recently rebuilt and picked up a new version of > OpenSSH (7.9.0.1). It appears that this may be causing build issues as the > Windows test runs are failing. Although the gradle call appears to complete, > the ssh call, that launches the build, does not exit properly and the job > times out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6477) GII provider should indicate that it does not persist the requester's new persistent id when processing PrepareNewPersistentMemberMessage during shutdown
[ https://issues.apache.org/jira/browse/GEODE-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6477: --- Fix Version/s: (was: 1.10.0) 1.9.0 > GII provider should indicate that it does not persist the requester's new > persistent id when processing PrepareNewPersistentMemberMessage during > shutdown > - > > Key: GEODE-6477 > URL: https://issues.apache.org/jira/browse/GEODE-6477 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Fix For: 1.9.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, provide does not persist the requester's new persistent id during > shutdown but it does not send a message to indicate this. The requester could > then request gii from the provider and then persists its new persistent id > and assume the provider has persisted its new id. And then it is being shut > down as well. > The end result is a requester could not be restarted if provider was > recovered first (shut down all case), as provider does not know the > requester's new persistent id and ConflictingPersistentDataException is > raised. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5012) Replace org.json with Jackson in GfJsonArray
[ https://issues.apache.org/jira/browse/GEODE-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-5012: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Replace org.json with Jackson in GfJsonArray > > > Key: GEODE-5012 > URL: https://issues.apache.org/jira/browse/GEODE-5012 > Project: Geode > Issue Type: Sub-task > Components: gfsh >Reporter: Jens Deppe >Assignee: Bruce Schuchardt >Priority: Major > Fix For: 1.9.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6033) DistributedTest rules should support bouncing and creating new VMs
[ https://issues.apache.org/jira/browse/GEODE-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6033: --- Fix Version/s: (was: 1.10.0) 1.9.0 > DistributedTest rules should support bouncing and creating new VMs > -- > > Key: GEODE-6033 > URL: https://issues.apache.org/jira/browse/GEODE-6033 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 6h > Remaining Estimate: 0h > > I just noticed that if you try to use SharedErrorCollector in a > DistributedTest that uses vm.bounce, the after() in the Rule will throw > NullPointerException in the vm that was bounced because nothing ever invoked > the before() in the new instance of that vm. > Presumably all of the DistributedTest Rules may fail in this way after using > bounce: > * DistributedDiskDirRule > * DistributedRestoreSystemProperties > * DistributedUseJacksonForJsonPathRule > * SharedCountersRule > * SharedErrorCollector -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6505) Use Enum instead of String for RegionConfig
[
https://issues.apache.org/jira/browse/GEODE-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6505:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> Use Enum instead of String for RegionConfig
> ---
>
> Key: GEODE-6505
> URL: https://issues.apache.org/jira/browse/GEODE-6505
> Project: Geode
> Issue Type: Improvement
>Reporter: Peter Tran
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> h1. Why
> For the java developer, especially for newbie of gemfire/geode, it is
> confusing to get exact type of region correct.
> *As Java developer*
> *I want* there to be a pre-defined region type, such as constant interface,
> enum or otherwise
> *So that* I can refer to it and pass it as a parameter in my code to get
> quick feedback if I misspell something.
> h2. Acceptance Criteria
> {code}
> Scenario: auto-complete like functionality
> Given I am creating a region via the RegionConfig class
> When I use the method .setType()
> Then there is a pre-defined region type for me to choose from with one of the
> following options (see setShortcutAttributes on RegionConfig.class)
> LOCAL,LOCAL_HEAP_LRU,LOCAL_OVERFLOW,LOCAL_PERSISTENT,LOCAL_PERSISTENT_OVERFLOW,PARTITION,PARTITION_HEAP_LRU,PARTITION_OVERFLOW,PARTITION_PERSISTENT,PARTITION_PERSISTENT_OVERFLOW,PARTITION_PROXY,PARTITION_PROXY_REDUNDANT,PARTITION_REDUNDANT,PARTITION_REDUNDANT_HEAP_LRU,PARTITION_REDUNDANT_OVERFLOW,PARTITION_REDUNDANT_PERSISTENT,PARTITION_REDUNDANT_PERSISTENT_OVERFLOW,REPLICATE,REPLICATE_HEAP_LRU,REPLICATE_OVERFLOW,REPLICATE_PERSISTENT,REPLICATE_PERSISTENT_OVERFLOW,REPLICATE_PROXY
>AND an example usage is provided on the wiki{code}
> {code}
> Scenario: Wiki
> Given I am looking at our wiki page
> When I review the example code for create region
> Then I am able to see all of the possible region types and how to properly
> specify each.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6492) Geode should fail gracefully if the HttpService cannot be started
[
https://issues.apache.org/jira/browse/GEODE-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6492:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> Geode should fail gracefully if the HttpService cannot be started
> -
>
> Key: GEODE-6492
> URL: https://issues.apache.org/jira/browse/GEODE-6492
> Project: Geode
> Issue Type: Bug
> Components: configuration, management
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Previously, starting our various webapps, would simply be dependent on the
> presence of the .war file. Anyone building and testing a Geode would
> typically not care whether theses additional services were available and
> would not notice their absence.
> Now we have a new {{HttpService}} which will attempt to start regardless of
> the presence of any .war files. This now also implies that various jetty jars
> need to be available. When building with maven or gradle, the necessary
> dependencies are marked as {{optional}} which means that a vanilla built app
> (configured without those optional dependencies) will not start.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6441) PartitionedRegionSingleHopDUnitTest.testServerLocationRemovalThroughPing flaky
[
https://issues.apache.org/jira/browse/GEODE-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6441:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> PartitionedRegionSingleHopDUnitTest.testServerLocationRemovalThroughPing flaky
> --
>
> Key: GEODE-6441
> URL: https://issues.apache.org/jira/browse/GEODE-6441
> Project: Geode
> Issue Type: Bug
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> Found in
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/421
> > Task :geode-core:distributedTest
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest >
> testServerLocationRemovalThroughPing FAILED
> java.lang.AssertionError: expected:<4> but was:<3>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.testServerLocationRemovalThroughPing(PartitionedRegionSingleHopDUnitTest.java:673)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6480) use long cli options in benchmark scripts
[ https://issues.apache.org/jira/browse/GEODE-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6480: --- Fix Version/s: (was: 1.10.0) 1.9.0 > use long cli options in benchmark scripts > - > > Key: GEODE-6480 > URL: https://issues.apache.org/jira/browse/GEODE-6480 > Project: Geode > Issue Type: Improvement > Components: benchmarks >Reporter: Helena Bales >Assignee: Helena Bales >Priority: Major > Fix For: 1.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > There are many cli options, and too many that start with the letter 'b', in > the benchmark scripts. This makes it difficult to remember all of the > single-letter cli options. Long (full-word) options would make it easier to > remember the option names for the benchmark scripts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6291) gfsh create jdbc-mapping should store pdx field to JDBC table column mapping to cluster config
[ https://issues.apache.org/jira/browse/GEODE-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6291: --- Fix Version/s: (was: 1.10.0) 1.9.0 > gfsh create jdbc-mapping should store pdx field to JDBC table column mapping > to cluster config > -- > > Key: GEODE-6291 > URL: https://issues.apache.org/jira/browse/GEODE-6291 > Project: Geode > Issue Type: Improvement > Components: extensions >Affects Versions: 1.9.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Currently 'gfsh create jdbc-mapping' does not define any of the actual pdx > field to column mapping information. Instead it just waits until a get or put > is done and then figures out how to do the mapping. > gfsh create jdbc-mapping should instead read the meta data from the table and > figure out how to map the columns to pdx. The mapping it determines should be > stored in cluster config. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6425) Region stats for get/put/etc. roll over to negative values during benchmark
[ https://issues.apache.org/jira/browse/GEODE-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6425: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Region stats for get/put/etc. roll over to negative values during benchmark > --- > > Key: GEODE-6425 > URL: https://issues.apache.org/jira/browse/GEODE-6425 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Jacob S. Barrett >Priority: Major > Fix For: 1.9.0 > > Time Spent: 2h > Remaining Estimate: 0h > > The region stats for put, gets, etc. are all implemented with an integer > counter. This counter rolls over in less than 5 minutes on the function > benchmarks, which perform fast get operations on execution. When viewed in a > stats viewer, like VSD, the values go cause massive peaks and valleys. > Increase these stats to long counters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6422) CI Failure: ConcurrencyRuleTest. repeatUntilValue fails with TimeoutException
[
https://issues.apache.org/jira/browse/GEODE-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6422:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> CI Failure: ConcurrencyRuleTest. repeatUntilValue fails with TimeoutException
> -
>
> Key: GEODE-6422
> URL: https://issues.apache.org/jira/browse/GEODE-6422
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Benjamin P Ross
>Assignee: Helena Bales
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Stack Trace:
> {noformat}
> org.apache.geode.test.junit.rules.ConcurrencyRuleTest >
> repeatUntilValue(EXECUTE_IN_PARALLEL) [0] FAILED
> java.lang.RuntimeException: java.util.concurrent.TimeoutException
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule$ProtectedErrorCollector.verify(ConcurrencyRule.java:489)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule.executeInParallel(ConcurrencyRule.java:154)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRuleTest$Execution.lambda$static$1(ConcurrencyRuleTest.java:619)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRuleTest$Execution.execute(ConcurrencyRuleTest.java:629)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRuleTest.repeatUntilValue(ConcurrencyRuleTest.java:419)
> Caused by:
> java.util.concurrent.TimeoutException
> at java.util.concurrent.FutureTask.get(FutureTask.java:205)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule.awaitFuture(ConcurrencyRule.java:227)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule.awaitFutures(ConcurrencyRule.java:219)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule.executeInParallel(ConcurrencyRule.java:153)
> ... 3 more
> {noformat}
> Artifacts can be downloaded:
> gs://files-gemfire-dev/builds/gemfire-develop-main/1.9.0-build.0427/test-artifacts/1550270829/windows-unittestfiles-OpenJDK8-1.9.0-build.0427.tgz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6420) Cleanup GetRegionsFunctionTest
[ https://issues.apache.org/jira/browse/GEODE-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6420: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Cleanup GetRegionsFunctionTest > -- > > Key: GEODE-6420 > URL: https://issues.apache.org/jira/browse/GEODE-6420 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Combine and cleanup GetRegionsFunctionTest and > GetRegionsFunctionCacheFactoryTest. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6443) Log all requests to REST ManagementService
[ https://issues.apache.org/jira/browse/GEODE-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6443: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Log all requests to REST ManagementService > -- > > Key: GEODE-6443 > URL: https://issues.apache.org/jira/browse/GEODE-6443 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Fix For: 1.9.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6474) CI failure: ConcurrencyRuleTest.repeatForDuration fails with ConditionTimeoutException
[
https://issues.apache.org/jira/browse/GEODE-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6474:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> CI failure: ConcurrencyRuleTest.repeatForDuration fails with
> ConditionTimeoutException
> --
>
> Key: GEODE-6474
> URL: https://issues.apache.org/jira/browse/GEODE-6474
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Helena Bales
>Priority: Major
> Fix For: 1.9.0
>
>
> ConcurrencyRuleTest.repeatForDuration fails intermittently in CI:
> {noformat}
> org.apache.geode.test.junit.rules.ConcurrencyRuleTest >
> repeatForDuration(EXECUTE_IN_PARALLEL) [1] FAILED
> org.awaitility.core.ConditionTimeoutException: Condition with alias
> 'Execution respects given duration' didn't complete within 2000 milliseconds
> because condition with lambda expression in
> org.apache.geode.test.junit.rules.ConcurrencyRuleTest was not fulfilled.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRuleTest.repeatForDuration(ConcurrencyRuleTest.java:398)
> {noformat}
> CI failure:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/305|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/305]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0003/test-results/test/1551408641/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0003/test-artifacts/1551408641/windows-unittestfiles-OpenJDK11-1.10.0-SNAPSHOT.0003.tgz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6508) aws README.md has some typos and out dated information
[ https://issues.apache.org/jira/browse/GEODE-6508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6508: --- Fix Version/s: (was: 1.10.0) 1.9.0 > aws README.md has some typos and out dated information > -- > > Key: GEODE-6508 > URL: https://issues.apache.org/jira/browse/GEODE-6508 > Project: Geode > Issue Type: Bug > Components: benchmarks >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Trivial > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > # ./run-tests should be changed to ./run_against_baseline.sh > # run_test.sh should be changed to run_tests.sh and run_against_baseline.sh > in the corresponding sections. > # building an image is not required to run the scripts > # give some instructions on how to figure out if aws cli is installed and if > not how to install > # give some instructions on how to answer the prompts when you run: aws > configure --profile geode-benchmarks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6442) Statistics numericId should default to PID and textId should default to Member Name
[ https://issues.apache.org/jira/browse/GEODE-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6442: --- Fix Version/s: (was: 1.10.0) 1.9.0 > Statistics numericId should default to PID and textId should default to > Member Name > --- > > Key: GEODE-6442 > URL: https://issues.apache.org/jira/browse/GEODE-6442 > Project: Geode > Issue Type: Bug > Components: statistics >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Fix For: 1.9.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > StatSampler should use PID if available and fall back to DistributedSystem ID > if the PID is unavailable. This is used to help identify the OS and Process > Statistics. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6550) AlterRegionCommand Fails to set CacheWriter
[
https://issues.apache.org/jira/browse/GEODE-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-6550:
---
Fix Version/s: (was: 1.10.0)
1.9.0
> AlterRegionCommand Fails to set CacheWriter
> ---
>
> Key: GEODE-6550
> URL: https://issues.apache.org/jira/browse/GEODE-6550
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{alter region}} command checks the nullity of the {{cache-writer}}
> parameter but, when altering the region, sets the {{cache-loader}} attribute
> instead.
> {code:java|title=AlterRegionCommand.java|borderStyle=solid}
> public ResultModel alterRegion(...) {
> ...
> if (cacheWriter != null) {
> regionAttributesType.setCacheWriter(
> new DeclarableType(cacheLoader.getClassName(),
> cacheLoader.getInitProperties()));
> }
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6044) java.lang.OutOfMemoryError: Java heap space when running DUnit tests using java11
[
https://issues.apache.org/jira/browse/GEODE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793913#comment-16793913
]
Sai Boorlagadda commented on GEODE-6044:
This happened on 1.9.0 release branch.
{noformat}
rg.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest >
testCreateMaximumSenders FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest$$Lambda$394/0x000840596040.run
in VM 4 running on Host 0e035e3a3086 with 8 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
at
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest.testCreateMaximumSenders(SerialGatewaySenderQueueDUnitTest.java:357)
Caused by:
java.lang.OutOfMemoryError: Java heap space
at
org.apache.geode.internal.cache.DiskInitFile.openRAF2(DiskInitFile.java:1577)
at
org.apache.geode.internal.cache.DiskInitFile.openRAF(DiskInitFile.java:1541)
at
org.apache.geode.internal.cache.DiskInitFile.(DiskInitFile.java:1915)
at
org.apache.geode.internal.cache.DiskStoreImpl.loadFiles(DiskStoreImpl.java:1936)
at
org.apache.geode.internal.cache.DiskStoreImpl.(DiskStoreImpl.java:470)
at
org.apache.geode.internal.cache.DiskStoreImpl.(DiskStoreImpl.java:384)
at
org.apache.geode.internal.cache.DiskStoreImpl.(DiskStoreImpl.java:379)
at
org.apache.geode.internal.cache.DiskStoreFactoryImpl.create(DiskStoreFactoryImpl.java:145)
at
org.apache.geode.internal.cache.wan.WANTestBase.configureGateway(WANTestBase.java:1702)
at
org.apache.geode.internal.cache.wan.WANTestBase.createSenderWithMultipleDispatchers(WANTestBase.java:1740)
at
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest.lambda$testCreateMaximumSenders$ca180b8$1(SerialGatewaySenderQueueDUnitTest.java:357){noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0017/test-results/distributedTest/1552550192/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-release-1-9-0-main/1.9.0-SNAPSHOT.0017/test-artifacts/1552550192/distributedtestfiles-OpenJDK11-1.9.0-SNAPSHOT.0017.tgz
> java.lang.OutOfMemoryError: Java heap space when running DUnit tests using
> java11
> -
>
> Key: GEODE-6044
> URL: https://issues.apache.org/jira/browse/GEODE-6044
> Project: Geode
> Issue Type: Sub-task
>Affects Versions: 1.8.0
>Reporter: Robert Houghton
>Assignee: Jinmei Liao
>Priority: Major
>
> The OOME errors seem to happen after executing these tests:
> org.apache.geode.internal.cache.wan.offheap.SerialGatewaySenderQueueOffHeapDUnitTest
> > testCreateMaximumSenders
> testCreateMaximumPlusOneSenders
> REPRODUCED:
> DistributedTestOpenJDK11 job 105 failed in the same way.
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.140/test-results/distributedTest/1542056138/
>
> Log (abridged)
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest$$Lambda$377/0x000840571840.run
> in VM 2 running on Host 72ac34082783 with 8 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:433)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:402)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:361)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest.testCreateMaximumSenders(SerialGatewaySenderQueueDUnitTest.java:370)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
[jira] [Updated] (GEODE-6533) Update LICENSE and NOTICE files for changed dependencies
[ https://issues.apache.org/jira/browse/GEODE-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-6533: --- Summary: Update LICENSE and NOTICE files for changed dependencies (was: Update LICENSE and NOTICES for new dependencies) > Update LICENSE and NOTICE files for changed dependencies > > > Key: GEODE-6533 > URL: https://issues.apache.org/jira/browse/GEODE-6533 > Project: Geode > Issue Type: Task >Reporter: Sai Boorlagadda >Priority: Major > > Update licenses for the dependencies that were changed recently on develop: > Here’s the list of additions: > animal-sniffer-annotations-1.17.jar > checker-qual-2.5.2.jar > commons-math3-3.2.jar > error_prone_annotations-2.2.0.jar > failureaccess-1.0.jar > geo-0.7.1.jar > grumpy-core-0.2.2.jar > istack-commons-runtime-2.2.jar > j2objc-annotations-1.1.jar > javax.activation-1.2.0.jar > javax.activation-api-1.2.0.jar > jsr305-3.0.2.jar > listenablefuture-.0-empty-to-avoid-conflict-with-guava.jar > Removed: > activation-1.1.1 > jaxb-core-2.2.11.jar -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6533) Update LICENSE and NOTICES for new dependencies
Sai Boorlagadda created GEODE-6533: -- Summary: Update LICENSE and NOTICES for new dependencies Key: GEODE-6533 URL: https://issues.apache.org/jira/browse/GEODE-6533 Project: Geode Issue Type: Task Reporter: Sai Boorlagadda Update licenses for the dependencies that were changed recently on develop: Here’s the list of additions: animal-sniffer-annotations-1.17.jar checker-qual-2.5.2.jar commons-math3-3.2.jar error_prone_annotations-2.2.0.jar failureaccess-1.0.jar geo-0.7.1.jar grumpy-core-0.2.2.jar istack-commons-runtime-2.2.jar j2objc-annotations-1.1.jar javax.activation-1.2.0.jar javax.activation-api-1.2.0.jar jsr305-3.0.2.jar listenablefuture-.0-empty-to-avoid-conflict-with-guava.jar Removed: activation-1.1.1 jaxb-core-2.2.11.jar -- This message was sent by Atlassian JIRA (v7.6.3#76005)
