Re: Create separate thread pool for query execution

Guys, I feel very uneasy about proliferation of thread pools in Ignite. I suggest we take step back. Most of the users (including yours truly) have no idea how to correctly configure the existing thread pools, what those thread pools are for (like, management thread pool, or marshaller cache

Re: API for query history

Dmitry, Current QueryMetrics collect metrics for all queries executed on cache without distinguish them, i.e. if you execute SCAN query and SQL_FIELDS_QUERY you will get single metrics with 2 executions (and other counters). I _added_ metrics that are grouped by query type and query text. So,

Re: API for query history

Alexey, I am a bit confused. I just looked at QueryMetrics API and it looks like a subset of the QueryDetailsMetrics you are suggesting. Why not just expand on QueryMetrics API we already have? D. On Mon, Oct 24, 2016 at 9:41 PM, Alexey Kuznetsov wrote: > Dmitriy,

Re: IGNITE-4103 IgniteDataStreamer doesn't throw exception if cache is destroyed

Hi Saikat, I added a comment in the ticket. -Val On Tue, Oct 25, 2016 at 12:51 PM, Saikat Maitra wrote: > Hi, > > I have raised PR[1] for the following jira ticket[2]. > > Please review and let me know if any changes required. > > Regards, > > Saikat > > [1]

IGNITE-4103 IgniteDataStreamer doesn't throw exception if cache is destroyed

Hi, I have raised PR[1] for the following jira ticket[2]. Please review and let me know if any changes required. Regards, Saikat [1] https://github.com/apache/ignite/pull/1186 [2] https://issues.apache.org/jira/browse/IGNITE-4103

[GitHub] ignite pull request #1186: IGNITE-4103 IgniteDataStreamer doesn't throw exce...

GitHub user samaitra opened a pull request: https://github.com/apache/ignite/pull/1186 IGNITE-4103 IgniteDataStreamer doesn't throw exception if cache is de… …stroyed You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-4110) BlockingSslHandler does not properly handle BUFFER_UNDERFLOW after unwrap

Valentin Kulichenko created IGNITE-4110: --- Summary: BlockingSslHandler does not properly handle BUFFER_UNDERFLOW after unwrap Key: IGNITE-4110 URL: https://issues.apache.org/jira/browse/IGNITE-4110

Re: Apache Ignite 1.8 Release

IGNITE-1915 is being reviewed, I think we can make it into 1.8. On Tue, Oct 25, 2016 at 7:26 PM, Denis Magda wrote: > Igniters, > > Looking at the discussions that happen on our dev list regarding Ignite's > improvements I should say that we’re ready to prepare and roll out

Apache Ignite 1.8 Release

Igniters, Looking at the discussions that happen on our dev list regarding Ignite's improvements I should say that we’re ready to prepare and roll out one more Ignite minor release before the end of the year - Apache Ignite 1.8.0. My proposal is to make it available by mid November, somewhere

Re: IGNITE-1943 ignitevisorcmd: wrong behavior for "mclear" command

Thank you Andrey. Regards Saikat On Tue, Oct 25, 2016 at 4:20 PM, Andrey Novikov wrote: > Hi, Saikat > > I reviewed your pull request and add my comments to the ticket. > > > On Sun, Oct 23, 2016 at 3:27 PM, Saikat Maitra > wrote: > >> Hi, >> >> I

[GitHub] ignite pull request #1185: IGNITE-4028 Get rid of OP_META in PlatformAbstrac...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1185 --- 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 #1185: IGNITE-4028 Get rid of OP_META in PlatformAbstrac...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1185 IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4028

Re: IGNITE-1943 ignitevisorcmd: wrong behavior for "mclear" command

Hi, Saikat I reviewed your pull request and add my comments to the ticket. On Sun, Oct 23, 2016 at 3:27 PM, Saikat Maitra wrote: > Hi, > > I have raised PR[1] for the following jira ticket[2]. > > Please review and let me know if any changes required. > > Regards, > >

[GitHub] ignite pull request #1184: Ignite 2523

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

[GitHub] ignite pull request #1181: IGNITE-4074 Refactor async (*future) operations i...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1181 --- 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 #1183: ignite-comm-balance

GitHub user yzhdanov opened a pull request: https://github.com/apache/ignite/pull/1183 ignite-comm-balance You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-comm-balance Alternatively you can review

Re: Threads got stuck

Alper, thanks for clarification, this will definitely help after we get the info I requested. This is the only way to go with the investigation. --Yakov 2016-10-25 11:20 GMT+03:00 Alper Tekinalp : > Hi Yakov. > > I should also mention that we load cache data from one server and

Re: Threads got stuck

Hi Yakov. I should also mention that we load cache data from one server and wait the data to be replicated to others. Can that cause such a situation, too? On Tue, Oct 25, 2016 at 11:14 AM, Yakov Zhdanov wrote: > Alper, > > There can be multiple reasons. > > Can you please

Re: Threads got stuck

Alper, There can be multiple reasons. Can you please reproduce the issue one more time, collect and share the following with us: 1. collect all the logs from all the nodes - clients and servers 2. take threaddumps of all JVMs (from all nodes) with jstack -l --Yakov 2016-10-25 10:49 GMT+03:00

Re: Threads got stuck

Hi. There is also a few logs as : Failed to register marshalled class for more than 10 times in a row (may affect performance). Can it be releated? On Tue, Oct 25, 2016 at 10:32 AM, Alper Tekinalp wrote: > Hi all. > > We have 3 servers and cache configuration like: > >

Threads got stuck

Hi all. We have 3 servers and cache configuration like: For our worker threads we check heartbeat and if a thread did not sent heart beat for