Re: Add ability to enable and disable rebalancing per-node

Sasha, The idea behind the ticket was as follows: currently, the rebalanceDelay property is set in CacheConfiguration, which is not very flexible. In certain circumstances, a user might expect particularly large load on some segments of the cluster and want to disable rebalancing for those (existi

[jira] [Created] (IGNITE-5207) .NET: Non-Int32 enums can't be serialized

Pavel Tupitsyn created IGNITE-5207: -- Summary: .NET: Non-Int32 enums can't be serialized Key: IGNITE-5207 URL: https://issues.apache.org/jira/browse/IGNITE-5207 Project: Ignite Issue Type: Bu

Re: 10X decrease in performance with Ignite 2.0.0

According to our benchmarks Ignite 2.0 is not slower for get operation. I think we need some minimal reproducer that shows the performance degradation before making any conclusions. Sergi 2017-05-12 1:10 GMT+03:00 Yakov Zhdanov : > Cross-posting to devlist. > > --Yakov >

[jira] [Created] (IGNITE-5208) C++ Segfault on Put

Tolga HOŞGÖR created IGNITE-5208: Summary: C++ Segfault on Put Key: IGNITE-5208 URL: https://issues.apache.org/jira/browse/IGNITE-5208 Project: Ignite Issue Type: Bug Components: ca

Re: 10X decrease in performance with Ignite 2.0.0

Absolutely agree here. I think if we can add getAll() benchmark and run it with batch sizes of 5 and 10. Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2017-05-12 10:48 GMT+03:00 Sergi Vladykin : > According to our benchmarks Ignite 2.0 is not slower for get operation

[GitHub] ignite pull request #1933: IGNITE-5207 .NET: Support non-Int32 enums

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1933 IGNITE-5207 .NET: Support non-Int32 enums You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-5207 Alternatively you can

[jira] [Created] (IGNITE-5209) "IllegalStateException: Already swapped" error with offheap_tired indexed cache

Ksenia Rybakova created IGNITE-5209: --- Summary: "IllegalStateException: Already swapped" error with offheap_tired indexed cache Key: IGNITE-5209 URL: https://issues.apache.org/jira/browse/IGNITE-5209

[GitHub] ignite pull request #1933: IGNITE-5207 .NET: Support non-Int32 enums

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1933 --- 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 ena

[jira] [Created] (IGNITE-5210) If enabled security authentication, server is unable to restart if client tries to reconnect

Dmitry Karachentsev created IGNITE-5210: --- Summary: If enabled security authentication, server is unable to restart if client tries to reconnect Key: IGNITE-5210 URL: https://issues.apache.org/jira/browse/IGN

[GitHub] ignite pull request #1934: Ignite 5112

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/1934 Ignite 5112 OLS regression example and tests refactoring. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5112 Alt

[GitHub] ignite pull request #1896: for test purposes.

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1896 --- 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] ignite pull request #471: Ignite 2396 - Service deployment for dynamic cache...

Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/471 --- 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] ignite pull request #42: Ignite 264

Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/42 --- 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 e

[GitHub] ignite pull request #348: IGNITE-2194 - Fixed cache proxy deserialization.

Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/348 --- 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] ignite pull request #332: Ignite 2100

Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/332 --- 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] ignite pull request #343: IGNITE-2178 - Fixed primary key set for scan query...

Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/343 --- 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

[jira] [Created] (IGNITE-5211) Classes based constructor for QueryEntities

Denis Magda created IGNITE-5211: --- Summary: Classes based constructor for QueryEntities Key: IGNITE-5211 URL: https://issues.apache.org/jira/browse/IGNITE-5211 Project: Ignite Issue Type: Task

Re: SQL: setting key field name for types registered via CacheConfiguration.setIndexedTypes

Here is a ticket: https://issues.apache.org/jira/browse/IGNITE-5211 Vovan, can it be done in 2.1? — Denis > On May 11, 2017, at 4:14 PM, Denis Magda wrote: > > Guys, > > Let’s suppose there is a cache that stores entries like that: > > * key - int > * value - custom object which fields are a

Re: 10X decrease in performance with Ignite 2.0.0

Chris, After looking at your code, the only slow down that may have occurred between 1.9 and 2.0 is the actual cache "get(...)" operation. As you may already know, Ignite 2.0 has moved data off-heap completely, so we do not cache data in the deserialized form any more, by default. However, you can

[jira] [Created] (IGNITE-5212) Allow custom affinity for system caches

Alexei Scherbakov created IGNITE-5212: - Summary: Allow custom affinity for system caches Key: IGNITE-5212 URL: https://issues.apache.org/jira/browse/IGNITE-5212 Project: Ignite Issue Type

[GitHub] ignite pull request #1935: IGNITE-4324 Check node list is non-empty before q...

GitHub user WilliamDo opened a pull request: https://github.com/apache/ignite/pull/1935 IGNITE-4324 Check node list is non-empty before query execution You can merge this pull request into a Git repository by running: $ git pull https://github.com/WilliamDo/ignite IGNITE-4324

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

Folks, The repository with the donation is ready and available for review: https://github.com/agoncharuk/ignite/tree/pds-donate Big and main part of the sources is aggregated in “modules/pds”. The rest, that connects Apache Ignite memory architecture and SQL engine is under “core” and “indexing

Apache Ignite weekly update

We have 4 new blog posts (starting from May 5) this past week. https://ignite.apache.org/blogs.html Next week's action will be in Miami at ApacheCon North America. Denis Magda will have a couple of talk there on May 18: * Apache Ignite SQL Grid: Hot Blend of Traditional SQL and Swift Data Grid an

Re: Apache Ignite weekly update

Tom, Thanks for keeping us posted! — Denis > On May 12, 2017, at 2:36 PM, Tom Diederich wrote: > > We have 4 new blog posts (starting from May 5) this past week. > https://ignite.apache.org/blogs.html > > Next week's action will be in Miami at ApacheCon North America. Denis Magda > will have