[GitHub] ignite pull request #1016: IGNITE-2881 : SPI queries not working

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1016 IGNITE-2881 : SPI queries not working ... fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2881

[GitHub] ignite pull request #1015: IGNITE-2881 SPI queries not working

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1015 IGNITE-2881 SPI queries not working ... fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2881

[GitHub] ignite pull request #1014: IGNITE-3628: Added fetch page size to configurati...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1014 IGNITE-3628: Added fetch page size to configuration params. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3628

Pull request for IGNITE-3699

Hi community, I raised a pull request [1] Can you please review it? [1] https://github.com/apache/ignite/pull/1011 Thanks.

[jira] [Created] (IGNITE-3815) CacheJdbcPojoStore.loadCache() should check arguments and fail with appropriate exception message

Alexey Kuznetsov created IGNITE-3815: Summary: CacheJdbcPojoStore.loadCache() should check arguments and fail with appropriate exception message Key: IGNITE-3815 URL:

[jira] [Created] (IGNITE-3814) Unstable results of compute benchmarks

Ilya Suntsov created IGNITE-3814: Summary: Unstable results of compute benchmarks Key: IGNITE-3814 URL: https://issues.apache.org/jira/browse/IGNITE-3814 Project: Ignite Issue Type: Bug

Re: Simulating network outages

You can shutdown and then restart (after some sleep) network stack on the host. I remember doing that on Fedora several years ago for exactly the same purposes. --Yakov 2016-08-31 15:21 GMT+03:00 Alexey Goncharuk : > Hi, > > As a starting point you can take a look

[GitHub] ignite pull request #1012: IGNITE-3390: Added DSN configuration window.

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1012 --- 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 #1013: IGNITE-3646 IGFS: Local secondary: Support symlin...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1013 IGNITE-3646 IGFS: Local secondary: Support symlinks for mkdirs operation. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-3813) High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys

Dmitry Karachentsev created IGNITE-3813: --- Summary: High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys Key: IGNITE-3813 URL:

[GitHub] ignite pull request #1012: IGNITE-3390: Added DSN configuration window.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1012 IGNITE-3390: Added DSN configuration window. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3390 Alternatively

Re: Simulating network outages

Hi, As a starting point you can take a look at org.apache.ignite.spi.discovery.tcp.ServerImpl#forceNextNodeFailure which forces DiscoverySpi to drop next node from the topology (not sure if this is what you need). Another idea is to create a test discovery SPI which will terminate all it's

[jira] [Created] (IGNITE-3812) Add executors configuration validation.

Andrew Mashenkov created IGNITE-3812: Summary: Add executors configuration validation. Key: IGNITE-3812 URL: https://issues.apache.org/jira/browse/IGNITE-3812 Project: Ignite Issue Type: