Re: Where and how to store metrics for queries.

Dima & Val, My first intention was to store metrics locally and collect them on demand. But after that I start to think about following scenarios: What if we have a grid with clients that connected to grid, execute some query and *disconnected*? In this case we would have no option to collect

Re: Official Apache Ignite meetup - Sept. 22nd - London

Hi Christos, I'like this video. Looking forward for new videos! Denis, does it make sense to add link to this video to https://ignite.apache.org "Latest news" section? -- Alexey Kuznetsov

Re: Official Apache Ignite meetup - Sept. 22nd - London

Hi Christos, Thanks for sharing! The use case is really unique. It was useful to learn how Apache Ignite and GridGain are applicable in betting and gambling platforms. — Denis > On Oct 6, 2016, at 3:27 AM, Christos Erotocritou > wrote: > > Hello Igniters, > > The

Re: Where and how to store metrics for queries.

Alexey, Why do you need to store metrics in cache? For all our metrics we just store them locally and aggregate on demand. What is the reason for different approach here? Generally, I think we should avoid using system caches wherever possible, and probably rework current usages of such caches.

Re: Where and how to store metrics for queries.

Alexey, why do you need to store the SQL metrics in a cache? I would avoid it. Instead, is there a way to have a local metric store on every node and have WebConsole send a task to each node and aggregate the results? D. On Wed, Oct 5, 2016 at 9:56 PM, Alexey Kuznetsov

[jira] [Created] (IGNITE-4045) .Net: Support DML API

Denis Magda created IGNITE-4045: --- Summary: .Net: Support DML API Key: IGNITE-4045 URL: https://issues.apache.org/jira/browse/IGNITE-4045 Project: Ignite Issue Type: Bug Components:

Re: IGNITE-3722 Cached in a file text must be written with UTF-8 charset, not default

Thank you Semen !!! Regards Saikat On Thu, Oct 6, 2016 at 11:13 AM, Semyon Boikov wrote: > Hi, > > I reviewed and merged your fix. Thanks for contribution! > > Thanks! > > On Tue, Oct 4, 2016 at 10:06 PM, Saikat Maitra > wrote: > > > Hi, > > > > I

[GitHub] ignite pull request #1151: Ignite 4011

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

[jira] [Created] (IGNITE-4044) Add an option to always authenticate local node

Dmitriy Govorukhin created IGNITE-4044: -- Summary: Add an option to always authenticate local node Key: IGNITE-4044 URL: https://issues.apache.org/jira/browse/IGNITE-4044 Project: Ignite

[jira] [Created] (IGNITE-4043) Visor CMD: cache scan - support execution on selected node only

Alexey Kuznetsov created IGNITE-4043: Summary: Visor CMD: cache scan - support execution on selected node only Key: IGNITE-4043 URL: https://issues.apache.org/jira/browse/IGNITE-4043 Project:

Re: Official Apache Ignite meetup - Sept. 22nd - London

Hello Igniters, The recording from our most recent Ignite London meetup is ready to share. This time we had the pleasure of having Sam Lawrence from FSB Technologies talk about how they have used Apache Ignite to transform their online sports betting platform. Check it out:

[jira] [Created] (IGNITE-4042) Refactor async operations

Pavel Tupitsyn created IGNITE-4042: -- Summary: Refactor async operations Key: IGNITE-4042 URL: https://issues.apache.org/jira/browse/IGNITE-4042 Project: Ignite Issue Type: Sub-task

Re: Concurrent read-through

I don't think there is a way to fix this other than having some bounded collection of futures finished with "null" result. --Yakov 2016-10-04 23:09 GMT+03:00 Dmitriy Setrakyan : > Hm... sounds like a bug. > > On Tue, Oct 4, 2016 at 1:06 PM, Valentin Kulichenko < >

[GitHub] ignite pull request #1150: Ignite 4041

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

[jira] [Created] (IGNITE-4041) Consistent thread pool resolution for IO and closures.

Vladimir Ozerov created IGNITE-4041: --- Summary: Consistent thread pool resolution for IO and closures. Key: IGNITE-4041 URL: https://issues.apache.org/jira/browse/IGNITE-4041 Project: Ignite

[jira] [Created] (IGNITE-4040) Web console: Do not scroll summary panel, scroll only table content

Pavel Konstantinov created IGNITE-4040: -- Summary: Web console: Do not scroll summary panel, scroll only table content Key: IGNITE-4040 URL: https://issues.apache.org/jira/browse/IGNITE-4040

Re: Start threads in our pools on demand?

Implemented. Will appear in master soon. Benchmarks shown no performance drop. On Thu, Sep 29, 2016 at 3:16 PM, Vladimir Ozerov wrote: > Ignite node thread dump after applying quick and dirty solution - just > added *ThreadPoolExecutor.allowCoreThreadTimeOut(true)* to base

[GitHub] ignite pull request #1130: Ignite 4001

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1130 --- 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 #1149: IGNITE-4034 Get rid of specialized methods in pla...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1149 IGNITE-4034 Get rid of specialized methods in platform targets You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-4034