Re: Right MXBean for new metrics

2017-11-24 Thread Dmitriy Setrakyan
Got it, but I do not like the name of the metric, I think it is confusing. I would provide the following metrics: - minNumberOfCopies() - maxNumberOfCopies() Will this work for you? D. On Thu, Nov 23, 2017 at 10:38 PM, Alex Plehanov wrote: > We have target redundancy

[GitHub] ignite pull request #3093: Ignite 2.4.1 mm page memory npe fix

2017-11-24 Thread sergey-chugunov-1985
GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3093 Ignite 2.4.1 mm page memory npe fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2813: IGNITE-6272: .NET: Propagate multiple services de...

2017-11-24 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2813 ---

[jira] [Created] (IGNITE-7017) Reconsider WAL archive strategy

2017-11-24 Thread Alexey Goncharuk (JIRA)
Alexey Goncharuk created IGNITE-7017: Summary: Reconsider WAL archive strategy Key: IGNITE-7017 URL: https://issues.apache.org/jira/browse/IGNITE-7017 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7016) Avoid fsync on WAL rollover in non-default mode

2017-11-24 Thread Alexey Goncharuk (JIRA)
Alexey Goncharuk created IGNITE-7016: Summary: Avoid fsync on WAL rollover in non-default mode Key: IGNITE-7016 URL: https://issues.apache.org/jira/browse/IGNITE-7016 Project: Ignite

[GitHub] ignite pull request #3092: ignite-gg-13017

2017-11-24 Thread AMashenkov
GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3092 ignite-gg-13017 fixed test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13017 Alternatively you can

Re: Losing data during restarting cluster with persistence enabled

2017-11-24 Thread Dmitry Pavlov
Please see the discussion on the user list. It seems that the same happened there: http://apache-ignite-users.70518.x6.nabble.com/Reassign-partitions-td7461.html#a7468 it contains examples when the data can diverge. пт, 24 нояб. 2017 г. в 16:42, Dmitry Pavlov : > If we

[jira] [Created] (IGNITE-7015) SQL: index should be updated only when relevant values changed

2017-11-24 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-7015: --- Summary: SQL: index should be updated only when relevant values changed Key: IGNITE-7015 URL: https://issues.apache.org/jira/browse/IGNITE-7015 Project: Ignite

[jira] [Created] (IGNITE-7014) SQL: in-place update should be allowed when indexing is enabled

2017-11-24 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-7014: --- Summary: SQL: in-place update should be allowed when indexing is enabled Key: IGNITE-7014 URL: https://issues.apache.org/jira/browse/IGNITE-7014 Project:

Re: Losing data during restarting cluster with persistence enabled

2017-11-24 Thread Dmitry Pavlov
If we compare native and 3rd party persistence (cache store): - Updating and reading data from DBMS is slower in most scenarios. - Non-clustered DBMS is a single point of failure, it is hard to scale. - Ignite SQL does not extend to External (3rd party persitsence) Cache Store (and queries

Re: Integration of Spark and Ignite. Prototype.

2017-11-24 Thread Николай Ижиков
Hello, Val, Denis. > Personally, I think that we should release the integration only after the strategy is fully supported. I see two major reason to propose merge of DataFrame API implementation without custom strategy: 1. My PR is relatively huge, already. From my experience of interaction

[GitHub] ignite pull request #3091: IGNITE-7013 .NET: Fix startup on macOS (dlopen ca...

2017-11-24 Thread ptupitsyn
GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3091 IGNITE-7013 .NET: Fix startup on macOS (dlopen call) You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-7013

[GitHub] ignite pull request #3090: IGNITE-6929

2017-11-24 Thread alexpaschenko
GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/3090 IGNITE-6929 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6929 Alternatively you can review and apply

[jira] [Created] (IGNITE-7013) .NET: Ignite does not start on macOS

2017-11-24 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-7013: -- Summary: .NET: Ignite does not start on macOS Key: IGNITE-7013 URL: https://issues.apache.org/jira/browse/IGNITE-7013 Project: Ignite Issue Type: Bug

TC issues. IGNITE-3084. Spark Data Frame API

2017-11-24 Thread Николай Ижиков
Hello, guys. I have some issues on TC with my PR [1] for IGNITE-3084(Spark Data Frame API). Can you, please, help me: 1. `Ignite RDD spark 2_10` - Currently this build runs with following profiles: `-Plgpl,examples,scala-2.10,-clean-libs,-release` [2] That means `scala` profile is activated

[GitHub] ignite pull request #3089: Ignite-2.4.1-merge-master

2017-11-24 Thread DmitriyGovorukhin
GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/3089 Ignite-2.4.1-merge-master You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-merge-master

[jira] [Created] (IGNITE-7012) Web console: investigate E2E tests

2017-11-24 Thread Ilya Borisov (JIRA)
Ilya Borisov created IGNITE-7012: Summary: Web console: investigate E2E tests Key: IGNITE-7012 URL: https://issues.apache.org/jira/browse/IGNITE-7012 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7011) Web console: add more tests

2017-11-24 Thread Ilya Borisov (JIRA)
Ilya Borisov created IGNITE-7011: Summary: Web console: add more tests Key: IGNITE-7011 URL: https://issues.apache.org/jira/browse/IGNITE-7011 Project: Ignite Issue Type: Improvement

Re: Losing data during restarting cluster with persistence enabled

2017-11-24 Thread Evgeniy Ignatiev
Sorry linked the wrong page, the latter url is not the example. On 11/24/2017 1:12 PM, Evgeniy Ignatiev wrote: By the way I remembered that there is an annotation CacheLocalStore for marking exactly the CacheStore that is not distributed -

Re: Losing data during restarting cluster with persistence enabled

2017-11-24 Thread Evgeniy Ignatiev
By the way I remembered that there is an annotation CacheLocalStore for marking exactly the CacheStore that is not distributed - http://apache-ignite-developers.2346864.n4.nabble.com/CacheLocalStore-td734.html - here is short explanation and this -

[GitHub] ignite pull request #3088: IGNITE-6853: Cassandra cache store does not clean...

2017-11-24 Thread jasonman107
GitHub user jasonman107 opened a pull request: https://github.com/apache/ignite/pull/3088 IGNITE-6853: Cassandra cache store does not clean prepared statements… IGNITE-6853: Cassandra cache store does not clean prepared statements cache when remove old cassandra session You can

Re: Data Rebalancing status API

2017-11-24 Thread Alexey Popov
Hm, actually, I've missed existent MXBean: RebalancingPartitionsCount. Probably it should be enough. Thanks, Alexey -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events

2017-11-24 Thread Krzysztof Chmielewski (JIRA)
Krzysztof Chmielewski created IGNITE-7010: - Summary: Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events Key: IGNITE-7010 URL: https://issues.apache.org/jira/browse/IGNITE-7010

Re: Confusing slf4j error messages

2017-11-24 Thread Alexey Popov
I've opened a ticket https://issues.apache.org/jira/browse/IGNITE-6828 some time ago to fix this message. If nobody argues I will prepare a patch. Thanks, Alexey -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Data Rebalancing status API

2017-11-24 Thread Alexey Popov
Hi Igniters, I saw several cases when Ignite users/admins need to ensure if Data Rebalancing is NOT in progress to prevent possible data loss. For instance, when nodes one-by-one are moved out of the cluster for maintenance and returned back by some script. Currently, this information could be

[GitHub] ignite pull request #3075: no BaselineTopology for in-memory-only grid

2017-11-24 Thread sergey-chugunov-1985
Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/3075 ---