Re: Data regions on client nodes

Actually, I would go even further: only allocate a data region on a node when the first cache assigned to this region is deployed on that node. Because issue is broader than client nodes and local caches. One can have server nodes without any caches as well - running only services, for example.

Re: Data regions on client nodes

Val, thanks for pointing this out. I would actually not allocate any off-heap memory on the client side unless we see Local caches in the configuration. This is such a rare case, that we can ignore it altogether. D. On Fri, Jul 20, 2018 at 3:59 PM, Valentin Kulichenko <

Re: Apache Ignite 2.7: scope, time and release manager

Hi Denis, Nikolay, The proposed 2.7 release timing sounds reasonable to me. Python [1], PHP [2], and Node.js [3] thin clients should take the train. p. [1] https://jira.apache.org/jira/browse/IGNITE-7782 [2] https://jira.apache.org/jira/browse/IGNITE-7783 [3]

Apache Ignite 2.7: scope, time and release manager

Igniters, Let's agree on the time and the scope of 2.7. As for the release manager, we had a conversation with Nikolay Izhikov and he decided to try the role out. Thanks, Nikolay! Nikolay, we need to prepare a page like that [1] once the release terms are defined. I propose us to roll Ignite

Data regions on client nodes

Folks, Currently do not create any regions or allocate any offheap memory on client nodes unless it's explicitly configured. This is good behavior, however there is a usability issue caused by the fact that many users have the same config file for both server and clients. This can lead to

[jira] [Created] (IGNITE-9046) Actualize dependency versions for Cassandra Cache Store

Dmitriy Pavlov created IGNITE-9046: -- Summary: Actualize dependency versions for Cassandra Cache Store Key: IGNITE-9046 URL: https://issues.apache.org/jira/browse/IGNITE-9046 Project: Ignite

Re: Spark DataFrame Partition Ordering Issue

Hello, Stuart. I will investigate this issue and return to you in a couple days. пт, 20 июля 2018 г., 17:59 Stuart Macdonald : > Ignite Dev Community, > > I’m working with the Ignite 2.4+ Spark SQL DataFrame functionality and > have run into what I believe to be a bug where spark partition

[jira] [Created] (IGNITE-9045) TxRecord is logged to WAL during node stop procedure

Sergey Chugunov created IGNITE-9045: --- Summary: TxRecord is logged to WAL during node stop procedure Key: IGNITE-9045 URL: https://issues.apache.org/jira/browse/IGNITE-9045 Project: Ignite

Re: Code duplicates in ssh tests

Ok, I agree here, that we can remove one test. Feel free to create an issue and PR if nobody else mind. Let us wait at least until Mon 23 Jul before merge. пт, 20 июл. 2018 г. в 17:57, Иван Федотов : > Hi, Dmitry. > > I thought about elements order, but if we go deeper in >

[GitHub] ignite pull request #4390: IGNITE-9039 AssertionError on cache stop

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4390 ---

Spark DataFrame Partition Ordering Issue

Ignite Dev Community, I’m working with the Ignite 2.4+ Spark SQL DataFrame functionality and have run into what I believe to be a bug where spark partition information is incorrect for non-trivial sizes of Ignite clusters. The partition array returned to Spark via

Re: Code duplicates in ssh tests

Hi, Dmitry. I thought about elements order, but if we go deeper in ignite.cluster().stopNodes() method, we can see that in ClusterIgniteImpl [1] all nodes id will be collected in HashSet in forNodesIds method [2]. So I think that in this case it's not important what use initially, HashSet or

[GitHub] ignite pull request #4395: IGNITE-9040 new FailureHandler for node segmentat...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4395 IGNITE-9040 new FailureHandler for node segmentation special case, test for the root cause error You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #4394: test

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/4394 test You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite IGNITE-999 Alternatively you can review and apply these changes as the patch

[jira] [Created] (IGNITE-9044) Update scala dependency version in Apache Ignite

Dmitriy Pavlov created IGNITE-9044: -- Summary: Update scala dependency version in Apache Ignite Key: IGNITE-9044 URL: https://issues.apache.org/jira/browse/IGNITE-9044 Project: Ignite Issue

Re: Code duplicates in ssh tests

Hi Ivan, I can suppose that it is related to elements order. Is it reasonable to keep 2 tests with 1 common mehod? One test will call this method with HashSet, and other with ArrayList. Sincerely, Dmitriy Pavlov пт, 20 июл. 2018 г. в 15:01, Иван Федотов : > Hi, Igniters! > > I’m working on ssh

[jira] [Created] (IGNITE-9043) Map field is registered as Object in BinaryType

Denis Mekhanikov created IGNITE-9043: Summary: Map field is registered as Object in BinaryType Key: IGNITE-9043 URL: https://issues.apache.org/jira/browse/IGNITE-9043 Project: Ignite

[GitHub] ignite pull request #4393: IGNITE-8866 Retries to upload class

GitHub user ezagumennov opened a pull request: https://github.com/apache/ignite/pull/4393 IGNITE-8866 Retries to upload class You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8866 Alternatively you

[GitHub] ignite pull request #4392: IGNITE-9041 AssertionError in TcpCommunicationSpi

GitHub user SpiderRus opened a pull request: https://github.com/apache/ignite/pull/4392 IGNITE-9041 AssertionError in TcpCommunicationSpi You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9041

[jira] [Created] (IGNITE-9042) Transaction with small timeout may lead to inconsistent partition state

Dmitriy Govorukhin created IGNITE-9042: -- Summary: Transaction with small timeout may lead to inconsistent partition state Key: IGNITE-9042 URL: https://issues.apache.org/jira/browse/IGNITE-9042

[jira] [Created] (IGNITE-9041) AssertionError in TcpCommunicationSpi

Alexey Stelmak created IGNITE-9041: -- Summary: AssertionError in TcpCommunicationSpi Key: IGNITE-9041 URL: https://issues.apache.org/jira/browse/IGNITE-9041 Project: Ignite Issue Type: Bug

Re: Desynchronization of true repo and github repo

Yes, very strange thing, I've also checked this commit in mirror before, and it is appeared only now. I have no clue about reasons. пт, 20 июл. 2018 г. в 15:02, Nikolay Izhikov : > When I'm try to push 8633d34e to master, GitHub repo doesn't contain Yury > commit. > > It appear on GitHub only

Re: Desynchronization of true repo and github repo

When I'm try to push 8633d34e to master, GitHub repo doesn't contain Yury commit. It appear on GitHub only after my merge and push. пт, 20 июля 2018 г., 14:53 Dmitry Pavlov : > Hi Yury, > > it seems commit has appeared now: > >

Code duplicates in ssh tests

Hi, Igniters! I’m working on ssh module and found some code duplicates in IgniteProjectionStartStopRestartSelfTest. 1. Tests testRestartNodesByIds and testRestartNodesByIdsC are fully duplicate themself [1]. I tried to found what differences should they have and looked at similar tests:

Re: Desynchronization of true repo and github repo

Hi Yury, it seems commit has appeared now: https://github.com/apache/ignite/commit/26e405281792d38b5505cde22b5c6a91749c4990 Sincerely, Dmitriy Pavlov пт, 20 июл. 2018 г. в 14:02, Yury Babak : > Igniters, > > Few hours ago I pushed the commit > < >

[GitHub] ignite pull request #4378: IGNITE-8915: NPE on local sql query for client no...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4378 ---

[GitHub] ignite pull request #4385: IGNITE-9021: Refactor vectors/matrix classes

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4385 ---

[GitHub] ignite pull request #4391: IGNITE-8892 add additional test.

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/4391 IGNITE-8892 add additional test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8892-zstan Alternatively you can

Desynchronization of true repo and github repo

Igniters, Few hours ago I pushed the commit into https://git-wip-us.apache.org/repos/asf/ignite But I dont see this commit in github repo, may be we have some problem with

[jira] [Created] (IGNITE-9040) StopNodeFailureHandler is not able to stop node correctly on node segmentation

Sergey Chugunov created IGNITE-9040: --- Summary: StopNodeFailureHandler is not able to stop node correctly on node segmentation Key: IGNITE-9040 URL: https://issues.apache.org/jira/browse/IGNITE-9040

Re: [ML] Machine Learning Pipeline Improvement

Alexey, I like this idea, this should improve usability of our ML module. Regards, Yury -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #4390: IGNITE-9039 AssertionError on cache stop

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/4390 IGNITE-9039 AssertionError on cache stop You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9039 Alternatively

[GitHub] ignite pull request #4389: Ignite 9038

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/4389 Ignite 9038 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9038 Alternatively you can review and apply

Re: GridCacheReplicatedFullApiMultithreadedSelfTest1 not used, not compile. Remove?

Hi Maxim, I think we should remove such code. And if nobody objects I can apply PR on Monday. Ilya, please confirm you're agree. Sincerely, Dmitriy Pavlov пт, 20 июл. 2018 г. в 13:16, Maxim Muzafarov : > Ignites, > > I've faced with test in Ignite code base that is fully commented. You can >

[jira] [Created] (IGNITE-9039) AssertionError on cache stop

Eduard Shangareev created IGNITE-9039: - Summary: AssertionError on cache stop Key: IGNITE-9039 URL: https://issues.apache.org/jira/browse/IGNITE-9039 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-9038) Node join serialization defaults

Dmitry Karachentsev created IGNITE-9038: --- Summary: Node join serialization defaults Key: IGNITE-9038 URL: https://issues.apache.org/jira/browse/IGNITE-9038 Project: Ignite Issue Type:

Re: data extractor

Alexey, 1. The utility will extract raw payload bytes. If you want to build binary object or Java class instances you will need binary/marshaller metadata. If two grid will have different metadata, you should move metadata as well as dumped data for construct binary objects on another grid. Do

GridCacheReplicatedFullApiMultithreadedSelfTest1 not used, not compile. Remove?

Ignites, I've faced with test in Ignite code base that is fully commented. You can check it by yoursefl [1]. As it not used since 2014 and not even compile I'm suggesting to remove it. What do you think about it? Please, share your thoughts. Full name:

Re: [ML] Machine Learning Pipeline Improvement

Yes, it make the prerocessing easy and clear for reading and understanding. In API it will looks like Model mdl = Pipeline.of(reading, featureExctracting, labelExtracting, normalizing, encoding, scaling, logisticRegression) where in .of(...) we can see the sequence of ML stages.

Fwd: The Apache Ignite Book

Hi Igniters, We somethimes mention lack of overall view and documentaion about Ignite, and I guess it could be changed soon. FYI, please find forwarded message below, and I hope you will have a free minute to review. At least I can see free book sample available and I find deep technical

[jira] [Created] (IGNITE-9037) Apache Pulsar intergration

Roman Shtykh created IGNITE-9037: Summary: Apache Pulsar intergration Key: IGNITE-9037 URL: https://issues.apache.org/jira/browse/IGNITE-9037 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #4388: test for Ignite 5980

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/4388 test for Ignite 5980 You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite IGNITE-5980 Alternatively you can review and apply these

[GitHub] ignite pull request #4375: tests for ignite 5980

Github user 1vanan closed the pull request at: https://github.com/apache/ignite/pull/4375 ---

[GitHub] ignite pull request #2957: IGNITE-5798

Github user 1vanan closed the pull request at: https://github.com/apache/ignite/pull/2957 ---

Re: Place Ignite TC helper to ASF Ignite supplementary git repo

Dmitry, At the last Moscow Apache Ignite Meetup a very high threshold of entry into Ignite code development was discussed. So, for me placing MTCGA.Bot to ASF sounds reasonable and I'm voiting for this case. It would be a good start point for each new community member. But I'm with all hands for