[jira] [Created] (IGNITE-14289) Calcite flaky test testNotOriginatorNodeStop.
Stanilovsky Evgeny created IGNITE-14289: --- Summary: Calcite flaky test testNotOriginatorNodeStop. Key: IGNITE-14289 URL: https://issues.apache.org/jira/browse/IGNITE-14289 Project: Ignite Issue Type: Bug Components: sql Environment: !image-2021-03-09-10-10-19-314.png! test is flaky for now. Reporter: Stanilovsky Evgeny Attachments: image-2021-03-09-10-10-19-314.png -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14288) Ability to define the JVM settings by globals for server and client (app) nodes separately
Dmitriy Sorokin created IGNITE-14288: Summary: Ability to define the JVM settings by globals for server and client (app) nodes separately Key: IGNITE-14288 URL: https://issues.apache.org/jira/browse/IGNITE-14288 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Sorokin Assignee: Dmitriy Sorokin Sometimes it becomes necessary to define the JVM options only for server nodes or only for application nodes globally, so new global parameters, _node_jvm_opts_ and _app_jvm_opts_ should be added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[MTCGA]: new failures in builds [5905952] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master Cache (Restarts) 1 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 22:10:21 08-03-2021
[CANCEL] [VOTE] Release Apache Ignite 2.10.0 RC1
Folks, The vote cancelled. The following issues need to be addressed: https://issues.apache.org/jira/browse/IGNITE-14284 https://issues.apache.org/jira/browse/IGNITE-14285
[jira] [Created] (IGNITE-14287) Ignite Accessibility Check: Broken links
Mauricio Stekl created IGNITE-14287: --- Summary: Ignite Accessibility Check: Broken links Key: IGNITE-14287 URL: https://issues.apache.org/jira/browse/IGNITE-14287 Project: Ignite Issue Type: Bug Components: website Reporter: Mauricio Stekl Assignee: Mauricio Stekl Attachments: Broken links (Outbound).xlsx While doing Ignite's usability audit, We have figured out that there's a small bunch of broken links on the website, leading to 404 pages. The attached report indicates the origin of these. -- This message was sent by Atlassian Jira (v8.3.4#803005)
IGNITE-2399 : Asynchronous Acquire method in IgniteSemaphore
Hi All, I would like to start a discussion around IGNITE-2399. Background: The typical use of IgniteSemaphore consists of acquiring the semaphore, performing the task and releasing the semaphore. This JIRA proposes a new method which will accept a callable, acquire the semaphore, and return a future. Upon completion of the future, the semaphore is released. This API seems useful for an easy encapsulation of the described use case and does not cause an internal flux since all the changes are focused at the public API. WIP PR for the same: https://github.com/apache/ignite/pull/8820 Please share your thoughts and comments. -- Regards, Atri Apache Concerted
