[jira] [Created] (IGNITE-5734) Web Console: update npm dependensies

[Alexey Kuznetsov (JIRA)]

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: Task
Reporter: Alexey Kuznetsov
Assignee: Andrey Novikov
 Fix For: 2.1


Before major release we can update npm dependencies.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5733) Activate/deactivate cluster through http-rest api

[Alexander Belyak (JIRA)]

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
  Issue Type: Improvement
Affects Versions: 2.0
Reporter: Alexander Belyak
Priority: Minor
 Fix For: 2.1


Need to add command to get/set cluster active flag into http rest api.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2283: IGNITE-5571

[alexpaschenko]

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 these changes as the patch at:

https://github.com/apache/ignite/pull/2283.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2283


commit 5aa613a4caa13250f4db19beb62f5c30e944be3b
Author: Alexander Paschenko 
Date:   2017-07-07T17:08:23Z

IGNITE-5571 Started refactoring.

commit df84a95b703146e0414246243e08b43a1ac9ea7f
Author: Alexander Paschenko 
Date:   2017-07-09T22:32:15Z

IGNITE-5571 Refactoring continued.

commit c5966dd33e12d9e1855c165854b965a8633b1869
Author: Andrey Novikov 
Date:   2017-07-11T10:02:56Z

IGNITE-5726 Web Console: Fixed duplication of dependencies in maven project.

commit bbf55dde32d42162206a616308dd8509af0b8479
Author: Alexander Paschenko 
Date:   2017-07-11T10:13:57Z

IGNITE-5571 Refactoring continued.

commit a9ae95342dd566b210fe835221214ecc67e6ed16
Author: Pavel Tupitsyn 
Date:   2017-07-11T11:13:14Z

 IGNITE-5446 Always use late affinity assignment mode - fix .NET tests

commit 1942db3af6538e6d1f0731b52eda94071f533ccb
Author: Pavel Tupitsyn 
Date:   2017-07-11T11:23:56Z

.NET: Fix code analysis warnings for deprecated IsLateAffinityAssignment

commit 1b2f5052ed34776d14d7614812b78e0aa66c69b1
Author: Ivan Rakov 
Date:   2017-07-11T11:19:14Z

Visor fails to connect to secure grid

commit e9f194a328b1704a7881f1bf1a148a3426cd1b53
Author: Alexey Kuznetsov 
Date:   2017-07-11T12:16:06Z

ignite-2.1 Improved web-console primitives.

commit 914fdc7b83ea5e73d2ee665fbb32bfdedc5e2dc7
Author: Alexey Kuznetsov 
Date:   2017-07-11T12:16:58Z

ignite-2.1 Web Console: improved demo.

commit 66ccf8594cc6de74c3d87620bc3c85cd86b571fa
Author: Alexey Kuznetsov 
Date:   2017-07-11T12:17:48Z

ignite-2.1 Minor update of generated classnames.

commit 2c737f0c6f42e983606e70faab5e9e6336b0a241
Author: Alexander Paschenko 
Date:   2017-07-11T12:23:26Z

IGNITE-5711: Allowed to run queries on caches without query entities. This 
closes #2264.

commit a0b56442365bad1100b078da33f00beb6a844cf0
Author: Sergey Chugunov 
Date:   2017-07-11T12:59:16Z

Minor fix - stopping nodes after test

commit 28ba989d7d864a8181cd9634a7d632a6cf38bb7e
Author: Alexander Paschenko 
Date:   2017-07-11T16:25:05Z

IGNITE-5571 Refactoring (almost) finished

commit 54f3b92872faa6447049190e119c0179b6439f30
Author: Alexander Paschenko 
Date:   2017-07-11T16:25:56Z

Merge remote-tracking branch 'origin/ignite-2.1.2' into ignite-5571




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2282: Ignite gg 12495

[glukos]

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 review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2282.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2282


commit c5966dd33e12d9e1855c165854b965a8633b1869
Author: Andrey Novikov 
Date:   2017-07-11T10:02:56Z

IGNITE-5726 Web Console: Fixed duplication of dependencies in maven project.

commit a9ae95342dd566b210fe835221214ecc67e6ed16
Author: Pavel Tupitsyn 
Date:   2017-07-11T11:13:14Z

 IGNITE-5446 Always use late affinity assignment mode - fix .NET tests

commit 1942db3af6538e6d1f0731b52eda94071f533ccb
Author: Pavel Tupitsyn 
Date:   2017-07-11T11:23:56Z

.NET: Fix code analysis warnings for deprecated IsLateAffinityAssignment

commit 1b2f5052ed34776d14d7614812b78e0aa66c69b1
Author: Ivan Rakov 
Date:   2017-07-11T11:19:14Z

Visor fails to connect to secure grid

commit e9f194a328b1704a7881f1bf1a148a3426cd1b53
Author: Alexey Kuznetsov 
Date:   2017-07-11T12:16:06Z

ignite-2.1 Improved web-console primitives.

commit 914fdc7b83ea5e73d2ee665fbb32bfdedc5e2dc7
Author: Alexey Kuznetsov 
Date:   2017-07-11T12:16:58Z

ignite-2.1 Web Console: improved demo.

commit 66ccf8594cc6de74c3d87620bc3c85cd86b571fa
Author: Alexey Kuznetsov 
Date:   2017-07-11T12:17:48Z

ignite-2.1 Minor update of generated classnames.

commit 2c737f0c6f42e983606e70faab5e9e6336b0a241
Author: Alexander Paschenko 
Date:   2017-07-11T12:23:26Z

IGNITE-5711: Allowed to run queries on caches without query entities. This 
closes #2264.

commit a0b56442365bad1100b078da33f00beb6a844cf0
Author: Sergey Chugunov 
Date:   2017-07-11T12:59:16Z

Minor fix - stopping nodes after test

commit c2efb935cacdc0b7c4614122a40d7ed6076e6d20
Author: Ivan Rakov 
Date:   2017-07-11T15:22:26Z

GG-12495: SaveStoreMetadata doesn't work for local cache. Got NPE.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5731) Wrong metrics calculation in ClusterMetricsSnapshot

[Evgenii Zhuravlev (JIRA)]

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
  Issue Type: Bug
Affects Versions: 1.6
Reporter: Evgenii Zhuravlev
Priority: Minor


 Error in ClusterMetricsSnapshot constructor:

 curWaitingJobs += m.getCurrentJobWaitTime();
 avgWaitingJobs += m.getCurrentWaitingJobs();



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2281: ignite-5722 Cache entries stay in onheap after sc...

[agura]

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 https://github.com/agura/incubator-ignite ignite-5722-master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2281.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2281


commit b5ecd3e00d34a465d0fedeaedf7813722e1680b3
Author: agura 
Date:   2017-07-11T13:24:54Z

ignite-5722 Cache entries stay in onheap after scan query execution for 
OFFHEAP_TIRED cache with expiry policy




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5730) .NET: Failed to load ignite.jni.dll when starting up multiple nodes

[Pavel Tupitsyn (JIRA)]

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: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.2


When starting multiple nodes at once (with a script of some kind), failure to 
load unmanaged dll can occur:

{code}
for (int i = 0; i < 30; i++)
{
Process.Start(@"cmd.exe", @"/k Apache.Ignite.exe");
}
{code}

Exception:
{code}
ERROR: System.TypeInitializationException: The type initializer for 
'Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils' threw an exception. ---> 
Apache.Ignite.Core.Common.IgniteException: Failed to load ignite.jni.dll: 126
   at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils..cctor()
   --- End of inner exception stack trace ---
   at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.Initialize()
   at Apache.Ignite.Core.Impl.IgniteUtils.LoadDlls(String configJvmDllPath, 
ILogger log)
   at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
   at Apache.Ignite.IgniteRunner.Main(String[] args)
{code}

Error codes may be 5 (ERROR_ACCESS_DENIED) or 126 (ERROR_MOD_NOT_FOUND).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2280: ignite-5722 Cache entries stay in onheap after sc...

[agura]

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 https://github.com/agura/incubator-ignite ignite-5722

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2280.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2280


commit 8add10e2ac9a91b0d7e473e6f40ff14d650abf96
Author: Pavel Tupitsyn 
Date:   2016-10-31T15:26:25Z

.NET: Fix ASP.NET session state provider test failures due to incorrect 
merge

commit e00d53173e7e217f4e94388fda34ebd813c4e7c3
Author: Pavel Tupitsyn 
Date:   2016-10-31T15:37:49Z

.NET: Fix license header

commit 260f9b2d01b16a98fcb7bc721573b95a72adade2
Author: Pavel Tupitsyn 
Date:   2016-10-31T15:37:49Z

.NET: Fix license header

commit e7d7a59eff6da1cd62e8ffb64405cdf12607b49d
Author: Pavel Tupitsyn 
Date:   2016-10-31T15:43:15Z

IGNITE-4153 .NET: IgniteConfiguration.FailureDetectionTimeout property is 
missing

commit d0f4b23600c655dfb94f6fe0205d1cca7cf19d36
Author: AKuznetsov 
Date:   2016-10-31T16:06:58Z

Fixed license.

commit 5fac786b6dbb179127ac725180acb54d0f6f4b0a
Author: devozerov 
Date:   2016-10-31T18:31:05Z

Merge branch 'ignite-1.6.10' into ignite-1.7.3

commit b8b9abe863ed8139553a9ad7013dfad5a363b4da
Author: devozerov 
Date:   2016-10-31T18:31:22Z

Fixes after merge.

commit 61ab650ecd353b4014a30f793090e9dab3519ad5
Author: devozerov 
Date:   2016-10-31T18:33:59Z

Fixes after merge.

commit 4495efc2aa37ca31214558968fa83598317e830a
Author: Pavel Tupitsyn 
Date:   2016-11-01T10:22:30Z

IGNITE-4117 .NET: Fix ClientReconnectTask completion timing

This closes #1195

commit dc0adf641f0ddac19af84ba0d701b33ee520b067
Author: Pavel Tupitsyn 
Date:   2016-08-16T15:11:34Z

IGNITE-3368 .NET: Improve test coverage

This closes #953

# Conflicts:
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/CacheAbstractTest.cs

commit cd0275d95dc6524464a154c74b1e62559b3d8af4
Author: Pavel Tupitsyn 
Date:   2016-08-19T14:34:00Z

IGNITE-3711 .NET: Fix PlatformRawMemory coverage issue

commit d7dee5248332c6c6276c9e21aed4afb3abdd4340
Author: Pavel Tupitsyn 
Date:   2016-07-29T12:40:42Z

IGNITE-3604 .NET: Fix inconsistent namespace imports in examples

Conflicts:
modules/platforms/dotnet/Apache.Ignite.sln.DotSettings

commit 390c8d59cf8d44d9703e5fbf8d9c0f8028a4a172
Author: Pavel Tupitsyn 
Date:   2016-08-11T13:18:14Z

IGNITE-3675 .NET: Use separate caches for different entities in 
QueryExample.

commit 861c1736facdf76c71e93ddada0d8e15b5b2950c
Author: Pavel Tupitsyn 
Date:   2016-08-11T14:32:13Z

IGNITE-3673 .NET: Add examples for distributed joins.

commit 3a9cbed4e692e76ad884e60a4f5edc670e6b3c8f
Author: Pavel Tupitsyn 
Date:   2016-08-08T14:00:04Z

IGNITE-3630 .NET: Add pure binary mode example with put-get and queries.

commit d5e15af76044cf65385672f8528d48ecdeca3cb6
Author: Pavel Tupitsyn 
Date:   2016-11-02T09:02:00Z

IGNITE-4121 .NET: add ScanQuery example

commit 74f8308d10fc011c00e52efcdb315b35cc79e60a
Author: Pavel Tupitsyn 
Date:   2016-11-02T12:59:15Z

IGNITE-4123 .NET: Remove [Serializable] from Employee in examples

commit 92fff630fbf36c82f93bbd9ddd53d11bed44e772
Author: devozerov 
Date:   2016-11-02T14:50:51Z

Restored services compatibility.

commit a62a0136d295486d95c6e2ab5bba88270d831753
Author: dkarachentsev 
Date:   2016-11-02T16:07:45Z

GG-11655 - Fix merge

commit 348593986b56ddfcec4a4455e49d9b279eae4dc8
Author: devozerov 
Date:   2016-11-05T10:28:03Z

Merge branch 'ignite-1.7.3' into ignite-1.7.4

commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d
Author: tledkov-gridgain 
Date:   2016-11-07T06:16:58Z

IGNITE-3432:  check data/meta cache names are different for different IGFS 
instances. This closes #1201

commit ead15193899d08f41491166003cabed0560f0c59
Author: Pavel Tupitsyn 
Date:   2016-11-07T07:49:03Z

IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget

This closes #1192

commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd
Author: Dmitriy Govorukhin 
Date:   2016-11-07T09:09:41Z

ignite-4178 support permission 

[GitHub] ignite pull request #2279: Merge remote-tracking branch 'upstream/master' in...

[BiryukovVA]

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 timeout during the grid 
stop.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/BiryukovVA/ignite IGNITE-5452

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2279.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2279


commit b2be98aff13d239dc0999491ebde52bd450a0bd0
Author: Vitaliy Biryukov 
Date:   2017-07-11T13:06:10Z

IGNITE-5452:
1) Handled eaten InterruptedException in TimeoutObject.
2) Test correctness of rollback a transaction with timeout during the grid 
stop.

commit e663bb37d86dfb4e6a57ba95629d2635e4cb92cc
Author: Vitaliy Biryukov 
Date:   2017-07-11T13:09:00Z

Merge remote-tracking branch 'upstream/master' into IGNITE-5452




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Patch for IGNITE-5597 is ready.

[Elen Code]

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

[jira] [Created] (IGNITE-5729) IgniteCacheProxy instances from "with..." methods are not reusable

[Pavel Kovalenko (JIRA)]

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: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.1
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko
 Fix For: 2.1


On cache restart all IgniteCacheProxy instances must be reset in order to reuse 
them.
But bunch of methods in IgniteCache interface including withKeepBinary create 
new instances of proxy for each call and these instances are not reset on cache 
restart. 
E.g. it leads to CacheStoppedException when reusing them after restoring from 
snapshot.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2277: Ignite-gg-12449 Failed to start node with persist...

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2240: ignite-5694 : Retries for getCollection().

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2273: IGNITE-5538 Double check for PersistenceStore mes...

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2227: IGNITE-5159 DDL example.

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2115: IGNITE-5204: Fixed NPE on certain data with index...

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2248: IGNITE-5483: SQL: Added limited support for Java8...

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2107: IGNITE-5437: Handling query argument type for que...

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5727) Node failed listener for TcpCommunicationSpi should be called first

[Semen Boikov (JIRA)]

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
  Issue Type: Bug
  Components: general
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 2.1


Ignite components rely on assumption that if node failed then it is not 
possible to send message to this node (TcpCommunicationSpi.send should throw an 
exception). If it was possible to send event and node then components' 
node_left listener will be called. But actually this will work only if 
component's node_left listener is called after TcpCommunicationSpi's listener. 
Need change node_left listener's order so that  TcpCommunicationSpi's listener 
is always called first.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Enabling memory and persistence metrics

[Sergey Chugunov]

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 better approach is to have a general message-based mechanism which
would allow user to send a command to the grid to turn on and off
collecting any metrics.
Although it requires more discussion, design and implementation efforts I
believe it is the only reasonable option in long-term.

Thanks,
Sergey.

On Tue, Jul 11, 2017 at 3:24 AM, Denis Magda  wrote:

> Hi Pavel, thanks.
>
> However, how do I enable the metrics for the default memory region
> (policy)? I’m talking about the use case when there are no custom memory
> regions/policies defined.
>
> Is it supposed that the user need to recreate the default policy
> configuration from sratch just in order to enable the metrics? Can we add
> “MemoryConfiguration.setMetricsEnabled” method that will enable metrics
> for all the regions we have?
>
> —
> Denis
>
> > On Jul 10, 2017, at 1:44 AM, Pavel Tupitsyn 
> wrote:
> >
> > Hi Denis,
> >
> > See PersistentStoreConfiguration.metricsEnabled,
> MemoryPolicyConfiguration.
> > metricsEnabled
> >
> > On Sat, Jul 8, 2017 at 2:55 AM, Denis Magda  wrote:
> >
> >> Sergey,
> >>
> >> How do I enable MemoryMetrics and PersistenceMetrics metrics aggregation
> >> if a have only the default region set and don’t wanna use the JMX beans
> >> available?
> >>
> >> Struggling to find any API method to do that. Hope we didn’t forget to
> >> support such an obvious thing.
> >>
> >> —
> >> Denis
>
>