Pessimistic Mode and Transactions and 2PC

Hi, Assume the following: - I have a transaction coordinator and two primary nodes with 0 backup nodes. - Persistence store is enabled. - I'm running a transaction in pessimistic mode with serializable isolation. I have these questions: 1. What exactly happens during the

Re: Metrics for MVCC caches

Ivan, To your 2nd question, can you suggest a few MVCC metrics to get the discussion started? D. On Tue, Aug 7, 2018 at 9:17 AM, Павлухин Иван wrote: > Hi Igniters, > > I am working on cache metrics support for caches with enabled MVCC. As you > may know, during MVCC transaction execution

Re: Folks, how do I generate tar.gz release for Ignite?

Hi John, Please refer to DEVNOTES.txt, it describes the process step by step. -Val On Tue, Aug 7, 2018 at 12:14 PM John Wilson wrote: > Hi, > > How do I generate tar.gz for Ignite from source? > > Thanks, >

Folks, how do I generate tar.gz release for Ignite?

Hi, How do I generate tar.gz for Ignite from source? Thanks,

[GitHub] ignite pull request #4497: IGNITE-9225

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/4497 IGNITE-9225 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-9225 Alternatively you can review and apply these changes as

Re: Spark SQL Table Name Resolution

Thanks Val, here’s the ticket: https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-9228 (Thanks for correcting my terminology - I work mostly with the traditional CacheConfiguration interface where

[jira] [Created] (IGNITE-9228) Spark SQL Table Schema Specification

Stuart Macdonald created IGNITE-9228: Summary: Spark SQL Table Schema Specification Key: IGNITE-9228 URL: https://issues.apache.org/jira/browse/IGNITE-9228 Project: Ignite Issue Type:

Re: Spark SQL Table Name Resolution

Stuart, Two tables can have same names only if they are located in different schemas. Said that, sdding schema name support makes sense to me for sure. We can implement this using either separate SCHEMA_NAME parameter, or similar to what you suggested in option 3 but with schema name instead of

Spark SQL Table Name Resolution

Hello Igniters, The Ignite Spark SQL interface currently takes just “table name” as a parameter which it uses to supply a Spark dataset with data from the underlying Ignite SQL table with that name. To do this it loops through each cache and finds the first one with the given table name [1].

[GitHub] ignite pull request #4496: IGNITE-9195

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/4496 IGNITE-9195 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-9195 Alternatively you can review and apply these changes as

Re: Creation of dynamic cache

Hi, > I want to add a simulation of IgniteCheckedException in during of cache creation to IgniteAbstractDynamicCacheStartFailTest > and delete the catch block from CacheAffinitySharedManager#processCacheStartRequests method Looks like a plan :) Thanks, S. вт, 7 авг. 2018 г. в 16:42, Denis Garus

[GitHub] ignite pull request #4494: Ignite 2.4.7.b8

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

welcome

Hello, Ignite Community! My name is Iurii. I want to contribute to Apache Ignite. my JIRA user name is jooger. Any help on this will be appreciated. Thanks! -- Live with a smile! :D

[jira] [Created] (IGNITE-9225) Cache 7 (With Persistence) configuration halted by failure handler.

Pavel Pereslegin created IGNITE-9225: Summary: Cache 7 (With Persistence) configuration halted by failure handler. Key: IGNITE-9225 URL: https://issues.apache.org/jira/browse/IGNITE-9225 Project:

Metrics for MVCC caches

Hi Igniters, I am working on cache metrics support for caches with enabled MVCC. As you may know, during MVCC transaction execution entry versions are written to storage right away (without deferring until commit). So, it is not obvious for me if we should update writes count right away or defer

Re: Orphaned, duplicate, and main-class tests!

Hello! Thank you Dmitriy, and thanks to everybody who participated in discussions. I have created tickets for next steps: https://issues.apache.org/jira/browse/IGNITE-9210 (with subtasks) https://issues.apache.org/jira/browse/IGNITE-9222 https://issues.apache.org/jira/browse/IGNITE-9223 As

Re: Creation of dynamic cache

Hello, Slava! Yes, I agree with you. If we get rid of this catch block, everything works well. But, IgniteAbstractDynamicCacheStartFailTest isn't honest enough because it can't expose this failure. We should simulate not only RuntimeException but IgniteCheckedException as well. I want to add a

[jira] [Created] (IGNITE-9224) MVCC SQL: Cache metrics

Ivan Pavlukhin created IGNITE-9224: -- Summary: MVCC SQL: Cache metrics Key: IGNITE-9224 URL: https://issues.apache.org/jira/browse/IGNITE-9224 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-9223) Vacate IgnitePerformanceTestSuite, or convert to a real test suite with TC runs

Ilya Kasnacheev created IGNITE-9223: --- Summary: Vacate IgnitePerformanceTestSuite, or convert to a real test suite with TC runs Key: IGNITE-9223 URL: https://issues.apache.org/jira/browse/IGNITE-9223

[jira] [Created] (IGNITE-9222) Vacate and delete IgniteLostAndFoundTestSuite

Ilya Kasnacheev created IGNITE-9222: --- Summary: Vacate and delete IgniteLostAndFoundTestSuite Key: IGNITE-9222 URL: https://issues.apache.org/jira/browse/IGNITE-9222 Project: Ignite Issue

[jira] [Created] (IGNITE-9221) Uncomment 25 test classes in various Indexing test suites

Ilya Kasnacheev created IGNITE-9221: --- Summary: Uncomment 25 test classes in various Indexing test suites Key: IGNITE-9221 URL: https://issues.apache.org/jira/browse/IGNITE-9221 Project: Ignite

Re: welcome

Sergei, you are welcome! I have added you to contributors. Please go ahead! --Yakov 2018-08-07 16:18 GMT+03:00 s v : > Hello, Ignite Community! > > My name is Sergei. I want to contribute to Apache Ignite and want to start > with this issue - https://issues.apache.org/jira/browse/IGNITE-9141 ,

welcome

Hello, Ignite Community! My name is Sergei. I want to contribute to Apache Ignite and want to start with this issue - https://issues.apache.org/jira/browse/IGNITE-9141 , my JIRA user name is SGrimstad. Any help on this will be appreciated. Thanks!

[jira] [Created] (IGNITE-9218) Uncomment 18 test classes in IgniteCacheTestSuite{3,5,6}

Ilya Kasnacheev created IGNITE-9218: --- Summary: Uncomment 18 test classes in IgniteCacheTestSuite{3,5,6} Key: IGNITE-9218 URL: https://issues.apache.org/jira/browse/IGNITE-9218 Project: Ignite

[jira] [Created] (IGNITE-9217) Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2)

Ilya Kasnacheev created IGNITE-9217: --- Summary: Uncomment 24 test classes in IgniteCacheTestSuite2 (Cache 2) Key: IGNITE-9217 URL: https://issues.apache.org/jira/browse/IGNITE-9217 Project: Ignite

[jira] [Created] (IGNITE-9215) Uncomment 23 test classes in various core suites (see inside)

Ilya Kasnacheev created IGNITE-9215: --- Summary: Uncomment 23 test classes in various core suites (see inside) Key: IGNITE-9215 URL: https://issues.apache.org/jira/browse/IGNITE-9215 Project: Ignite

[jira] [Created] (IGNITE-9213) CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout

Ilya Lantukh created IGNITE-9213: Summary: CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout Key: IGNITE-9213 URL: https://issues.apache.org/jira/browse/IGNITE-9213

[jira] [Created] (IGNITE-9214) Uncomment 21 test classes in misc cache test suites (see inside)

Ilya Kasnacheev created IGNITE-9214: --- Summary: Uncomment 21 test classes in misc cache test suites (see inside) Key: IGNITE-9214 URL: https://issues.apache.org/jira/browse/IGNITE-9214 Project:

[jira] [Created] (IGNITE-9212) Uncomment 18 test classes in various modules' sutes (see inside)

Ilya Kasnacheev created IGNITE-9212: --- Summary: Uncomment 18 test classes in various modules' sutes (see inside) Key: IGNITE-9212 URL: https://issues.apache.org/jira/browse/IGNITE-9212 Project:

[jira] [Created] (IGNITE-9211) Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite

Ilya Kasnacheev created IGNITE-9211: --- Summary: Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite Key: IGNITE-9211 URL: https://issues.apache.org/jira/browse/IGNITE-9211 Project: Ignite

[jira] [Created] (IGNITE-9210) Uncomment tests in test suites, make sure they pass without hang-ups or errors.

Ilya Kasnacheev created IGNITE-9210: --- Summary: Uncomment tests in test suites, make sure they pass without hang-ups or errors. Key: IGNITE-9210 URL: https://issues.apache.org/jira/browse/IGNITE-9210

[jira] [Created] (IGNITE-9209) GridDistributedTxMapping.toString() returns broken string

Ryabov Dmitrii created IGNITE-9209: -- Summary: GridDistributedTxMapping.toString() returns broken string Key: IGNITE-9209 URL: https://issues.apache.org/jira/browse/IGNITE-9209 Project: Ignite

Re: Creation of dynamic cache

Hello Denis, It seems we can just comment out the following catch block: ``` try { if (startCache) { cctx.cache().prepareCacheStart(req.startCacheConfiguration(), cacheDesc, nearCfg, evts.topologyVersion(),

[jira] [Created] (IGNITE-9208) Allow proper handling of transactions if node is stopped using stop(false)

Alexei Scherbakov created IGNITE-9208: - Summary: Allow proper handling of transactions if node is stopped using stop(false) Key: IGNITE-9208 URL: https://issues.apache.org/jira/browse/IGNITE-9208

[GitHub] ignite pull request #3464: IGNITE-7615 Lost and Found suite for orphaned tes...

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

[jira] [Created] (IGNITE-9207) Update Web Console dependencies

Alexey Kuznetsov created IGNITE-9207: Summary: Update Web Console dependencies Key: IGNITE-9207 URL: https://issues.apache.org/jira/browse/IGNITE-9207 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #4495: IGNITE-9178 Partition lost event are not triggere...

GitHub user pvinokurov opened a pull request: https://github.com/apache/ignite/pull/4495 IGNITE-9178 Partition lost event are not triggered if multiple nodes … …left cluster You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-9206) Node can't join to ring if all existing nodes have stopped and another new node joined ahead

Pavel Kovalenko created IGNITE-9206: --- Summary: Node can't join to ring if all existing nodes have stopped and another new node joined ahead Key: IGNITE-9206 URL:

Re: [MTCGA]: new failures in builds [1570331] needs to be handled

Maxim, if it is a new failure, why is it filed as Minor and is not assigned to any release? I would suggest that any new failure should be filed as a Blocker and assigned to the next release. D. On Tue, Aug 7, 2018 at 12:55 AM, Maxim Muzafarov wrote: > Igniters, > > Seems this is a new

Re: Orphaned, duplicate, and main-class tests!

Hi Igniters, I've merged chages for following tickets IGNITE-7615: Find orphaned tests without test suites, create separate test suite for them; IGNITE-8344: Remove duplicate tests and suites; IGNITE-8345: Streamline tests' class names: mark Abstract and Load tests obviously so; After including

[GitHub] ignite pull request #4494: Ignite 2.4.7.b8

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/4494 Ignite 2.4.7.b8 Created for testing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.7.b8 Alternatively

[GitHub] ignite pull request #4493: Ignite 1.8.21

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/4493 Ignite 1.8.21 Created for testing You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.8.21 Alternatively you

[GitHub] ignite pull request #4492: Ignite-2.5.1-p13

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/4492 Ignite-2.5.1-p13 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p13 Alternatively you can

[GitHub] ignite pull request #4488: IGNITE-9197 Java thin client querying empty table...

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

Re: find bugs code check

Hi, igniters, As a result of this discussion [1] two issue were created: - NPE and CCE on equals() methods [2]; - Methods may fail to close stream in core module [3]. In addition to the list of bugs from the letter, FindBugs plug-in was additionally analyzed the core module for the

[jira] [Created] (IGNITE-9204) Test org.apache.ignite.client.ReliabilityTest@testFailover fails intermittently

Alexey Kukushkin created IGNITE-9204: Summary: Test org.apache.ignite.client.ReliabilityTest@testFailover fails intermittently Key: IGNITE-9204 URL: https://issues.apache.org/jira/browse/IGNITE-9204

[GitHub] ignite pull request #4491: IGNITE-9193 Stop child python processes on parent...

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/4491 IGNITE-9193 Stop child python processes on parent stop. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-9203) Web Console: Actualize README.txt for direct install.

Alexey Kuznetsov created IGNITE-9203: Summary: Web Console: Actualize README.txt for direct install. Key: IGNITE-9203 URL: https://issues.apache.org/jira/browse/IGNITE-9203 Project: Ignite

Re: Creation of dynamic cache

Thank you! This is what I need. пн, 6 авг. 2018 г. в 16:09, Maxim Muzafarov : > Denis, > > At the first glance looks like the main problem here is about > rollbacking of cache creation due to exception. Incorrect rollback > leads us to critial problem with ExchangeWorker as expected. It's >