[jira] [Commented] (IGNITE-20466) Investigate running sonar checks from fork repositories
[ https://issues.apache.org/jira/browse/IGNITE-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770397#comment-17770397 ] Maxim Muzafarov commented on IGNITE-20466: -- References: pull_request_target https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target Checking out a merge commit in pull_request_target workflows #518 https://github.com/actions/checkout/issues/518 Feature Request |trigger action on "Pull Request Approved" #25372 https://github.com/orgs/community/discussions/25372 Run Sonar scan for PRs from forks https://stackoverflow.com/questions/76528833/run-sonar-scan-for-prs-from-forks How to use SonarCloud with a forked repository on GitHub? https://community.sonarsource.com/t/how-to-use-sonarcloud-with-a-forked-repository-on-github/7363/30 > Investigate running sonar checks from fork repositories > --- > > Key: IGNITE-20466 > URL: https://issues.apache.org/jira/browse/IGNITE-20466 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > > Investigate running sonar checks from fork repositories. > See the discussion here: > https://github.com/actions/checkout/issues/518 > Additionally, we can run checks after a pull-request has been approved by a > maintainer: > https://github.com/orgs/community/discussions/25372 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20490: - Affects Version/s: 2.15 > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Affects Versions: 2.15 >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20490: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20490: - Release Note: Updates snappy java dependency up to the latest 1.1.10.4 > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769101#comment-17769101 ] Maxim Muzafarov commented on IGNITE-20490: -- Merged to the master branch. [~NIzhikov] thank you for the review. > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
[ https://issues.apache.org/jira/browse/IGNITE-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20490: - Release Note: (was: Merged to the master branch. [~NIzhikov] thank you for the review.) > Update the snappy dependency in order to fix CVEs > - > > Key: IGNITE-20490 > URL: https://issues.apache.org/jira/browse/IGNITE-20490 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The dependency needs to be updated to fix CVE: > https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20490) Update the snappy dependency in order to fix CVEs
Maxim Muzafarov created IGNITE-20490: Summary: Update the snappy dependency in order to fix CVEs Key: IGNITE-20490 URL: https://issues.apache.org/jira/browse/IGNITE-20490 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.16 The dependency needs to be updated to fix CVE: https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20466) Investigate running sonar checks from fork repositories
Maxim Muzafarov created IGNITE-20466: Summary: Investigate running sonar checks from fork repositories Key: IGNITE-20466 URL: https://issues.apache.org/jira/browse/IGNITE-20466 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Investigate running sonar checks from fork repositories. See the discussion here: https://github.com/actions/checkout/issues/518 Additionally, we can run checks after a pull-request has been approved by a maintainer: https://github.com/orgs/community/discussions/25372 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20274) Github actions must rely on environment variables instead of context
[ https://issues.apache.org/jira/browse/IGNITE-20274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-20274: - Ignite Flags: (was: Docs Required,Release Notes Required) > Github actions must rely on environment variables instead of context > > > Key: IGNITE-20274 > URL: https://issues.apache.org/jira/browse/IGNITE-20274 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Github actions that are used to perform verification against the source code > must use environment variables set directly on the action. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20274) Github actions must rely on environment variables instead of context
[ https://issues.apache.org/jira/browse/IGNITE-20274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17758536#comment-17758536 ] Maxim Muzafarov commented on IGNITE-20274: -- Merged to the master branch. > Github actions must rely on environment variables instead of context > > > Key: IGNITE-20274 > URL: https://issues.apache.org/jira/browse/IGNITE-20274 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Github actions that are used to perform verification against the source code > must use environment variables set directly on the action. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20274) Github actions must rely on environment variables instead of context
Maxim Muzafarov created IGNITE-20274: Summary: Github actions must rely on environment variables instead of context Key: IGNITE-20274 URL: https://issues.apache.org/jira/browse/IGNITE-20274 Project: Ignite Issue Type: Bug Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.16 Github actions that are used to perform verification against the source code must use environment variables set directly on the action. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Fix Version/s: 2.15
(was: 2.16)
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.15
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
> [INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
> [INFO]
> {code}
> Host runners for GitHub:
> https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
> Reference for OOM:
> https://community.sonarsource.com/t/oome-in-analysis/79571
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19178) Add Sonar to Ignite project to analyze sources
[ https://issues.apache.org/jira/browse/IGNITE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-19178: - Fix Version/s: 2.15 (was: 2.16) > Add Sonar to Ignite project to analyze sources > -- > > Key: IGNITE-19178 > URL: https://issues.apache.org/jira/browse/IGNITE-19178 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.15 > > Time Spent: 20m > Remaining Estimate: 0h > > Sonar is a code quality and security tool that is free to open-source > projects and recommended by the INFRA team the link for documentation: > https://cwiki.apache.org/confluence/display/INFRA/SonarCloud+for+ASF+projects > Despite in commonly used by many of the ASF projects, it can have the > following benefits for us: > - visualise simple problems for newcomers to work on; > - see the trends in the source code; > - add an extra layer of static code analysis; > The INFRA ticket: > https://issues.apache.org/jira/browse/INFRA-24415 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov resolved IGNITE-19266.
--
Resolution: Fixed
[~NSAmelchev] thank you for the review. Merged to the master branch.
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
> [INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
> [INFO]
> {code}
> Host runners for GitHub:
> https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
> Reference for OOM:
> https://community.sonarsource.com/t/oome-in-analysis/79571
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Fix Version/s: 2.16
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
> [INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
> [INFO]
> {code}
> Host runners for GitHub:
> https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
> Reference for OOM:
> https://community.sonarsource.com/t/oome-in-analysis/79571
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Description:
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
Host runners for GitHub:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
Reference for OOM:
https://community.sonarsource.com/t/oome-in-analysis/79571
was:
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
Host runners for GitHub:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Description:
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
Host runners for GitHub:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
was:
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
[jira] [Updated] (IGNITE-19266) Sonar Analysis fails with Java heap space
[
https://issues.apache.org/jira/browse/IGNITE-19266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-19266:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Sonar Analysis fails with Java heap space
> -
>
> Key: IGNITE-19266
> URL: https://issues.apache.org/jira/browse/IGNITE-19266
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.16
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
>
> https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
> {code}
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
> This sink will not be analyzed any further.
> [INFO] Too high simulation costs for sink in
> /home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
> This sink will not be analyzed any further.
> [INFO] Time spent writing ucfgs 0ms
> Error: Exception in thread "HttpClient-1-Worker-5"
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
>
> [INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
> [INFO]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-19266) Sonar Analysis fails with Java heap space
Maxim Muzafarov created IGNITE-19266:
Summary: Sonar Analysis fails with Java heap space
Key: IGNITE-19266
URL: https://issues.apache.org/jira/browse/IGNITE-19266
Project: Ignite
Issue Type: Task
Affects Versions: 2.16
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
https://github.com/apache/ignite/actions/runs/463944/jobs/8210274861
{code}
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java:124.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java:2581.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:103.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/MarshallerMappingFileStore.java:95.
This sink will not be analyzed any further.
[INFO] Too high simulation costs for sink in
/home/runner/work/ignite/ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/diagnostic/DiagnosticProcessor.java:162.
This sink will not be analyzed any further.
[INFO] Time spent writing ucfgs 0ms
Error: Exception in thread "HttpClient-1-Worker-5" java.lang.OutOfMemoryError:
Java heap space
[INFO]
[INFO] Reactor Summary for apache-ignite 2.15.0-SNAPSHOT:
[INFO]
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19178) Add Sonar to Ignite project to analyze sources
[ https://issues.apache.org/jira/browse/IGNITE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709727#comment-17709727 ] Maxim Muzafarov commented on IGNITE-19178: -- [~NSAmelchev] thank you for the review. Merged to the master branch. Examples of Sonar Analysis: https://sonarcloud.io/summary/overall?id=apache_ignite A PR Analysis: https://github.com/apache/ignite/pull/10629 > Add Sonar to Ignite project to analyze sources > -- > > Key: IGNITE-19178 > URL: https://issues.apache.org/jira/browse/IGNITE-19178 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > Sonar is a code quality and security tool that is free to open-source > projects and recommended by the INFRA team the link for documentation: > https://cwiki.apache.org/confluence/display/INFRA/SonarCloud+for+ASF+projects > Despite in commonly used by many of the ASF projects, it can have the > following benefits for us: > - visualise simple problems for newcomers to work on; > - see the trends in the source code; > - add an extra layer of static code analysis; > The INFRA ticket: > https://issues.apache.org/jira/browse/INFRA-24415 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19178) Add Sonar to Ignite project to analyze sources
[ https://issues.apache.org/jira/browse/IGNITE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-19178: - Summary: Add Sonar to Ignite project to analyze sources (was: Add Sonar to Ignite project to analyze master and release branches) > Add Sonar to Ignite project to analyze sources > -- > > Key: IGNITE-19178 > URL: https://issues.apache.org/jira/browse/IGNITE-19178 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > > Sonar is a code quality and security tool that is free to open-source > projects and recommended by the INFRA team the link for documentation: > https://cwiki.apache.org/confluence/display/INFRA/SonarCloud+for+ASF+projects > Despite in commonly used by many of the ASF projects, it can have the > following benefits for us: > - visualise simple problems for newcomers to work on; > - see the trends in the source code; > - add an extra layer of static code analysis; > The INFRA ticket: > https://issues.apache.org/jira/browse/INFRA-24415 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19178) Add Sonar to Ignite project to analyze master and release branches
[ https://issues.apache.org/jira/browse/IGNITE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-19178: - Ignite Flags: (was: Docs Required,Release Notes Required) > Add Sonar to Ignite project to analyze master and release branches > -- > > Key: IGNITE-19178 > URL: https://issues.apache.org/jira/browse/IGNITE-19178 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > > Sonar is a code quality and security tool that is free to open-source > projects and recommended by the INFRA team the link for documentation: > https://cwiki.apache.org/confluence/display/INFRA/SonarCloud+for+ASF+projects > Despite in commonly used by many of the ASF projects, it can have the > following benefits for us: > - visualise simple problems for newcomers to work on; > - see the trends in the source code; > - add an extra layer of static code analysis; > The INFRA ticket: > https://issues.apache.org/jira/browse/INFRA-24415 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-19178) Add Sonar to Ignite project to analyze master and release branches
Maxim Muzafarov created IGNITE-19178: Summary: Add Sonar to Ignite project to analyze master and release branches Key: IGNITE-19178 URL: https://issues.apache.org/jira/browse/IGNITE-19178 Project: Ignite Issue Type: Task Components: build Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.16 Sonar is a code quality and security tool that is free to open-source projects and recommended by the INFRA team the link for documentation: https://cwiki.apache.org/confluence/display/INFRA/SonarCloud+for+ASF+projects Despite in commonly used by many of the ASF projects, it can have the following benefits for us: - visualise simple problems for newcomers to work on; - see the trends in the source code; - add an extra layer of static code analysis; The INFRA ticket: https://issues.apache.org/jira/browse/INFRA-24415 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15287) Yardstick's -cwd params does not clean persistence and wal directories
[
https://issues.apache.org/jira/browse/IGNITE-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15287:
-
Fix Version/s: (was: 2.10)
> Yardstick's -cwd params does not clean persistence and wal directories
> --
>
> Key: IGNITE-15287
> URL: https://issues.apache.org/jira/browse/IGNITE-15287
> Project: Ignite
> Issue Type: Bug
> Environment: -
>Reporter: Anton Vinogradov
>Priority: Major
>
> The current code at IgniteNode.java is
> {noformat}
> if (args.cleanWorkDirectory() && !clientMode)
> FileUtils.cleanDirectory(U.workDirectory(c.getWorkDirectory(),
> c.getIgniteHome()));
> {noformat}
> and we should append {{dataStorageConfiguration#storagePath}} and
> {{dataStorageConfiguration#walPath}} clean-up as well.
> Why it's important:
> For example, hawing following configuration
> {noformat}
> class="org.apache.ignite.configuration.DataStorageConfiguration">
>
>
>
>
>
>
>
>
>
>
>
>
>
> {noformat}
> We will use same persistence each time we running benchmarks, this means
> we'll gain different numbers each time :(
> {{/mnt/ssd/wal}} will grow until possible, and {{/mnt/ssd/persistence}} will
> be different before each benchmark start.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17915) Generalize support for inversion of control mechanisms
[
https://issues.apache.org/jira/browse/IGNITE-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676388#comment-17676388
]
Maxim Muzafarov commented on IGNITE-17915:
--
[~ldywicki] I've added you to the Contributors list. Please, check that you're
able to assign the issue.
> Generalize support for inversion of control mechanisms
> ---
>
> Key: IGNITE-17915
> URL: https://issues.apache.org/jira/browse/IGNITE-17915
> Project: Ignite
> Issue Type: Improvement
> Components: spring
>Affects Versions: 2.14
>Reporter: Łukasz Dywicki
>Priority: Major
> Labels: patch-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current inversion of control support for Ignite is bound to Spring framework
> and Spring ApplicationContext interface which is used to lookup beans by type
> or name.
> Above lookup criteria are fairly generic and can be used to first - extract,
> second - generalize support for foreign injections within Ignite itself. With
> little work it is possible to open this for further extensions. This is known
> pattern used in other Apache projects, ie.
> [{{BeanRepository}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/BeanRepository.java]
> and
> [{{Registry}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/Registry.java].
> Main motivation is Ignite running under OSGi which does not host Spring
> (Spring framework dropped support for OSGi a while ago), and has alternative
> ways to provide similar functionality. For OSGi there are mechanisms such as
> OSGi Blueprint and OSGi Service Registry itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17915) Generalize support for inversion of control mechanisms
[
https://issues.apache.org/jira/browse/IGNITE-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676364#comment-17676364
]
Maxim Muzafarov commented on IGNITE-17915:
--
I will take a look within the next few weeks.
[~ldywicki] you can assign the issue to yourself and set the right status.
> Generalize support for inversion of control mechanisms
> ---
>
> Key: IGNITE-17915
> URL: https://issues.apache.org/jira/browse/IGNITE-17915
> Project: Ignite
> Issue Type: Improvement
> Components: spring
>Affects Versions: 2.14
>Reporter: Łukasz Dywicki
>Priority: Major
> Labels: patch-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current inversion of control support for Ignite is bound to Spring framework
> and Spring ApplicationContext interface which is used to lookup beans by type
> or name.
> Above lookup criteria are fairly generic and can be used to first - extract,
> second - generalize support for foreign injections within Ignite itself. With
> little work it is possible to open this for further extensions. This is known
> pattern used in other Apache projects, ie.
> [{{BeanRepository}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/BeanRepository.java]
> and
> [{{Registry}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/Registry.java].
> Main motivation is Ignite running under OSGi which does not host Spring
> (Spring framework dropped support for OSGi a while ago), and has alternative
> ways to provide similar functionality. For OSGi there are mechanisms such as
> OSGi Blueprint and OSGi Service Registry itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-17738) Cluster must be able to fix the inconsistency on restart/node_join by itself
[
https://issues.apache.org/jira/browse/IGNITE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov reassigned IGNITE-17738:
Assignee: Maxim Muzafarov
> Cluster must be able to fix the inconsistency on restart/node_join by itself
>
>
> Key: IGNITE-17738
> URL: https://issues.apache.org/jira/browse/IGNITE-17738
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: iep-31, ise
> Attachments: PartialHistoricalRebalanceTest.java,
> SkippedRebalanceBecauseOfTheSameLwmTest.java
>
>
> On cluster restart (because of power-off, OOM or some other problem) it's
> possible to have PDS inconsistent (primary partitions may contain operations
> missed on backups as well as counters may contain gaps even on primary).
> 1) Currently, "historical rebalance" is able to sync the data to the highest
> LWM for every partition.
> Most likely, a primary will be chosen as a rebalance source, but the data
> after the LWM will not be rebalanced. So, all updates between LWM and HWM
> will not be synchronized.
> See [^PartialHistoricalRebalanceTest.java]
> Such partition may be rebalanced correctly "later" in case of full rebalance
> will be triggered sometime.
> 2) In case LWM is the same on primary and backup, rebalance will be skipped
> for such partition.
> See [^SkippedRebalanceBecauseOfTheSameLwmTest.java]
> Proposals:
> 1) Cheap fix
> A possible solution for the case when the cluster failed and restarted (same
> baseline) is to fix the counters automatically (when cluster composition is
> equal to the baseline specified before the crash).
> Counters should be set as
> - HWM at primary and as LWM at backups for caches with 2+ backups,
> - LWM at primary and as HWM at backups for caches with a single backup.
> 2) Correct fix
> Rebalance must honor whole counter state (LWM, HWM, gaps).
> 2.0) Primary HWM must be set to the highest HWM across the copies to avoid
> reapplying of already applied update counters on backups.
> 2.1) In case when WAL is available all entries between LWM and HWM
> (including) must be rebalanced to other nodes where they are required.
> Even from backups to the primary.
> 2.2) Full rebalance must be restricted when it causes any updates loss.
> For example, it's
> - ok to replace B with A when
> A[lwm=100, gaps=[142], hwm=200] and B[lwm=50, gaps=[76,99,111], hwm=120],
> because A contains whole B.
> - NOT ok to replace B with A when
> A[lwm=100, gaps=[142], hwm=200] and B[lwm=50, gaps=[76,99,111],
> hwm={*}148{*}],
> when update *142* will be lost.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17738) Cluster must be able to fix the inconsistency on restart/node_join by itself
[
https://issues.apache.org/jira/browse/IGNITE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17738:
-
Fix Version/s: 2.15
> Cluster must be able to fix the inconsistency on restart/node_join by itself
>
>
> Key: IGNITE-17738
> URL: https://issues.apache.org/jira/browse/IGNITE-17738
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: iep-31, ise
> Fix For: 2.15
>
> Attachments: PartialHistoricalRebalanceTest.java,
> SkippedRebalanceBecauseOfTheSameLwmTest.java
>
>
> On cluster restart (because of power-off, OOM or some other problem) it's
> possible to have PDS inconsistent (primary partitions may contain operations
> missed on backups as well as counters may contain gaps even on primary).
> 1) Currently, "historical rebalance" is able to sync the data to the highest
> LWM for every partition.
> Most likely, a primary will be chosen as a rebalance source, but the data
> after the LWM will not be rebalanced. So, all updates between LWM and HWM
> will not be synchronized.
> See [^PartialHistoricalRebalanceTest.java]
> Such partition may be rebalanced correctly "later" in case of full rebalance
> will be triggered sometime.
> 2) In case LWM is the same on primary and backup, rebalance will be skipped
> for such partition.
> See [^SkippedRebalanceBecauseOfTheSameLwmTest.java]
> Proposals:
> 1) Cheap fix
> A possible solution for the case when the cluster failed and restarted (same
> baseline) is to fix the counters automatically (when cluster composition is
> equal to the baseline specified before the crash).
> Counters should be set as
> - HWM at primary and as LWM at backups for caches with 2+ backups,
> - LWM at primary and as HWM at backups for caches with a single backup.
> 2) Correct fix
> Rebalance must honor whole counter state (LWM, HWM, gaps).
> 2.0) Primary HWM must be set to the highest HWM across the copies to avoid
> reapplying of already applied update counters on backups.
> 2.1) In case when WAL is available all entries between LWM and HWM
> (including) must be rebalanced to other nodes where they are required.
> Even from backups to the primary.
> 2.2) Full rebalance must be restricted when it causes any updates loss.
> For example, it's
> - ok to replace B with A when
> A[lwm=100, gaps=[142], hwm=200] and B[lwm=50, gaps=[76,99,111], hwm=120],
> because A contains whole B.
> - NOT ok to replace B with A when
> A[lwm=100, gaps=[142], hwm=200] and B[lwm=50, gaps=[76,99,111],
> hwm={*}148{*}],
> when update *142* will be lost.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-15629) Cluster Management API
[ https://issues.apache.org/jira/browse/IGNITE-15629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-15629: - Labels: iep-81 important ise (was: iep-81 important) > Cluster Management API > -- > > Key: IGNITE-15629 > URL: https://issues.apache.org/jira/browse/IGNITE-15629 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: iep-81, important, ise > > Ignite must provide cluster management internal API in that way the other > available user APIs like REST, CLI or JMX won't require the source code > changes. > The following features must be available out of the box: > - man pages and documentation autogeneration > - registering new commands from plugins -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15516:
-
Labels: ise (was: )
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
> Labels: ise
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov reassigned IGNITE-15516:
Assignee: Maxim Muzafarov
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: ise
> Fix For: 2.15
>
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15516:
-
Fix Version/s: 2.15
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
> Labels: ise
> Fix For: 2.15
>
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-16714) [IEP-80] Move binary metadata storage to distributed metastorage
[ https://issues.apache.org/jira/browse/IGNITE-16714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598890#comment-17598890 ] Maxim Muzafarov commented on IGNITE-16714: -- The same issues are related to the marshaller mapping also. > [IEP-80] Move binary metadata storage to distributed metastorage > > > Key: IGNITE-16714 > URL: https://issues.apache.org/jira/browse/IGNITE-16714 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Major > Labels: IEP-80, ise > > We have common way to spread internal information over the cluster - > distributed metastorage. > But, currently, binary_metadata uses own code to do the same. > Moreover, binary_metadata folder stores file separately from other Ignite > data. > This should be refactored and binary metadata stored inside distributed > metastorage. > Additionally, we can introduce tool to retrieve and upload binary schemes to > the cluster to overcome possible bugs or edgecases during migration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598591#comment-17598591
]
Maxim Muzafarov commented on IGNITE-16136:
--
[~Sawfish], [~Norbert Löffler]
Are you using the Apache Ignite 2.7.6 ? I can cherry-pick this issue to the
related branch, so you can test the patch. However, it will be a bit difficult
due to the release is completely outdated and there is no guarantee of success
for that.
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Assignee: Maxim Muzafarov
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: configuration.zip, image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(Ljava/util/concurrent/ConcurrentMap;ILjava/lang/ClassLoader;Lorg/apache/ignite/marshaller/MarshallerContext;Lorg/apache/ignite/internal/marshaller/optimized/OptimizedMarshallerIdMapper;)Lorg/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor;
> (OptimizedMarshallerUtils.java:264)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:341)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride()Ljava/lang/Object;
>
[jira] [Commented] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598573#comment-17598573
]
Maxim Muzafarov commented on IGNITE-16136:
--
[~tledkov]
You're right. The client node can't handle the mapping request due to the
SYSTEM_POOL is busy by cache event messages. The issue described above related
both for marshalling and binary metadata requests and leads for the system
thread pool starvation.
For the client node binary metadata and marshalling mappings propaged thought
the discovery and communication SPIs. If the client node is waiting for the
reply from the server node and concurrently receives the required mappings from
discovery messages, then we can for sure release the thread locks immediately,
thus no starvation will occur.
Moving processing of such a messages to the dedicated pool sound reasonable for
me, but should be widely discussed with the whole Community. Currently, there
is no need of such an actions to fix the starvation.
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Assignee: Maxim Muzafarov
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: configuration.zip, image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
>
[jira] [Updated] (IGNITE-17033) Move ignite-aop to the Ignite Extensions
[ https://issues.apache.org/jira/browse/IGNITE-17033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17033: - Release Note: Moved inigte-aop module to the Ignite Extensions project > Move ignite-aop to the Ignite Extensions > > > Key: IGNITE-17033 > URL: https://issues.apache.org/jira/browse/IGNITE-17033 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > The ignite-aop module must be moved to the Ignite Extension since it has not > been updated for a few years and it is not configured on TC for running tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13570: - Release Note: Moved inigte-osgi module to the Ignite Extensions project > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task > Components: extensions >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > Labels: ignite-osgi > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-12622) Forbid mixed cache groups with both atomic and transactional caches
[ https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-12622: Assignee: (was: Maxim Muzafarov) > Forbid mixed cache groups with both atomic and transactional caches > --- > > Key: IGNITE-12622 > URL: https://issues.apache.org/jira/browse/IGNITE-12622 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Ivan Rakov >Priority: Major > Labels: IEP-80, newbie > Fix For: 2.15 > > > Apparently it's possible in Ignite to configure a cache group with both > ATOMIC and TRANSACTIONAL caches. > IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. > As per discussed on dev list > (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), > the community has concluded that such configurations should be prohibited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-12622) Forbid mixed cache groups with both atomic and transactional caches
[ https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-12622: Assignee: Maxim Muzafarov > Forbid mixed cache groups with both atomic and transactional caches > --- > > Key: IGNITE-12622 > URL: https://issues.apache.org/jira/browse/IGNITE-12622 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Ivan Rakov >Assignee: Maxim Muzafarov >Priority: Major > Labels: IEP-80, newbie > Fix For: 2.15 > > > Apparently it's possible in Ignite to configure a cache group with both > ATOMIC and TRANSACTIONAL caches. > IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. > As per discussed on dev list > (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), > the community has concluded that such configurations should be prohibited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12622) Forbid mixed cache groups with both atomic and transactional caches
[ https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12622: - Labels: IEP-80 newbie (was: IEP-80) > Forbid mixed cache groups with both atomic and transactional caches > --- > > Key: IGNITE-12622 > URL: https://issues.apache.org/jira/browse/IGNITE-12622 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Ivan Rakov >Priority: Major > Labels: IEP-80, newbie > Fix For: 2.15 > > > Apparently it's possible in Ignite to configure a cache group with both > ATOMIC and TRANSACTIONAL caches. > IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. > As per discussed on dev list > (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), > the community has concluded that such configurations should be prohibited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-12622) Forbid mixed cache groups with both atomic and transactional caches
[ https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-12622: Assignee: (was: Ivan Rakov) > Forbid mixed cache groups with both atomic and transactional caches > --- > > Key: IGNITE-12622 > URL: https://issues.apache.org/jira/browse/IGNITE-12622 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Ivan Rakov >Priority: Major > Labels: IEP-80 > Fix For: 2.15 > > > Apparently it's possible in Ignite to configure a cache group with both > ATOMIC and TRANSACTIONAL caches. > IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. > As per discussed on dev list > (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), > the community has concluded that such configurations should be prohibited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12622) Forbid mixed cache groups with both atomic and transactional caches
[ https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12622: - Fix Version/s: 2.15 (was: 2.14) > Forbid mixed cache groups with both atomic and transactional caches > --- > > Key: IGNITE-12622 > URL: https://issues.apache.org/jira/browse/IGNITE-12622 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Ivan Rakov >Assignee: Ivan Rakov >Priority: Major > Labels: IEP-80 > Fix For: 2.15 > > > Apparently it's possible in Ignite to configure a cache group with both > ATOMIC and TRANSACTIONAL caches. > IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. > As per discussed on dev list > (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), > the community has concluded that such configurations should be prohibited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17581965#comment-17581965
]
Maxim Muzafarov commented on IGNITE-16136:
--
Folks,
I'm able to reproduce the issue. I will fix it soon.
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Assignee: Maxim Muzafarov
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: configuration.zip, image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(Ljava/util/concurrent/ConcurrentMap;ILjava/lang/ClassLoader;Lorg/apache/ignite/marshaller/MarshallerContext;Lorg/apache/ignite/internal/marshaller/optimized/OptimizedMarshallerIdMapper;)Lorg/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor;
> (OptimizedMarshallerUtils.java:264)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:341)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:198)
> at
> java.io.ObjectInputStream.readObject(Ljava/lang/Class;)Ljava/lang/Object;
> (ObjectInputStream.java:484)
> at java.io.ObjectInputStream.readObject()Ljava/lang/Object;
[jira] [Assigned] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov reassigned IGNITE-16136:
Assignee: Maxim Muzafarov
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Assignee: Maxim Muzafarov
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(Ljava/util/concurrent/ConcurrentMap;ILjava/lang/ClassLoader;Lorg/apache/ignite/marshaller/MarshallerContext;Lorg/apache/ignite/internal/marshaller/optimized/OptimizedMarshallerIdMapper;)Lorg/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor;
> (OptimizedMarshallerUtils.java:264)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:341)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:198)
> at
> java.io.ObjectInputStream.readObject(Ljava/lang/Class;)Ljava/lang/Object;
> (ObjectInputStream.java:484)
> at java.io.ObjectInputStream.readObject()Ljava/lang/Object;
> (ObjectInputStream.java:451)
> at
>
[jira] [Comment Edited] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17579835#comment-17579835
]
Maxim Muzafarov edited comment on IGNITE-16136 at 8/15/22 6:06 PM:
---
Please, provide the additional information about the number of registered
binary metadata types on server nodes.
{code:java}
ls -la /ingite/work/db/marshaller/ | wc -l
{code}
or since 2.10
{code:java}
select count(*) from SYS.BINARY_METADATA
{code}
[BINARY_METADATA|https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#binary_metadata]
was (Author: mmuzaf):
Please, provide the additional information about the number of registered
binary metadata types on server nodes.
{code:java}
ls -la /ingite/work/db/marshaller/ | wc -l
{code}
or since 2.12
{code:java}
select count(*) from SYS.BINARY_METADATA
{code}
[BINARY_METADATA|https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#binary_metadata]
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
>
[jira] [Commented] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17579835#comment-17579835
]
Maxim Muzafarov commented on IGNITE-16136:
--
Please, provide the additional information about the number of registered
binary metadata types on server nodes.
{code:java}
ls -la /ingite/work/db/marshaller/ | wc -l
{code}
or since 2.12
{code:java}
select count(*) from SYS.BINARY_METADATA
{code}
[BINARY_METADATA|https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#binary_metadata]
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(Ljava/util/concurrent/ConcurrentMap;ILjava/lang/ClassLoader;Lorg/apache/ignite/marshaller/MarshallerContext;Lorg/apache/ignite/internal/marshaller/optimized/OptimizedMarshallerIdMapper;)Lorg/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor;
> (OptimizedMarshallerUtils.java:264)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:341)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride()Ljava/lang/Object;
>
[jira] [Commented] (IGNITE-16136) System Thread pool starvation and out of memory
[
https://issues.apache.org/jira/browse/IGNITE-16136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17579823#comment-17579823
]
Maxim Muzafarov commented on IGNITE-16136:
--
[~Norbert Löffler] donations to the open-source are always a good thing, but I
doubt it will speedup any particular issue for investigation :-)
[~Norbert Löffler]
[~Sawfish]
Can you help with the issue investigation and describe the steps to reproduce
the issue? Can you attach configuration?
As I can see the Continuous Query and thick clients are used here.
> System Thread pool starvation and out of memory
> ---
>
> Key: IGNITE-16136
> URL: https://issues.apache.org/jira/browse/IGNITE-16136
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: David Albrecht
>Priority: Critical
> Labels: ise
> Fix For: 2.14
>
> Attachments: image-2021-12-15-21-13-43-775.png,
> image-2021-12-15-21-17-47-652.png
>
>
> We are experiencing thread pool starvations and after some time out of memory
> exceptions in some of our ignite client nodes while the server node seems to
> be running without any problems. It seems like all sys threads are stuck when
> calling MarshallerContextImpl.getClassName. Which in turn leads to a growing
> worker queue.
>
> First warnings regarding the thread pool starvation:
> {code:java}
> 10.12.21 11:22:34.603 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:27:34.654 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:32:34.713 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:37:34.764 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:42:34.796 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> 10.12.21 11:47:34.839 [WARN ]
> IgniteKernal.warning(127): Possible thread pool starvation detected (no task
> completed in last 3ms, is system thread pool size large enough?)
> {code}
> Out of memory error leading to a crash of the application:
> {code}
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "https-openssl-nio-16443-ClientPoller"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "ajp-nio-16009-ClientPoller"
> 11-Dec-2021 03:07:24.446 SEVERE [Catalina-utility-1]
> org.apache.coyote.AbstractProtocol.startAsyncTimeout Error processing async
> timeouts
> java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
> Java heap space
> {code}
> The queue full of messages:
> !image-2021-12-15-21-17-47-652.png!
> It seems like all sys threads are stuck while waiting at:
> {code}
> sys-#170
> at jdk.internal.misc.Unsafe.park(ZJ)V (Native Method)
> at java.util.concurrent.locks.LockSupport.park()V (LockSupport.java:323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(Z)Ljava/lang/Object;
> (GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get()Ljava/lang/Object;
> (GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClassName(BI)Ljava/lang/String;
> (MarshallerContextImpl.java:379)
> at
> org.apache.ignite.internal.MarshallerContextImpl.getClass(ILjava/lang/ClassLoader;)Ljava/lang/Class;
> (MarshallerContextImpl.java:344)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(Ljava/util/concurrent/ConcurrentMap;ILjava/lang/ClassLoader;Lorg/apache/ignite/marshaller/MarshallerContext;Lorg/apache/ignite/internal/marshaller/optimized/OptimizedMarshallerIdMapper;)Lorg/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor;
> (OptimizedMarshallerUtils.java:264)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0()Ljava/lang/Object;
> (OptimizedObjectInputStream.java:341)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride()Ljava/lang/Object;
>
[jira] [Assigned] (IGNITE-12662) Get rid of CacheConfiguration#getRebalanceDelay and related functionality.
[ https://issues.apache.org/jira/browse/IGNITE-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-12662: Assignee: Maxim Muzafarov > Get rid of CacheConfiguration#getRebalanceDelay and related functionality. > -- > > Key: IGNITE-12662 > URL: https://issues.apache.org/jira/browse/IGNITE-12662 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Scherbakov >Assignee: Maxim Muzafarov >Priority: Major > Labels: IEP-80 > Fix For: 2.14 > > > We have for a long time this property to mitigate a case with premature > rebalancing on node restart. > Currently this is handled by baseline topology. > I suggest to deprecate and remove related functionality in next releases. > For example org.apache.ignite.IgniteCache#rebalance is no longer needed as > well. > [Dev list > discussion|http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Deprecation-of-obsolete-rebalancing-functionality-td45824.html] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15759) [IEP-80] Removal of LOCAL caches support
[ https://issues.apache.org/jira/browse/IGNITE-15759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-15759: - Labels: IEP-80 important (was: IEP-80) > [IEP-80] Removal of LOCAL caches support > > > Key: IGNITE-15759 > URL: https://issues.apache.org/jira/browse/IGNITE-15759 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Maxim Muzafarov >Priority: Major > Labels: IEP-80, important > Fix For: 2.14 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > LOCAL cachens has huge amount of known limitation and not intended to be used > in production environment. > Should be removed in 2.13 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-11547) ClassCastException when creating LOCAL cache on client in Data Region which is considered persistent
[ https://issues.apache.org/jira/browse/IGNITE-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov resolved IGNITE-11547. -- Resolution: Won't Fix LOCAL caches removed from support. > ClassCastException when creating LOCAL cache on client in Data Region which > is considered persistent > > > Key: IGNITE-11547 > URL: https://issues.apache.org/jira/browse/IGNITE-11547 > Project: Ignite > Issue Type: Bug > Components: cache, persistence >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Madhusudhan Reddy Vennapusa >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > If default region in cluster is persistent, then creating a LOCAL cache on > client will fail with: > org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl cannot be cast > to > org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryEx > This is unless there is a second non-persistent data region, and cache is > created in this non-persistent region. > I think this case calls for a check and helpful error message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-13076) Cluster read-only mode doesn't affect LOCAL caches
[
https://issues.apache.org/jira/browse/IGNITE-13076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov resolved IGNITE-13076.
--
Resolution: Won't Fix
> Cluster read-only mode doesn't affect LOCAL caches
> --
>
> Key: IGNITE-13076
> URL: https://issues.apache.org/jira/browse/IGNITE-13076
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Sergey Antonov
>Priority: Major
> Labels: read-only-mode
>
> You can make data modification operations with LOCAL cache even if cluster in
> a {{ACTIVE_READ_ONLY}} state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-9110) Tx commit hangs after cross-cache operations with LOCAL cache
[
https://issues.apache.org/jira/browse/IGNITE-9110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov resolved IGNITE-9110.
-
Resolution: Won't Fix
> Tx commit hangs after cross-cache operations with LOCAL cache
> -
>
> Key: IGNITE-9110
> URL: https://issues.apache.org/jira/browse/IGNITE-9110
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Ryabov Dmitrii
>Priority: Minor
>
> Commit hangs when tx contains operations on LOCAL and PARTITIONED or
> REPLICATED caches in some cases. Example:
> {code:java}
> public class LocalCacheFails extends GridCommonAbstractTest {
> /** */
> public void testLocalCache() throws Exception {
> IgniteEx ignite = startGrid(0);
> IgniteCache locCache =
> ignite.createCache(getConfig(LOCAL));
> IgniteCache partCache =
> ignite.createCache(getConfig(PARTITIONED));
> try (Transaction tx = ignite.transactions().txStart(OPTIMISTIC,
> SERIALIZABLE)) {
> locCache.put(1, 1);
> partCache.put(1, 1);
> tx.commit(); // Fails here.
> }
> }
> /** */
> private CacheConfiguration getConfig(CacheMode
> cacheMode) {
> CacheConfiguration cfg = new CacheConfiguration<>();
> cfg.setCacheMode(cacheMode);
> cfg.setName(cacheMode.name());
> cfg.setAtomicityMode(TRANSACTIONAL);
> return cfg;
> }
> }
> {code}
> Stacktrace here:
> {code:java}
> [18:05:44] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=ff3264cd461-707c41df-7a8c-4067-8367-5d941df0aec1, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false,
> colocatedLocallyMapped=true, needCheckBackup=null, hasRemoteLocks=false,
> trackTimeout=false, lb=null,
> thread=test-runner-#1%transactions.LocalCacheFails%,
> mappings=IgniteTxMappingsImpl [], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl
> [activeCacheIds=[72607563,-887906071], recovery=false, txMap=[IgniteTxEntry
> [key=KeyCacheObjectImpl [part=0, val=1, hasValBytes=true], cacheId=72607563,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=0, val=1, hasValBytes=true],
> cacheId=72607563], val=[op=CREATE, val=UserCacheObjectImpl [val=1,
> hasValBytes=true]], prevVal=[op=CREATE, val=UserCacheObjectImpl [val=1,
> hasValBytes=true]], oldVal=[op=NOOP, val=null], entryProcessorsCol=null,
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridLocalCacheEntry [super=GridCacheMapEntry [key=KeyCacheObjectImpl
> [part=0, val=1, hasValBytes=true], val=CacheObjectImpl [val=null,
> hasValBytes=true], ver=GridCacheVersion [topVer=144183944,
> order=1532703942007, nodeOrder=1], hash=1, extras=null, flags=2]],
> prepared=1, locked=false, nodeId=1068e98c-9c17-4fee-967b-8270,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=144183944,
> order=1532703942006, nodeOrder=1]], IgniteTxEntry [key=KeyCacheObjectImpl
> [part=1, val=1, hasValBytes=true], cacheId=-887906071, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> cacheId=-887906071], val=[op=CREATE, val=UserCacheObjectImpl [val=1,
> hasValBytes=true]], prevVal=[op=CREATE, val=UserCacheObjectImpl [val=1,
> hasValBytes=true]], oldVal=[op=NOOP, val=null], entryProcessorsCol=null,
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtCacheEntry [rdrs=[], part=1, super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], val=CacheObjectImpl [val=null, hasValBytes=true],
> ver=GridCacheVersion [topVer=144183944, order=1532703942007, nodeOrder=1],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc
> [locs=[GridCacheMvccCandidate [nodeId=1068e98c-9c17-4fee-967b-8270,
> ver=GridCacheVersion [topVer=144183944, order=1532703942006, nodeOrder=1],
> threadId=14, id=2, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=2],
> reentry=null, otherNodeId=1068e98c-9c17-4fee-967b-8270,
> otherVer=GridCacheVersion [topVer=144183944, order=1532703942006,
> nodeOrder=1], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=GridCacheVersion [topVer=144183944, order=1532703942006,
> nodeOrder=1], key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
>
[jira] [Updated] (IGNITE-17316) Thin client pluggable affnity mapping for the partition awareness usage
[
https://issues.apache.org/jira/browse/IGNITE-17316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17316:
-
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Thin client pluggable affnity mapping for the partition awareness usage
> ---
>
> Key: IGNITE-17316
> URL: https://issues.apache.org/jira/browse/IGNITE-17316
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.13
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> We should provie a pluggable affinity for the thin client, thus using the
> partition awareness features become possible on only for
> {{RendezvousAffinityFunction}}.
> Dev-list discussion:
> https://lists.apache.org/thread/7n7zbcgw59voxyr08ct3zx2ss5g8q9wh
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17316) Thin client pluggable affnity mapping for the partition awareness usage
[
https://issues.apache.org/jira/browse/IGNITE-17316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17316:
-
Summary: Thin client pluggable affnity mapping for the partition awareness
usage (was: Thin client pluggable affnity function to use partition awareness)
> Thin client pluggable affnity mapping for the partition awareness usage
> ---
>
> Key: IGNITE-17316
> URL: https://issues.apache.org/jira/browse/IGNITE-17316
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.13
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> We should provie a pluggable affinity for the thin client, thus using the
> partition awareness features become possible on only for
> {{RendezvousAffinityFunction}}.
> Dev-list discussion:
> https://lists.apache.org/thread/7n7zbcgw59voxyr08ct3zx2ss5g8q9wh
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (IGNITE-15759) [IEP-80] Removal of LOCAL caches support
[ https://issues.apache.org/jira/browse/IGNITE-15759 ]
Maxim Muzafarov deleted comment on IGNITE-15759:
--
was (Author: ignitetcbot):
{panel:title=Branch: [pull/10157/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10157/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 8{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6712991]]
* {color:#013220}IgniteCacheTestSuite8:
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsFifo - PASSED{color}
* {color:#013220}IgniteCacheTestSuite8:
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsSorted - PASSED{color}
* {color:#013220}IgniteCacheTestSuite8:
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsLru - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6713084buildTypeId=IgniteTests24Java8_RunAll]
> [IEP-80] Removal of LOCAL caches support
>
>
> Key: IGNITE-15759
> URL: https://issues.apache.org/jira/browse/IGNITE-15759
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: IEP-80
> Fix For: 2.14
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> LOCAL cachens has huge amount of known limitation and not intended to be used
> in production environment.
> Should be removed in 2.13
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (IGNITE-15759) [IEP-80] Removal of LOCAL caches support
[ https://issues.apache.org/jira/browse/IGNITE-15759 ]
Maxim Muzafarov deleted comment on IGNITE-15759:
--
was (Author: ignitetcbot):
{panel:title=Branch: [pull/10157/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10157/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 8{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6712991]]
* {color:#013220}IgniteCacheTestSuite8:
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsFifo - PASSED{color}
* {color:#013220}IgniteCacheTestSuite8:
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsSorted - PASSED{color}
* {color:#013220}IgniteCacheTestSuite8:
GridCacheConcurrentEvictionsSelfTest.testConcurrentPutsLru - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6713084buildTypeId=IgniteTests24Java8_RunAll]
> [IEP-80] Removal of LOCAL caches support
>
>
> Key: IGNITE-15759
> URL: https://issues.apache.org/jira/browse/IGNITE-15759
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: IEP-80
> Fix For: 2.14
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> LOCAL cachens has huge amount of known limitation and not intended to be used
> in production environment.
> Should be removed in 2.13
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17463) AssertionError: Logging at INFO level without checking if INFO level
Maxim Muzafarov created IGNITE-17463:
Summary: AssertionError: Logging at INFO level without checking if
INFO level
Key: IGNITE-17463
URL: https://issues.apache.org/jira/browse/IGNITE-17463
Project: Ignite
Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.14
The suite failed with the follwoing stacktrace.
{code}
[18:11:11]W: [org.apache.ignite:ignite-control-utility] Exception
in thread "shutdown-hook" java.lang.AssertionError: Logging at INFO level
without checking if INFO level is enabled: No verification for local node leave
has been received from coordinator (will stop node anyway).
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.testframework.junits.logger.GridTestLog4jLogger.info(GridTestLog4jLogger.java:522)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.testframework.ListeningTestLogger.info(ListeningTestLogger.java:157)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.internal.GridLoggerProxy.info(GridLoggerProxy.java:137)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStop0(ServerImpl.java:555)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStop(ServerImpl.java:492)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStop(TcpDiscoverySpi.java:2345)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:313)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1777)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1928)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1806)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2340)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2163)
[18:11:11]W: [org.apache.ignite:ignite-control-utility] at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$4.run(IgnitionEx.java:1806)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17463) AssertionError: Logging at INFO level without checking if INFO level
[
https://issues.apache.org/jira/browse/IGNITE-17463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17463:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> AssertionError: Logging at INFO level without checking if INFO level
>
>
> Key: IGNITE-17463
> URL: https://issues.apache.org/jira/browse/IGNITE-17463
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
>
> The suite failed with the follwoing stacktrace.
> {code}
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] Exception
> in thread "shutdown-hook" java.lang.AssertionError: Logging at INFO level
> without checking if INFO level is enabled: No verification for local node
> leave has been received from coordinator (will stop node anyway).
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.testframework.junits.logger.GridTestLog4jLogger.info(GridTestLog4jLogger.java:522)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.testframework.ListeningTestLogger.info(ListeningTestLogger.java:157)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.internal.GridLoggerProxy.info(GridLoggerProxy.java:137)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStop0(ServerImpl.java:555)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStop(ServerImpl.java:492)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStop(TcpDiscoverySpi.java:2345)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:313)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1777)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1928)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1806)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2340)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2163)
> [18:11:11]W: [org.apache.ignite:ignite-control-utility] at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$4.run(IgnitionEx.java:1806)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-11486) Support Automatic modules for ignite-zookeeper: Migrate to log4j2 to resolve issues with logging packages conflict
[
https://issues.apache.org/jira/browse/IGNITE-11486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574860#comment-17574860
]
Maxim Muzafarov commented on IGNITE-11486:
--
Log4j was removed IGNITE-16650
I think the issue can be viewed from a new angle from now on.
> Support Automatic modules for ignite-zookeeper: Migrate to log4j2 to resolve
> issues with logging packages conflict
> --
>
> Key: IGNITE-11486
> URL: https://issues.apache.org/jira/browse/IGNITE-11486
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitry Pavlov
>Priority: Minor
>
> Usage of Ignite Zookeeper module in a modular environment failed
> {noformat}
> error: the unnamed module reads package org.apache.log4j from both
> slf4j.log4j12 and log4j
> {noformat}
> slf4j version is updated by the build system when Ignite Zookeeper is used.
> {noformat}
> +--- org.slf4j:slf4j-api:1.7.7 -> 1.7.25
> +--- org.slf4j:slf4j-log4j12:1.7.7 -> 1.7.25
> +--- org.slf4j:slf4j-api:1.7.25
> \--- log4j:log4j:1.2.17
> {noformat}
> Probably we should update whole Ignite dependency for Slf4j
> Following combination seems to be compilable in a modular environment
> {code}
> compile (group: 'org.apache.ignite', name: 'ignite-zookeeper', version:
> ignVer) {
> exclude group: "org.slf4j", module: "slf4j-log4j12"
> exclude group: "log4j", module: "log4j"
> }
> compile group: "org.slf4j", name: "slf4j-api", version: "1.7.25"
> compile group: "org.apache.logging.log4j", name: "log4j-slf4j-impl",
> version: "2.11.2"
> {code}
> According to https://www.slf4j.org/news.html only 1.8x version is
> modularized, but this major versions line contains only betas. See also
> https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/
> See also https://blogs.apache.org/logging/entry/moving_on_to_log4j_2
> Migration quide https://logging.apache.org/log4j/2.x/manual/migration.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16787) Sql calcite. Bump calcite version up to 1.30
[ https://issues.apache.org/jira/browse/IGNITE-16787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-16787: - Fix Version/s: 2.14 > Sql calcite. Bump calcite version up to 1.30 > > > Key: IGNITE-16787 > URL: https://issues.apache.org/jira/browse/IGNITE-16787 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: calcite > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Seems it would helpful to bump calcite dependency up to > [1.30|https://calcite.apache.org/docs/history.html#v1-30-0] ver. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17427) Update netty version up to 4.1.79.Final
[ https://issues.apache.org/jira/browse/IGNITE-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572294#comment-17572294 ] Maxim Muzafarov commented on IGNITE-17427: -- Merged to the master branch. [~agidaspov] thank you for the contribution. > Update netty version up to 4.1.79.Final > --- > > Key: IGNITE-17427 > URL: https://issues.apache.org/jira/browse/IGNITE-17427 > Project: Ignite > Issue Type: Task >Reporter: Alexey Gidaspov >Assignee: Alexey Gidaspov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Need to update netty version up to 4.1.79.Final because of > [CVE-2022-24823|https://nvd.nist.gov/vuln/detail/CVE-2022-24823] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17427) Update netty version up to 4.1.79.Final
[ https://issues.apache.org/jira/browse/IGNITE-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov resolved IGNITE-17427. -- Resolution: Fixed > Update netty version up to 4.1.79.Final > --- > > Key: IGNITE-17427 > URL: https://issues.apache.org/jira/browse/IGNITE-17427 > Project: Ignite > Issue Type: Task >Reporter: Alexey Gidaspov >Assignee: Alexey Gidaspov >Priority: Minor > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to update netty version up to 4.1.79.Final because of > [CVE-2022-24823|https://nvd.nist.gov/vuln/detail/CVE-2022-24823] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17427) Update netty version up to 4.1.79.Final
[ https://issues.apache.org/jira/browse/IGNITE-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17427: - Fix Version/s: 2.14 > Update netty version up to 4.1.79.Final > --- > > Key: IGNITE-17427 > URL: https://issues.apache.org/jira/browse/IGNITE-17427 > Project: Ignite > Issue Type: Task >Reporter: Alexey Gidaspov >Assignee: Alexey Gidaspov >Priority: Minor > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Need to update netty version up to 4.1.79.Final because of > [CVE-2022-24823|https://nvd.nist.gov/vuln/detail/CVE-2022-24823] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17365) Move internal classes used by H2 to an appropriate package
[ https://issues.apache.org/jira/browse/IGNITE-17365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17365: - Issue Type: Improvement (was: Task) > Move internal classes used by H2 to an appropriate package > -- > > Key: IGNITE-17365 > URL: https://issues.apache.org/jira/browse/IGNITE-17365 > Project: Ignite > Issue Type: Improvement >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: ignite-osgi > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > We should avoid intersectipon of package definition between different > sub-modules in the Ignite Project. This is required to build OSGi bundle. > The follwoing classes must be moved: > - GridCacheTwoStepQuery > - QueryTable > - RegisteredQueryCursor > - SqlQueryMXBean > - SqlQueryMXBeanImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-6352) ignite-indexing is not compatible to OSGI
[ https://issues.apache.org/jira/browse/IGNITE-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-6352: Issue Type: Bug (was: Improvement) > ignite-indexing is not compatible to OSGI > - > > Key: IGNITE-6352 > URL: https://issues.apache.org/jira/browse/IGNITE-6352 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.1 >Reporter: Mikhail Cherkasov >Priority: Major > Labels: ignite-osgi > > the issue is reported by user, there's his message: > When trying to start Ignite in an OSGi context I get the following exception: > Caused by: java.lang.NoClassDefFoundError: org/h2/server/Service > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at > org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:153) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1832) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1648) > at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1076) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:506) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:482) > at org.apache.ignite.Ignition.start(Ignition.java:304) > That is because the h2 bundle (jar) is properly osgified, but does NOT > export the package org.h2.server, so it isn't visible to my code's classloader -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-6352) ignite-indexing is not compatible to OSGI
[ https://issues.apache.org/jira/browse/IGNITE-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-6352: Labels: ignite-osgi (was: ) > ignite-indexing is not compatible to OSGI > - > > Key: IGNITE-6352 > URL: https://issues.apache.org/jira/browse/IGNITE-6352 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.1 >Reporter: Mikhail Cherkasov >Priority: Major > Labels: ignite-osgi > > the issue is reported by user, there's his message: > When trying to start Ignite in an OSGi context I get the following exception: > Caused by: java.lang.NoClassDefFoundError: org/h2/server/Service > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at > org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:153) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1832) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1648) > at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1076) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:506) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:482) > at org.apache.ignite.Ignition.start(Ignition.java:304) > That is because the h2 bundle (jar) is properly osgified, but does NOT > export the package org.h2.server, so it isn't visible to my code's classloader -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-7670) Errors Installing Ignite OSGi Karaf features on JBoss fuse
[
https://issues.apache.org/jira/browse/IGNITE-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-7670:
Labels: ignite-osgi (was: )
> Errors Installing Ignite OSGi Karaf features on JBoss fuse
> --
>
> Key: IGNITE-7670
> URL: https://issues.apache.org/jira/browse/IGNITE-7670
> Project: Ignite
> Issue Type: Bug
> Components: osgi
>Affects Versions: 2.3
> Environment: jboss-fuse-6.2.1.redhat-159
>Reporter: Stefano Violi
>Priority: Critical
> Labels: ignite-osgi
>
> Installing Ignite's features repository on JBoss Fuse generates the following
> error:
> *Karaf shell command:*
> JBossFuse:karaf@root18007> features:addurl
> mvn:org.apache.ignite/ignite-osgi-karaf/2.3.0/xml/features
> *Error:*
> Error executing command: Unable to add repositories:
> Unrecognized root element:
> \{http://karaf.apache.org/xmlns/features/v1.3.0}features
>
> I also generated a new feature repository compliant with Fuse, adding the
> ignite-core and ignite-indexing features: in this way i installed them on
> JBoss Fuse.
> By the way, when i use these features from my component and I start Ignite
> with the following Java code
> Ignition.start();
> I get the following error:
> Caused by: java.lang.NoClassDefFoundError: org/h2/server/Service
> at java.lang.Class.forName0(Native Method)[:1.8.0_112]
> at java.lang.Class.forName(Class.java:264)[:1.8.0_112]
> at
> org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:153)
>
> I think there is some OSGi package import/export problem on Ignite features
> and boundles.
> Below the feature:
>
> feature name="ignite-core" version="2.3.0" description="Apache Ignite ::
> Core">
>
> dependency="true">mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-cache-api/1.0.0_1
> dependency="true">mvn:org.apache.ignite/ignite-osgi/2.5.0-SNAPSHOT
> start="true">mvn:org.apache.ignite/ignite-core/2.5.0-SNAPSHOT
>
>
>
>
>
>
> dependency="true">mvn:org.osgi/org.osgi.enterprise/5.0.0
> dependency="true">mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.lucene/5.5.2_1
> dependency="true">mvn:com.h2database/h2/1.4.195
> start="false">mvn:org.apache.ignite/ignite-indexing/2.3.0
>
>
> Thanks
> Kind regards
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-11668) OSGI: Self-imported package causes failure upon Karaf restart
[
https://issues.apache.org/jira/browse/IGNITE-11668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11668:
-
Labels: ignite-osgi (was: )
> OSGI: Self-imported package causes failure upon Karaf restart
> -
>
> Key: IGNITE-11668
> URL: https://issues.apache.org/jira/browse/IGNITE-11668
> Project: Ignite
> Issue Type: Bug
> Components: osgi
>Affects Versions: 2.7
> Environment: Ignite 2.7
> Apache Karaf 4.2.0
>Reporter: Oleksii Mohylin
>Assignee: Oleksii Mohylin
>Priority: Major
> Labels: ignite-osgi
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I've got problem using Ignite 2.7 in Apache Karaf 4.2.0. The problem is
> caused by strange bundle meta of ignite-osgi. It exports package
> org.apache.ignite.osgi.classloaders and imports it at the same time. Here's
> extract from METADATA.MF:
> {noformat}
> Import-Package: org.apache.ignite;version="[2.7,3)",org.apache.ignite.
> configuration;version="[2.7,3)",org.apache.ignite.internal.util;versi
> on="[2.7,3)",org.apache.ignite.internal.util.tostring;version="[2.7,3
> )",org.apache.ignite.internal.util.typedef.internal;version="[2.7,3)"
> ,org.apache.ignite.osgi.classloaders,org.osgi.framework;version="[1.7
> ,2)"
> Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
> Fragment-Host: org.apache.ignite.ignite-core
> Export-Package: org.apache.ignite.osgi.classloaders;uses:="org.apache.
> ignite.internal.util.tostring,org.osgi.framework";version="2.7.0",org
> .apache.ignite.osgi;uses:="org.apache.ignite,org.apache.ignite.config
> uration,org.apache.ignite.osgi.classloaders,org.osgi.framework";versi
> on="2.7.0"
> {noformat}
> There is no problem with initial installation of my application into Karaf,
> although after Karaf ignite-osgi dependency is not resolved, and this
> exception in log:
> {noformat}
> org.osgi.framework.BundleException: Unable to resolve graphql-core [399](R
> 399.0): missing requirement [graphql-core [399](R 399.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.ignite.osgi.classloaders)(version>=2.7.0)(!(version>=3.0.0)))
> [caused by: Unable to resolve org.apache.ignite.ignite-osgi [432](R 432.0):
> missing requirement [org.apache.ignite.ignite-osgi [432](R 432.0)]
> osgi.wiring.host;
> (&(osgi.wiring.host=org.apache.ignite.ignite-core)(bundle-version>=0.0.0))]
> Unresolved requirements: [[graphql-core [399](R 399.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.ignite.osgi.classloaders)(version>=2.7.0)(!(version>=3.0.0)))]
> {noformat}
> *Proposed solution:*
> remove the self-import by adding instruction to bundle plugin configuration
> in modules/osgi/pom.xml
> {code:java}
>
> org.apache.felix
> maven-bundle-plugin
>
>
> org.apache.ignite.ignite-core
>
> !org.apache.ignite.osgi.classloaders,*
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17365) Move internal classes used by H2 to an appropriate package
[ https://issues.apache.org/jira/browse/IGNITE-17365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566373#comment-17566373 ] Maxim Muzafarov commented on IGNITE-17365: -- Merged to the master branch. > Move internal classes used by H2 to an appropriate package > -- > > Key: IGNITE-17365 > URL: https://issues.apache.org/jira/browse/IGNITE-17365 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: ignite-osgi > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > We should avoid intersectipon of package definition between different > sub-modules in the Ignite Project. This is required to build OSGi bundle. > The follwoing classes must be moved: > - GridCacheTwoStepQuery > - QueryTable > - RegisteredQueryCursor > - SqlQueryMXBean > - SqlQueryMXBeanImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17365) Move internal classes used by H2 to an appropriate package
[ https://issues.apache.org/jira/browse/IGNITE-17365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17365: - Description: We should avoid intersectipon of package definition between different sub-modules in the Ignite Project. This is required to build OSGi bundle. The follwoing classes must be moved: - GridCacheTwoStepQuery - QueryTable - RegisteredQueryCursor - SqlQueryMXBean - SqlQueryMXBeanImpl was: The follwoing classes must be moved: - GridCacheTwoStepQuery - QueryTable - RegisteredQueryCursor - SqlQueryMXBean - SqlQueryMXBeanImpl > Move internal classes used by H2 to an appropriate package > -- > > Key: IGNITE-17365 > URL: https://issues.apache.org/jira/browse/IGNITE-17365 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: ignite-osgi > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > We should avoid intersectipon of package definition between different > sub-modules in the Ignite Project. This is required to build OSGi bundle. > The follwoing classes must be moved: > - GridCacheTwoStepQuery > - QueryTable > - RegisteredQueryCursor > - SqlQueryMXBean > - SqlQueryMXBeanImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17365) Move internal classes used by H2 to an appropriate package
[ https://issues.apache.org/jira/browse/IGNITE-17365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17365: - Summary: Move internal classes used by H2 to an appropriate package (was: Move H2 internal classes to an appropriate package) > Move internal classes used by H2 to an appropriate package > -- > > Key: IGNITE-17365 > URL: https://issues.apache.org/jira/browse/IGNITE-17365 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: ignite-osgi > Fix For: 2.14 > > > The follwoing classes must be moved: > - GridCacheTwoStepQuery > - QueryTable > - RegisteredQueryCursor > - SqlQueryMXBean > - SqlQueryMXBeanImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17365) Move H2 internal classes to an appropriate package
[ https://issues.apache.org/jira/browse/IGNITE-17365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17365: - Ignite Flags: (was: Docs Required,Release Notes Required) > Move H2 internal classes to an appropriate package > -- > > Key: IGNITE-17365 > URL: https://issues.apache.org/jira/browse/IGNITE-17365 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: ignite-osgi > Fix For: 2.14 > > > The follwoing classes must be moved: > - GridCacheTwoStepQuery > - QueryTable > - RegisteredQueryCursor > - SqlQueryMXBean > - SqlQueryMXBeanImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17365) Move H2 internal classes to an appropriate package
Maxim Muzafarov created IGNITE-17365: Summary: Move H2 internal classes to an appropriate package Key: IGNITE-17365 URL: https://issues.apache.org/jira/browse/IGNITE-17365 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.14 The follwoing classes must be moved: - GridCacheTwoStepQuery - QueryTable - RegisteredQueryCursor - SqlQueryMXBean - SqlQueryMXBeanImpl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17184) Ignite OSGi Karaf 2.13.0 doesn't exist in maven central
[ https://issues.apache.org/jira/browse/IGNITE-17184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17184: - Labels: ignite-osgi (was: ) > Ignite OSGi Karaf 2.13.0 doesn't exist in maven central > --- > > Key: IGNITE-17184 > URL: https://issues.apache.org/jira/browse/IGNITE-17184 > Project: Ignite > Issue Type: Bug > Components: osgi >Affects Versions: 2.13 >Reporter: Valeria Borodina >Priority: Major > Labels: ignite-osgi > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17216) Ignite modules in maven central aren't "bundle".
[ https://issues.apache.org/jira/browse/IGNITE-17216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17216: - Labels: ignite-osgi (was: ) > Ignite modules in maven central aren't "bundle". > > > Key: IGNITE-17216 > URL: https://issues.apache.org/jira/browse/IGNITE-17216 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.12, 2.13 >Reporter: Valeria Borodina >Priority: Major > Labels: ignite-osgi > > In osgi we use bundle not just jar. Ignite-osgi-karaf also installation how > bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16335) Ignite 2.12.0 jars are not OSGi compatible
[ https://issues.apache.org/jira/browse/IGNITE-16335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-16335: - Labels: ignite-osgi (was: ) > Ignite 2.12.0 jars are not OSGi compatible > -- > > Key: IGNITE-16335 > URL: https://issues.apache.org/jira/browse/IGNITE-16335 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.12 >Reporter: Richard Bryan >Priority: Blocker > Labels: ignite-osgi > > The ignite jars for 2.12.0 published to maven central are not > OSGi-compatible. For instance, this is the 2.12.0 MANIFEST for ignite-osgi: > Manifest-Version: 1.0 > Implementation-Title: ignite-osgi > Implementation-Version: 2.12.0 > Specification-Vendor: The Apache Software Foundation > Specification-Title: ignite-osgi > Build-Jdk-Spec: 1.8 > Created-By: Maven Jar Plugin 3.2.0 > Specification-Version: 2.12 > Implementation-Vendor: The Apache Software Foundation > > And this is the MANIFEST from 2.11.1: > > Manifest-Version: 1.0 > Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt > Bundle-SymbolicName: org.apache.ignite.ignite-osgi > Archiver-Version: Plexus Archiver > Built-By: teamcity > Bnd-LastModified: 1639998601403 > Specification-Title: ignite-osgi > Implementation-Vendor-Id: org.apache.ignite > Bundle-DocURL: http://ignite.apache.org > Import-Package: org.apache.ignite;version="[2.11,3)",org.apache.ignite > .configuration;version="[2.11,3)",org.apache.ignite.internal.util;ver > sion="[2.11,3)",org.apache.ignite.internal.util.tostring;version="[2. > 11,3)",org.apache.ignite.internal.util.typedef.internal;version="[2.1 > 1,3)",org.apache.ignite.osgi.classloaders,org.osgi.framework;version= > "[1.7,2)" > Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))" > Fragment-Host: org.apache.ignite.ignite-core > Export-Package: org.apache.ignite.osgi;uses:="org.apache.ignite,org.ap > ache.ignite.configuration,org.apache.ignite.osgi.classloaders,org.osg > i.framework";version="2.11.1",org.apache.ignite.osgi.classloaders;use > s:="org.apache.ignite.internal.util.tostring,org.osgi.framework";vers > ion="2.11.1" > Bundle-Name: ignite-osgi > Implementation-Title: ignite-osgi > Bundle-Description: Java-based middleware for in-memory processing of > big data in a distributed environment. > Implementation-Version: 2.11.1 > Embed-Directory: lib > Specification-Vendor: The Apache Software Foundation > Bundle-ManifestVersion: 2 > Bundle-Vendor: The Apache Software Foundation > Tool: Bnd-3.5.0.201709291849 > Implementation-Vendor: The Apache Software Foundation > Bundle-Version: 2.11.1 > Embed-Transitive: false > Created-By: Apache Maven Bundle Plugin > Build-Jdk: 1.8.0_261 > Specification-Version: 2.11.1 > > > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17364) Move control utility index tasks to the core module
[ https://issues.apache.org/jira/browse/IGNITE-17364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17364: - Labels: ignite-osgi (was: ) > Move control utility index tasks to the core module > --- > > Key: IGNITE-17364 > URL: https://issues.apache.org/jira/browse/IGNITE-17364 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: ignite-osgi > Time Spent: 20m > Remaining Estimate: 0h > > There are some control utility tasks (indexes list, index validate, index > rebuild), which are depended on H2 and located in indexing module. But > instead of H2 module classes core module classes having almost the same > functionality can be used. > We should rewrite these tasks to use core module classes to make tasks > workable without H2. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17046) Move H2RowComparator logic to the core module
[
https://issues.apache.org/jira/browse/IGNITE-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17046:
-
Labels: ignite-osgi (was: )
> Move H2RowComparator logic to the core module
> -
>
> Key: IGNITE-17046
> URL: https://issues.apache.org/jira/browse/IGNITE-17046
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: ignite-osgi
> Fix For: 2.14
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> {{H2RowComparator}} depends on H2 classes and can't be used without
> ignite-indexing module. We should move the logic from this comparator to the
> core module providing backward compatibility, to be able to use indexes
> without H2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13570: - Labels: ignite-osgi (was: ) > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task > Components: extensions >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > Labels: ignite-osgi > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15424:
-
Labels: calcite2-required ignite-osgi osgi (was: calcite2-required osgi)
> Calcite engine. Move schema management infrastructure to the core module
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite2-required, ignite-osgi, osgi
>
> Currently, schema management commands initiated in the {{ignite-core}}
> module, but all processing implemented in the {{ignite-indexing}} module.
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own
> structures.
> To get rid of {{ignite-indexing}} (and H2) dependency from the
> {{ignite-calcite}} module we should move schema management implementation to
> the core module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17190) Calcite engine. Unbind statistics from H2
[ https://issues.apache.org/jira/browse/IGNITE-17190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17190: - Labels: calcite calcite2-required ignite-osgi (was: calcite calcite2-required) > Calcite engine. Unbind statistics from H2 > - > > Key: IGNITE-17190 > URL: https://issues.apache.org/jira/browse/IGNITE-17190 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Ivan Daschinsky >Priority: Major > Labels: calcite, calcite2-required, ignite-osgi > > Currently, table statistics in Ignite uses some H2 classes (Value for > example). We should unbind statistics from H2 and move statistics to the core > module to be able to use it in calcite module without dependency to H2. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15424:
-
Labels: calcite2-required osgi (was: calcite2-required)
> Calcite engine. Move schema management infrastructure to the core module
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite2-required, osgi
>
> Currently, schema management commands initiated in the {{ignite-core}}
> module, but all processing implemented in the {{ignite-indexing}} module.
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own
> structures.
> To get rid of {{ignite-indexing}} (and H2) dependency from the
> {{ignite-calcite}} module we should move schema management implementation to
> the core module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564301#comment-17564301 ] Maxim Muzafarov commented on IGNITE-13570: -- Merged to the master branch. > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task > Components: extensions >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17342) Fix compatibility tests running a new client with the old server
[ https://issues.apache.org/jira/browse/IGNITE-17342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17342: - Labels: compatibility (was: ) > Fix compatibility tests running a new client with the old server > > > Key: IGNITE-17342 > URL: https://issues.apache.org/jira/browse/IGNITE-17342 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: compatibility > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Tests that are using JavaThinCompatibilityTest#testCurrentClientToOldServer > is not running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17342) Fix compatibility tests running a new client with the old server
[ https://issues.apache.org/jira/browse/IGNITE-17342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17342: - Ignite Flags: (was: Docs Required,Release Notes Required) > Fix compatibility tests running a new client with the old server > > > Key: IGNITE-17342 > URL: https://issues.apache.org/jira/browse/IGNITE-17342 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > > Tests that are using JavaThinCompatibilityTest#testCurrentClientToOldServer > is not running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17342) Fix compatibility tests running a new client with the old server
Maxim Muzafarov created IGNITE-17342: Summary: Fix compatibility tests running a new client with the old server Key: IGNITE-17342 URL: https://issues.apache.org/jira/browse/IGNITE-17342 Project: Ignite Issue Type: Bug Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.14 Tests that are using JavaThinCompatibilityTest#testCurrentClientToOldServer is not running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13570: - Component/s: extensions > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task > Components: extensions >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-13412) Publish nightly snapshot in apache repository
[ https://issues.apache.org/jira/browse/IGNITE-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov resolved IGNITE-13412. -- Resolution: Duplicate > Publish nightly snapshot in apache repository > -- > > Key: IGNITE-13412 > URL: https://issues.apache.org/jira/browse/IGNITE-13412 > Project: Ignite > Issue Type: Improvement > Components: streaming >Reporter: Saikat Maitra >Priority: Major > > > We used to publish nightly packages earlier in the apache snapshot repository > but we are no longer publishing the packages. > > [https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/] > > The last published package was > [2.2.2-SNAPSHOT/|https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/2.2.2-SNAPSHOT/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563612#comment-17563612 ] Maxim Muzafarov commented on IGNITE-13570: -- [~agoncharuk] I've assigned this issue to myselft. Please, let me know if you'd like to continue working on this issue. > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-13570: Assignee: Maxim Muzafarov (was: Alexey Goncharuk) > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17316) Thin client pluggable affnity function to use partition awareness
[
https://issues.apache.org/jira/browse/IGNITE-17316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17316:
-
Description:
We should provie a pluggable affinity for the thin client, thus using the
partition awareness features become possible on only for
{{RendezvousAffinityFunction}}.
Dev-list discussion:
https://lists.apache.org/thread/7n7zbcgw59voxyr08ct3zx2ss5g8q9wh
was:We should provie a pluggable affinity for the thin client, thus using the
partition awareness features become possible on only for
{{RendezvousAffinityFunction}}.
> Thin client pluggable affnity function to use partition awareness
> -
>
> Key: IGNITE-17316
> URL: https://issues.apache.org/jira/browse/IGNITE-17316
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
>
> We should provie a pluggable affinity for the thin client, thus using the
> partition awareness features become possible on only for
> {{RendezvousAffinityFunction}}.
> Dev-list discussion:
> https://lists.apache.org/thread/7n7zbcgw59voxyr08ct3zx2ss5g8q9wh
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17316) Thin client pluggable affnity function to use partition awareness
[
https://issues.apache.org/jira/browse/IGNITE-17316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17316:
-
Component/s: thin client
> Thin client pluggable affnity function to use partition awareness
> -
>
> Key: IGNITE-17316
> URL: https://issues.apache.org/jira/browse/IGNITE-17316
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
>
> We should provie a pluggable affinity for the thin client, thus using the
> partition awareness features become possible on only for
> {{RendezvousAffinityFunction}}.
> Dev-list discussion:
> https://lists.apache.org/thread/7n7zbcgw59voxyr08ct3zx2ss5g8q9wh
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17316) Thin client pluggable affnity function to use partition awareness
[
https://issues.apache.org/jira/browse/IGNITE-17316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17316:
-
Affects Version/s: 2.13
> Thin client pluggable affnity function to use partition awareness
> -
>
> Key: IGNITE-17316
> URL: https://issues.apache.org/jira/browse/IGNITE-17316
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.13
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
>
> We should provie a pluggable affinity for the thin client, thus using the
> partition awareness features become possible on only for
> {{RendezvousAffinityFunction}}.
> Dev-list discussion:
> https://lists.apache.org/thread/7n7zbcgw59voxyr08ct3zx2ss5g8q9wh
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-17316) Thin client pluggable affnity function to use partition awareness
Maxim Muzafarov created IGNITE-17316:
Summary: Thin client pluggable affnity function to use partition
awareness
Key: IGNITE-17316
URL: https://issues.apache.org/jira/browse/IGNITE-17316
Project: Ignite
Issue Type: Improvement
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.14
We should provie a pluggable affinity for the thin client, thus using the
partition awareness features become possible on only for
{{RendezvousAffinityFunction}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562270#comment-17562270 ] Maxim Muzafarov commented on IGNITE-13570: -- [~agoncharuk] Hello. Would you don't mind if I take care of this issue? > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13570) Migrate OSGI module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13570: - Fix Version/s: 2.14 > Migrate OSGI module to ignite-extensions > > > Key: IGNITE-13570 > URL: https://issues.apache.org/jira/browse/IGNITE-13570 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.14 > > > Migrate OSGI module to ignite-extensions > https://github.com/apache/ignite-extensions > Details: > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12355) [Umbrella] IEP-36 Modularization
[ https://issues.apache.org/jira/browse/IGNITE-12355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12355: - Ignite Flags: (was: Docs Required,Release Notes Required) > [Umbrella] IEP-36 Modularization > > > Key: IGNITE-12355 > URL: https://issues.apache.org/jira/browse/IGNITE-12355 > Project: Ignite > Issue Type: Improvement > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Labels: IEP-36 > > Migrate streaming modules in ignite-extensions repo > > [https://github.com/apache/ignite-extensions] > > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12355) [Umbrella] IEP-36 Modularization
[ https://issues.apache.org/jira/browse/IGNITE-12355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12355: - Summary: [Umbrella] IEP-36 Modularization (was: IEP-36: Modularization) > [Umbrella] IEP-36 Modularization > > > Key: IGNITE-12355 > URL: https://issues.apache.org/jira/browse/IGNITE-12355 > Project: Ignite > Issue Type: Improvement > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Labels: IEP-36 > > Migrate streaming modules in ignite-extensions repo > > [https://github.com/apache/ignite-extensions] > > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17019) [Umbrella] Move modules to the Ignite Extensions
[ https://issues.apache.org/jira/browse/IGNITE-17019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17019: - Labels: IEP-36 IEP-80 (was: IEP-80) > [Umbrella] Move modules to the Ignite Extensions > > > Key: IGNITE-17019 > URL: https://issues.apache.org/jira/browse/IGNITE-17019 > Project: Ignite > Issue Type: Task > Components: extensions >Reporter: Maxim Muzafarov >Priority: Major > Labels: IEP-36, IEP-80 > > This is an umbrella ticket of the activity moving Apache Modules to the > Ignite Extensions project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12854) Node failed under load when ATOMIC and TRANSACTIONAL caches created in the same cache group
[
https://issues.apache.org/jira/browse/IGNITE-12854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12854:
-
Labels: IEP-80 (was: )
> Node failed under load when ATOMIC and TRANSACTIONAL caches created in the
> same cache group
> ---
>
> Key: IGNITE-12854
> URL: https://issues.apache.org/jira/browse/IGNITE-12854
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: Aleksey Plekhanov
>Priority: Major
> Labels: IEP-80
>
> Node failed with assertion error under concurrent puts to ATOMIC and
> TRANSACTIONAL caches belonging to the same cache group:
> {noformat}
> java.lang.AssertionError: LWM after HWM: lwm=262, hwm=261
> at
> org.apache.ignite.internal.processors.cache.PartitionUpdateCounterTrackingImpl.reserve(PartitionUpdateCounterTrackingImpl.java:262)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.getAndIncrementUpdateCounter(IgniteCacheOffheapManagerImpl.java:1601)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.getAndIncrementUpdateCounter(GridCacheOffheapManager.java:2162)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.getAndIncrementUpdateCounter(GridDhtLocalPartition.java:1087)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.calculatePartitionUpdateCounters(IgniteTxLocalAdapter.java:520)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1343)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:709)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1104)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:411)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:577)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:374)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:183)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:161)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:205)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:203)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1847)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1472)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1367)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120){noformat}
> Reproducer:
>
> {code:java}
> public void testPartCounters() throws Exception {
> final AtomicBoolean end = new AtomicBoolean();
> final IgniteEx srv = startGrids(3);
> srv.cluster().active(true);
> IgniteInternalFuture loadFut = runMultiThreadedAsync(() -> {
> while (!end.get() && !fail) {
> List> caches = F.asList(
> srv.getOrCreateCache(new
> CacheConfiguration<>(CACHE_NAME_ATOMIC)
> .setAtomicityMode(CacheAtomicityMode.ATOMIC)
> .setGroupName(GROUP_NAME)
> ),
> srv.getOrCreateCache(new CacheConfiguration<>(CACHE_NAME_TX)
> .setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL)
> .setGroupName(GROUP_NAME)
> )
> );
>
