Alexey Kuznetsov created IGNITE-5734:
Summary: Web Console: update npm dependensies
Key: IGNITE-5734
URL: https://issues.apache.org/jira/browse/IGNITE-5734
Project: Ignite
Issue Type:
Alexander Belyak created IGNITE-5733:
Summary: Activate/deactivate cluster through http-rest api
Key: IGNITE-5733
URL: https://issues.apache.org/jira/browse/IGNITE-5733
Project: Ignite
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2283
IGNITE-5571
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5571
Alternatively you can review and apply
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/2282
Ignite gg 12495
PR for tests run
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12495
Alternatively you can
Evgenii Zhuravlev created IGNITE-5731:
-
Summary: Wrong metrics calculation in ClusterMetricsSnapshot
Key: IGNITE-5731
URL: https://issues.apache.org/jira/browse/IGNITE-5731
Project: Ignite
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/2281
ignite-5722 Cache entries stay in onheap after scan query execution for
OFFHEAP_TIRED cache with expiry policy
You can merge this pull request into a Git repository by running:
$ git pull
Pavel Tupitsyn created IGNITE-5730:
--
Summary: .NET: Failed to load ignite.jni.dll when starting up
multiple nodes
Key: IGNITE-5730
URL: https://issues.apache.org/jira/browse/IGNITE-5730
Project:
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/2280
ignite-5722 Cache entries stay in onheap after scan query execution for
OFFHEAP_TIRED cache with expiry policy
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/2279
Merge remote-tracking branch 'upstream/master' into IGNITE-5452
IGNITE-5452:
1) Handled eaten InterruptedException in TimeoutObject.
2) Test correctness of rollback a transaction with
Hi Ignite team,
I'm finished with https://issues.apache.org/jira/browse/IGNITE-5597. It is
small ticket about changing JavaDocs.Please review pull-request:
https://github.com/apache/ignite/pull/2268
Regards,Andrei
Pavel Kovalenko created IGNITE-5729:
---
Summary: IgniteCacheProxy instances from "with..." methods are not
reusable
Key: IGNITE-5729
URL: https://issues.apache.org/jira/browse/IGNITE-5729
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2277
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2240
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2273
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2227
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2115
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2248
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2107
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Semen Boikov created IGNITE-5727:
Summary: Node failed listener for TcpCommunicationSpi should be
called first
Key: IGNITE-5727
URL: https://issues.apache.org/jira/browse/IGNITE-5727
Project: Ignite
Denis,
Indeed for default MemoryPolicy user has to create a MemoryPolicy
explicitly.
But I strongly dislike the idea of adding new global setting to
MemoryConfiguration section. This section is already overloaded with a lot
of non-obvious stuff; and adding one more will make it even worse.
The
20 matches
Mail list logo
