Re: Sort nodes in the ring in order to minimize the number of reconnections

Actually, after giving it some thought, I now think that the same kind of flexibility can be achieved by giving multiple nodes the same CLUSTER_REGION_ID (don't like the arc id). For example, nodes in 2 racks could be given CLUSTER_REGION_ID of 1 and 2. This way all nodes in rack 1 or rack 2 would

About RoundRobinLoadBalancingSpi

Hi， In RoundRobinLoadBalancingSpi，according to the description of the document,per-task mode is the default configuration and should fit most of the use cases as it provides a fairly well-distributed split and also ensures that jobs within a single task are spread out across nodes to the

Re: Rework Sql Queries use case to SQL Grid one

Agree, looks good. On Tue, Dec 27, 2016 at 3:36 PM, Denis Magda wrote: > Dmitriy, I like the picture we already have [1]. > > I would rename “Ignite Cluster” to “SQL Grid”, remove “Client” text and > change the look and feel. This picture is really a good candidate to be a >

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

Denis, I think we can remove all configs except: benchmark-multicast.properties benchmark.properties ignite-base-config.xml ignite-localhost-config.xml ignite-multicast-config.xml 2016-12-28 2:49 GMT+03:00 Denis Magda : > I would have only those configs that are useful.

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

I would have only those configs that are useful. Ilya Suntsov, basing on your experience, please suggest which configs makes sense to include into every Ignite release. Oleg, also please note that community decided to include not only the benchmarking binaries but the sources as well into

Re: Rework Sql Queries use case to SQL Grid one

Dmitriy, I like the picture we already have [1]. I would rename “Ignite Cluster” to “SQL Grid”, remove “Client” text and change the look and feel. This picture is really a good candidate to be a kind of SQL Grid billboard on the site. The rest is deeply covered in the documentation. Any

Re: IGNITE-4487 - NPE on query execution

Alexander, I need to know your JIRA ID in order to add you to the contributors list. As for your questions, this situation might be caused by the race when a cache is being stopped and there are still scan queries running in parallel. So, in general it’s not about data loss. Sam, Alex G.,

Re: Diagram for RDBMS Schema Import with Web Console

Done. The doc gets released https://apacheignite-mix.readme.io/docs/web-console — Denis > On Dec 21, 2016, at 2:28 PM, Denis Magda wrote: > > Thanks guys, I’ve sent an updated version to the designer. > > — > Denis >

Re: Hello

Hi Vadim, I added you to the contributors list in JIRA. Please go ahead and assign the ticket on yourself. Here is the other useful information. Subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process

Re: Sort nodes in the ring in order to minimize the number of reconnections

On Tue, Dec 27, 2016 at 2:32 AM, Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > 2016-12-27 10:42 GMT+03:00 Yakov Zhdanov : > > I think the NodeComparator approach will work. User can chose how to sort > > nodes from one rack before nodes from another rack. Same

Re: Sort nodes in the ring in order to minimize the number of reconnections

Yes, i can. But someone needs to give me the rights of contributor in Jira. 2016-12-27 17:07 GMT+03:00 Vyacheslav Daradur : > I have described a task: https://issues.apache.org/jira/browse/IGNITE-4501 > > and linked a bug https://issues.apache.org/jira/browse/IGNITE-4499 > >

Re: Hello

Hello, Vadim, Welcome :) On 27 December 2016 at 16:12, Вадим Опольский wrote: > Dear sirs! > > I'm Vadim Opolskij, Jira user name is javaller. I want to contribute an > ignite project, ticket number is IGNITE-3537. > > Vadim Opolskij >

Hello

Dear sirs! I'm Vadim Opolskij, Jira user name is javaller. I want to contribute an ignite project, ticket number is IGNITE-3537. Vadim Opolskij

Re: Sort nodes in the ring in order to minimize the number of reconnections

I have described a task: https://issues.apache.org/jira/browse/IGNITE-4501 and linked a bug https://issues.apache.org/jira/browse/IGNITE-4499 Alex Menshikov, maybe you will take her? 2016-12-27 13:32 GMT+03:00 Alexei Scherbakov : > 2016-12-27 10:42 GMT+03:00

[jira] [Created] (IGNITE-4501) Improvement of connection in a cluster of new node

Vyacheslav Daradur created IGNITE-4501: -- Summary: Improvement of connection in a cluster of new node Key: IGNITE-4501 URL: https://issues.apache.org/jira/browse/IGNITE-4501 Project: Ignite

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

I mean removing those configs from binary assembly, not from repository. On Tue, Dec 27, 2016 at 4:28 PM, Oleg Ostanin wrote: > Hello Igniters. > I think it would be better to remove some configuration files from > benchmarks/config: > > ignite-base-load-config.xml >

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

Hello Igniters. I think it would be better to remove some configuration files from benchmarks/config: ignite-base-load-config.xml ignite-cache-load-config.xml ignite-failover-base-config.xml ignite-failover-localhost-config.xml benchmark-cache-load.properties benchmark-cache-load-win.properties

[GitHub] ignite pull request #1390: IGNITE-4458 Hadoop: striped shuffle mode must be ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1390 IGNITE-4458 Hadoop: striped shuffle mode must be enabled by default You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-4500) .NET: Support identity resolver for binary enums

Pavel Tupitsyn created IGNITE-4500: -- Summary: .NET: Support identity resolver for binary enums Key: IGNITE-4500 URL: https://issues.apache.org/jira/browse/IGNITE-4500 Project: Ignite Issue

Re: IGNITE-4374 - Ignite should validate JVM and OS configuration and output warning in log

I mean ConfigurationValidator as another class, not GridPerformanceSuggestion. And invoke it from IgniteKernal. 2016-12-27 14:46 GMT+03:00 Vyacheslav Daradur : > >> > 3. I think this should be a new section in performance suggestion output. > And I think the

Re: IGNITE-4374 - Ignite should validate JVM and OS configuration and output warning in log

>> 3. I think this should be a new section in performance suggestion output. And I think the GridPerformanceSuggestions should be used, but it should be probably renamed to reflect its new role and remove Grid prefix also. How about ConfigurationSuggestions? >> How about: public class

Re: IGNITE-4374 - Ignite should validate JVM and OS configuration and output warning in log

Vyacheslav, my comments are below. >> 1. It is necessary to check a flag MaxDirectMemorySize, but there is no recommendation of it: https://apacheignite.readme.io/docs/jvm-and-system-tuning 2. Whether it is necessary to output message in "Quiet mode"? 3. Where it is better to output information

[GitHub] ignite pull request #1389: IGNITE-4428 Hadoop: move HadoopMapReducePlanner a...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1389 IGNITE-4428 Hadoop: move HadoopMapReducePlanner and dependent classes to public space. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-4499) TcpDiscoverySpi is not reliable in some network split scenarios.

Alexei Scherbakov created IGNITE-4499: - Summary: TcpDiscoverySpi is not reliable in some network split scenarios. Key: IGNITE-4499 URL: https://issues.apache.org/jira/browse/IGNITE-4499 Project:

[GitHub] ignite pull request #1388: IGNITE-4487: Fixed

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/1388 IGNITE-4487: Fixed Fix NPE in inner class 'GridCacheQueryAdapter.ScanQueryFallbackClosableIterator' in constructor. Method ScanQueryFallbackClosableIterator#init() cannot be called with an empty

Re: Sort nodes in the ring in order to minimize the number of reconnections

2016-12-27 10:42 GMT+03:00 Yakov Zhdanov : > >> > My main concern here is code complexity. Yakov, how difficult it is to > stick a new node in an arbitrary spot of a discovery ring? > >> > > Dmitry, I think this is not hard. At least I don't see any issue now. > > >> > I

[GitHub] ignite pull request #1371: IGNITE-2793 Added support for byte arrays to ODBC

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1371 --- 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-4498) .NET: Remove legacy BinaryObject.Equals

Pavel Tupitsyn created IGNITE-4498: -- Summary: .NET: Remove legacy BinaryObject.Equals Key: IGNITE-4498 URL: https://issues.apache.org/jira/browse/IGNITE-4498 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4497) CacheDefaultBinaryAffinityKeyMapper class has a wrong duplicate

Vasiliy Sisko created IGNITE-4497: - Summary: CacheDefaultBinaryAffinityKeyMapper class has a wrong duplicate Key: IGNITE-4497 URL: https://issues.apache.org/jira/browse/IGNITE-4497 Project: Ignite