[GitHub] ignite pull request #3244: IGNITE-7182: throttle only changes

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3244 IGNITE-7182: throttle only changes Part of implementation changes throttling policy You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/ap

[jira] [Created] (IGNITE-7217) Add abilities to monitor custom thread pools

Valentin Kulichenko created IGNITE-7217: --- Summary: Add abilities to monitor custom thread pools Key: IGNITE-7217 URL: https://issues.apache.org/jira/browse/IGNITE-7217 Project: Ignite I

Re: Switching Java language level to 8

Hi Denis Filed the ticket [1] 1. IGNITE-7216 Refactor examples project On Fri, Dec 15, 2017 at 8:45 PM, Denis Magda wrote: > Yuri, Sergey, > > These are all good points! Please create sub-tasks fro this umbrella > tickets (one for ML and the

[jira] [Created] (IGNITE-7216) Refactor examples project

Sergey Kozlov created IGNITE-7216: - Summary: Refactor examples project Key: IGNITE-7216 URL: https://issues.apache.org/jira/browse/IGNITE-7216 Project: Ignite Issue Type: Sub-task

Re: Thin Client Protocol documentation

Hi Andrey, I’m afraid there are no plans for this features yet (at least I didn’t spot any relevant discussion on @dev). Feel free to start a separate discussion proposing the protocol expansion. It’s better not to intermix this with the documentation thread. — Denis > On Dec 15, 2017, at 11:

Re: Thin Client Protocol documentation

Pavel, could you please at least share your time frame wrt adding compute, clustering and services features to the spec? Thanks Andrey From: Pavel Tupitsyn Sent: Tuesday, December 5, 2017 11:15 PM To: dev@ignite.apache.org Subject: Re: Thin Client Protocol docume

Re: [ARTICLE] In-Memory Technologies: Meeting Healthcare's Fast Data Challenges. Part I

Excellent article! Look forward to the second part where to learn more about a real-world use case powered by Ignite. — Denis > On Dec 15, 2017, at 9:13 AM, Akmal Chaudhri > wrote: > > Part 1 of a 2-part series is now live: > > https://www.gridgain.com/resources/blog/in-memory-technologies-m

Re: Switching Java language level to 8

Yuri, Sergey, These are all good points! Please create sub-tasks fro this umbrella tickets (one for ML and the other for examples): https://issues.apache.org/jira/browse/IGNITE-7203 Don’t want this to be missed in the discussion. — Denis > O

[GitHub] ignite pull request #3242: IGNITE-7213: Empty class descriptions for KNNMode...

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

[GitHub] ignite pull request #3243: Ignite 7182: buckets (experimental)

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3243 Ignite 7182: buckets (experimental) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7182-buckets Alternatively

[GitHub] ignite pull request #3242: IGNITE-7213: Empty class descriptions for KNNMode...

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/3242 IGNITE-7213: Empty class descriptions for KNNModelFormat fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-721

[ARTICLE] In-Memory Technologies: Meeting Healthcare's Fast Data Challenges. Part I

Part 1 of a 2-part series is now live: https://www.gridgain.com/resources/blog/in-memory-technologies-meeting-healthcares-fast-data-challenges-part-i Thank you.

[jira] [Created] (IGNITE-7215) Documentation bug: "Cross-cache Query" page is dead

Alexey Kukushkin created IGNITE-7215: Summary: Documentation bug: "Cross-cache Query" page is dead Key: IGNITE-7215 URL: https://issues.apache.org/jira/browse/IGNITE-7215 Project: Ignite

[jira] [Created] (IGNITE-7214) performance measurement for FCM and KNN algorithms

Oleg Ignatenko created IGNITE-7214: -- Summary: performance measurement for FCM and KNN algorithms Key: IGNITE-7214 URL: https://issues.apache.org/jira/browse/IGNITE-7214 Project: Ignite Issue

[jira] [Created] (IGNITE-7213) Empty class descriptions for KNNModelFormat

Yury Babak created IGNITE-7213: -- Summary: Empty class descriptions for KNNModelFormat Key: IGNITE-7213 URL: https://issues.apache.org/jira/browse/IGNITE-7213 Project: Ignite Issue Type: Bug

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

This may be related to the recent changes in TC infrastructure. I see the following in remote nodes output: nohup: ignoring input /data/teamcity/work/820be461cd64b574/bin/ignite.sh, ERROR: The version of JAVA installed in JAVA_HOME= is incorrect. Please point JAVA_HOME variable to installation of

[GitHub] ignite pull request #3241: IGNITE-7097 performance measurement for SparseDis...

GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/3241 IGNITE-7097 performance measurement for SparseDistributedMatrix multi… …plication - optimised and unoptimised benchmarks, along with respective documentation - also a common adju

IGNITE-7203 Java 8 by default

Hi, all. Finished IGNITE-7203 [1] and prepared PR [2] Test TeamCity run can be watched here [3] [1] https://issues.apache.org/jira/browse/IGNITE-7203 [2] https://github.com/apache/ignite/pull/3240

Re: Rework locking architecture for MVCC and transactional SQL

That would be great, actually, We have a lot of data structures which size heavily depends on the topology size and caches number, and all those data structures are placed on-heap. I am looking forward moving that stuff to a limited memory region with disk offload. The DataRegion and disk offload

[GitHub] ignite pull request #3240: IGNITE-7203 Java 8 by default

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/3240 IGNITE-7203 Java 8 by default You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7203 Alternatively you can review

Re: Switching Java language level to 8

Hi The examples project should be refactored. Now we have regular and Java8 examples and I suppose to replace regular examples by corresponding Java8 examples if any. On Fri, Dec 15, 2017 at 3:14 PM, vveider wrote: > Very good. I came to the same thoughts. > > Yet, there is a situation that s

Re: Rework locking architecture for MVCC and transactional SQL

Well, there is completely different approach to handle the problem - lock escalation. E.g. SQL Server typically require 96 bytes per lock. Much less than Ignite, but still. And as soon as some query require more than 5000 row locks, it is escalated to exclusive table lock. Not only this eliminates

[GitHub] ignite pull request #3239: ignite-2.4.1-p6

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3239 ignite-2.4.1-p6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p6 Alternatively you can review and app

Re: Rework locking architecture for MVCC and transactional SQL

Alex, That might be very good idea. In fact, what you describe closely resembles TempDB in MS SQL Server [1]. It is also offloaded to disk, minimally logged and purged on restart. Ideally we could try designing this component in generic way, so that it could store a lot different temporal stuff: 1

Re: Rework locking architecture for MVCC and transactional SQL

Vladimir, What about moving the entire locking mechanism to a separate off-heap memory region which will be volatile wrt restarts, but will still support off-load to disk. In the current architecture, it means that we will need to allocate a separate DataRegion with no WAL and no crash recovery -

Re: MVCC version format

Hi Alex, Good points. 1) So far we've seen clusters up to ~ 2K nodes in size, and typical size is much smaller. So this doesn't appear to be a a big problem in common case. But what if at some point we see, say, 10_000 nodes deployment? in this case proposed schema may virtually stop working at a

[GitHub] ignite pull request #3238: Gg 13213

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/3238 Gg 13213 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gg-13213 Alternatively you can review and apply these ch

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

According to Failure Conditions [1] — it is designed to fail after 30 min. So the question is - should we consider 30 min run time to be project’s error (and fix the code) or TeamCity error (and fix the build configuration by, for example, increasing build failure timeout)? [1] https://ci.igni

[GitHub] ignite pull request #3237: ignite-7195: limit toString of arrays and additio...

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/3237 ignite-7195: limit toString of arrays and additional values; add "and… ignite-7195: limit toString of arrays and additional values; add "and N more". You can merge this pull request into a Git r

Re: Switching Java language level to 8

Very good. I came to the same thoughts. Yet, there is a situation that some classes in *.java.* and .*java8.* packages that share the name and policy of merging them is not quite clear. Should *.java.* classes be replace by .*java8.*? -- Sent from: http://apache-ignite-developers.2346864.n4.nab

Re: Switching Java language level to 8

Hi, currently we use maven profile "ml" for all ML sources. So during this switching we could remove this profile and add ML module to the normal build chain. NB: we use this hack in example and yardstick modules. Also in examples we have the separate source folder(and profile) for non-ml java 8

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

Hi Igniters, Who can became Jedi of TeamCity and substitute me in this research? Sincerely, Dmitry Pavlov пт, 15 дек. 2017 г. в 12:38, Anton Vinogradov : > Dmitry, > > Could you please investigate? > > On Fri, Dec 15, 2017 at 9:16 AM, Andrey Kuznetsov > wrote: > > > Hi Anton, > > > > I doubt i

[jira] [Created] (IGNITE-7212) Load stoped after server node kill

Ilya Suntsov created IGNITE-7212: Summary: Load stoped after server node kill Key: IGNITE-7212 URL: https://issues.apache.org/jira/browse/IGNITE-7212 Project: Ignite Issue Type: Bug

Re: MVCC version format

Vladimir, Although at the first glance this seems to be ok for a local solution, I have a few concerns wrt distributed version behavior: 1) I cannot say that epoch switch in this approach will be an extremely rare event. Let's say a user regularly deploys a new version of application code to a la

[GitHub] ignite pull request #3236: IGNITE-5136: GridLogThrottle memory leak

GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/3236 IGNITE-5136: GridLogThrottle memory leak You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite ignite-5136 Alternatively you can re

MVCC version format

Igniters, As you probably know, we are working on MVCC feature [1]. When MVCC is enabled every cache operation/tx require one unique version for read and possibly one version for write. Versions are assigned by a single node called *coordinator*. Requirements for version: 1) Must be increasing an

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

Dmitry, Could you please investigate? On Fri, Dec 15, 2017 at 9:16 AM, Andrey Kuznetsov wrote: > Hi Anton, > > I doubt it was merge conflict. Couple of days ago 'Ignite Start Nodes' > suite succeeded 1 time after unrelated changes, and now it is failing > again. > > 2017-12-12 16:25 GMT+03:00 A

[jira] [Created] (IGNITE-7211) Web console: Wrong cluster active state on cluster switch.

Vasiliy Sisko created IGNITE-7211: - Summary: Web console: Wrong cluster active state on cluster switch. Key: IGNITE-7211 URL: https://issues.apache.org/jira/browse/IGNITE-7211 Project: Ignite

[jira] [Created] (IGNITE-7210) Web console: Fix show time of "Connected clusters: N" label

Vasiliy Sisko created IGNITE-7210: - Summary: Web console: Fix show time of "Connected clusters: N" label Key: IGNITE-7210 URL: https://issues.apache.org/jira/browse/IGNITE-7210 Project: Ignite