Re: Explicit lock hang

I'll take a look. Thanks On Sat, Dec 17, 2016 at 2:01 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Folks, > > Can anyone take a look at this ticket? > https://issues.apache.org/jira/browse/IGNITE-4450 > > Looks like pretty serious issue. Most likely it can happen with >

[jira] [Created] (IGNITE-4452) Web console: add execution time to results panel on Queries screen

Pavel Konstantinov created IGNITE-4452: -- Summary: Web console: add execution time to results panel on Queries screen Key: IGNITE-4452 URL: https://issues.apache.org/jira/browse/IGNITE-4452

[jira] [Created] (IGNITE-4451) Web console: improve a tables

Pavel Konstantinov created IGNITE-4451: -- Summary: Web console: improve a tables Key: IGNITE-4451 URL: https://issues.apache.org/jira/browse/IGNITE-4451 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1357: ignite-4293

GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/1357 ignite-4293 storeVal fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4293 Alternatively you can review

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

Dmitriy, Please have a look at IGNITE-4212 description (https://issues.apache.org/jira/browse/IGNITE-4212). The whole purpose of the ticket is to automate benchmarks execution for the end user for a specific Ignite release. Now he/she needs to go through a number of steps like build,

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

Dmitriy Examples folder is not good location for yardstick binaries (but good for yardstick sources). I suppose we should look on how to other products include additional tools. On Sun, Dec 18, 2016 at 6:08 PM, Dmitriy Setrakyan wrote: > On Sun, Dec 18, 2016 at 2:53 AM,

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

On Sun, Dec 18, 2016 at 2:53 AM, Oleg Ostanin wrote: > Dmitriy, ignite-yardstick allows user to run plenty of useful Yardstick > benchmarks, which can be used to check Ignite performance. > In that case, why would it be under the "libs" folder at all? Do we really need to

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

Dmitriy, ignite-yardstick allows user to run plenty of useful Yardstick benchmarks, which can be used to check Ignite performance. On Fri, Dec 16, 2016 at 11:49 PM, Dmitriy Setrakyan wrote: > Oleg, what does ignite-yardstick module do? > > On Fri, Dec 16, 2016 at 12:37