Re: IgniteSet implementation: changes required

On Thu, Mar 15, 2018 at 12:24 AM, Andrey Kuznetsov wrote: > Dmitriy, > > It's technically possible to produce both kinds of sets with > {{Ignite.set()}} call, but this will require to one more argument ('small' > vs 'large'). Doesn't it look less inuitive than separate > {{IgniteCache.asSet()}} ?

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Ivan, Is there a performance difference between LOG_ONLY and LOG_ONLY_SAFE? D. On Thu, Mar 15, 2018 at 4:23 PM, Ivan Rakov wrote: > Igniters and especially Native Persistence experts, > > We decided to change default WAL mode from DEFAULT(FSYNC) to LOG_ONLY in > 2.4 release. That was difficult

[GitHub] ignite pull request #3644: IGNITE-7800: Correction for IgniteSystemPropertie...

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

[GitHub] ignite pull request #3644: IGNITE-7800: Correction for IgniteSystemPropertie...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/3644 IGNITE-7800: Correction for IgniteSystemProperties.IGNITE_NO_SHUTDOWN… …_HOOK javadoc. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shrom

[jira] [Created] (IGNITE-7970) Fix E2E test with user notifications

Alexander Kalinin created IGNITE-7970: - Summary: Fix E2E test with user notifications Key: IGNITE-7970 URL: https://issues.apache.org/jira/browse/IGNITE-7970 Project: Ignite Issue Type: B

Fwd: [ANNOUNCE] Apache Ignite 2.4.0 Released: Machine Learning GA and Spark DataFrames

Igniters, Please use your social media accounts to promote the release we were working on for a while: https://twitter.com/denismagda/status/974438862465351681 It will be great if you can translate the article into your native language and publish it in your country of origin.

[ANNOUNCE] Apache Ignite 2.4.0 Released: Machine Learning GA and Spark DataFrames

Usually, Ignite community rolls out a new version once in 3 months, but we had to make an exception for Apache Ignite 2.4 that consumed five months in total. We could easily blame Thanksgiving, Christmas and New Year holidays for the delay and would be forgiven, but, in fact, we were forging the r

Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Igniters and especially Native Persistence experts, We decided to change default WAL mode from DEFAULT(FSYNC) to LOG_ONLY in 2.4 release. That was difficult decision: we sacrificed power loss / OS crash tolerance, but gained significant performance boost. From my perspective, LOG_ONLY is right

Re: IEP-14: Ignite failures handling (Discussion)

On Thu, Mar 15, 2018 at 5:21 AM, Dmitry Pavlov wrote: > Hi Dmitriy, > > It seems, here everyone agrees that killing the process will give a more > guaranteed result. The question is that the majority in the community does > not consider this to be acceptable in case Ignite as started as embedded

Re: Partition eviction failed, this can cause grid hang. (Caused by: java.lang.IllegalStateException: Failed to get page IO instance (page content is corrupted))

Hi, guys. I've got a reproducer for a problem which is generally reported as "Caused by: java.lang.IllegalStateException: Failed to get page IO instance (page content is corrupted)". Actually it reproduces the result. I don't have an idea how the data has been corrupted, but the cluster node doesn

Re: Data eviction/expiration from Ignite persistence

On Thu, Mar 15, 2018 at 12:31 PM, Denis Magda wrote: > > > > Agree with AG. There is a difference between expiration and eviction. If > an > > entry is expired, then it should be removed from the store, regardless if > > it is in memory or on disk. > > > Well, then it works this way now depending

Re: readme.io weird interface element

Please create a ticket and let's fix it in the nearest future. -- Denis On Thu, Mar 15, 2018 at 12:47 PM, Prachi Garg wrote: > That's the download button. Tables on feature pages are downloadable in > pdf, csv format. There is a javascript code embedded with the table > element. Not sure why it

Re: readme.io weird interface element

That's the download button. Tables on feature pages are downloadable in pdf, csv format. There is a javascript code embedded with the table element. Not sure why it doesn't work on the download page; works fine on other pages. On Thu, Mar 15, 2018 at 12:16 PM, Denis Magda wrote: > Have no idea,

Re: Partition loss policy - how to use?

The monitoring screen that should show the partition loss metrics is not in open source. It's a plugin GridGain built on top of the console foundation. However, we can use it for free via that deployment even for Ignite clusters: https://console.gridgain.com/ -- Denis On Wed, Mar 14, 2018 at 8:2

Re: Data eviction/expiration from Ignite persistence

> > Agree with AG. There is a difference between expiration and eviction. If an > entry is expired, then it should be removed from the store, regardless if > it is in memory or on disk. Well, then it works this way now depending on a memory configuration: - memory only mode: expired entry rem

Re: Timeline for support of compute functions by thin clients

Pavel, I just don't see a substantial reason why we need to support the compute APIs. As you properly mentioned, it's not easy to copy all the APIs and, again, for what. It's right that the thin client allows decoupling .NET from JVM, but its implementation won't be more performant than the regul

Re: readme.io weird interface element

Have no idea, just makes the table looks nicer :) Prachi, what is this for? It's not clear from the HTML sources. -- Denis On Thu, Mar 15, 2018 at 12:09 PM, Petr Ivanov wrote: > Sorry for misleading. I meant https://ignite.apache.org/download.cgi > indeed. > > > > > On 15 Mar 2018, at 22:05, D

Re: Apache Ignite RPM packaging (Stage II)

I suppose that most everything if not all from libs/options will go to OPTIONAL (I’d call it simply ‘apache-ignite-libs'). More precise lib selection (if something from optional would better to have in core package) will be discussed right after preliminary split architecture agreement. > On

Re: Apache Ignite RPM packaging (Stage II)

I like idea of keeping simple system of modules, so +1 from me. Where optional libs (e.g Direct IO plugin) would be included, would it be core or optional? чт, 15 мар. 2018 г. в 22:09, Denis Magda : > > > > > > > > How big would be a final core module? > > Around 30M. Can be shrinked to ~15M if

Re: readme.io weird interface element

Sorry for misleading. I meant https://ignite.apache.org/download.cgi indeed. > On 15 Mar 2018, at 22:05, Denis Magda wrote: > > Petr, > > What's that? It doesn't look like the readme.io doc that hosts all Ignite > docs: > https://apacheignite.readme.io/docs > > -- > Denis > > On Thu, Mar 15

Re: Apache Ignite RPM packaging (Stage II)

> > > > > How big would be a final core module? > Around 30M. Can be shrinked to ~15M if separate Visor and create it’s own > package. Guys, 30 vs 280M is a hge difference. I would agree with Petr and propose the simplest modular system: - core module that includes basic Ignite capabilit

Re: readme.io weird interface element

Petr, What's that? It doesn't look like the readme.io doc that hosts all Ignite docs: https://apacheignite.readme.io/docs -- Denis On Thu, Mar 15, 2018 at 1:52 AM, vveider wrote: > Hi, all! > > > Does anyone know what is this button with arrow and disk at the right > corner > of versions list

Re: TeamCity test names refactoring

I think I agree about digits. Will fix. > On 15 Mar 2018, at 20:09, Dmitry Pavlov wrote: > > In using digits in suite name, there is nothing to do with > short-sightedness. > > I think this is a matter of taste, so I would like to hear the opinion of > all. > > чт, 15 мар. 2018 г. в 20:02, Pe

Re: Ignite contibutors page

Dmitriy, Alexey, Done, now your names are engraved on the page ;) -- Denis On Thu, Mar 15, 2018 at 2:34 AM, Dmitriy Shabalin wrote: > I'm not mentioned on the community contributors page: > https://ignite.apache.org/community/resources.html > > pls add me, dmitriyff (Dmitriy Shabalin) > > > >

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Looks like we're good to go with the announce. I'll blast it out today. -- Denis On Thu, Mar 15, 2018 at 11:19 AM, Pavel Tupitsyn wrote: > Igniters, is there still something blocking the release announcement? > > On Thu, Mar 15, 2018 at 7:00 AM, Petr Ivanov wrote: > > > I am sure about AWS and

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Igniters, is there still something blocking the release announcement? On Thu, Mar 15, 2018 at 7:00 AM, Petr Ivanov wrote: > I am sure about AWS and GC images now — there is only script inside that > have IGNITE_VERSION on input and runs apacheignite/ignite: > docker image inside the container. >

Re: Partition recovery issue on partition loss.

I dared to set fix version to 2.5 and increased the severity. It's important to fix the race since we've just released the partition loss functionality in 2.4 and it's already broken. Andrey, please keep us posted. If you didn't fix it, we would need to find another contributor. -- Denis On Thu,

[GitHub] ignite pull request #3622: IGNITE-7770 For TC tests only

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3622 ---

Re: TeamCity test names refactoring

In using digits in suite name, there is nothing to do with short-sightedness. I think this is a matter of taste, so I would like to hear the opinion of all. чт, 15 мар. 2018 г. в 20:02, Petr Ivanov : > I understand conservatism and inertia of such changes. > But thus we are sticking to arrogance

[GitHub] ignite pull request #3575: OSGI tests fail

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

Re: TeamCity test names refactoring

I understand conservatism and inertia of such changes. But thus we are sticking to arrogance and shortsightedness of previous engineers who worked on this project, while trying to make it better. My point is - without some legacy cleaning and approaches review it becomes impossible to introduce a

[GitHub] ignite pull request #3643: IGNITE-7811: ODBC: Implemented connection failove...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3643 IGNITE-7811: ODBC: Implemented connection failover You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7811 Alternat

Re: TeamCity test names refactoring

I think it is better to keep existing naming because Igniters are used to it. Moreover a lot of issues use suite name as reference on where test is located. So I prefer existing naming. чт, 15 мар. 2018 г. в 19:43, vveider : > Hi, Igniters! > > > Took the liberty to introduce minor refactoring i

TeamCity test names refactoring

Hi, Igniters! Took the liberty to introduce minor refactoring into test build names in our (now) main test project Ignite Tests 2.4+ (Java 8) [1] Changes affected the numeration of tests with common name, i.e Ignite Basic => Ignite Basic [I] Ignite Basic 2 => Ignite Basic [II] And so on.

Re: Partition eviction failed, this can cause grid hang. (Caused by: java.lang.IllegalStateException: Failed to get page IO instance (page content is corrupted))

Hi Alexey, It may be serious issue. Could you recommend expert here who can pick up this? Sincerely, Dmitriy Pavlov чт, 15 мар. 2018 г. в 19:25, Arseny Kovalchuk : > Hi, guys. > > I've got a reproducer for a problem which is generally reported as "Caused > by: java.lang.IllegalStateException: F

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

I see now. Thank you. Nikolay, could you please merge this change? чт, 15 мар. 2018 г. в 18:48, Vyacheslav Daradur : > In brief: > Nodes in *separate* JVMs are shutting down by the computing task > *StopGridTask* which has sent from *local* JVM *synchronously* that > means *local* node must wait

Fwd: [jira] [Resolved] (IGNITE-7646) OSGI tests fail to unlock build directory causing following builds to fail to start

Hi Peter, Vyacheslav, thank you for solving this issue. Each contribution like this helps Ignite to achieve stable test runs. -- Forwarded message - From: Peter Ivanov (JIRA) Date: чт, 15 мар. 2018 г. в 18:37 Subject: [jira] [Resolved] (IGNITE-7646) OSGI tests fail to unlock bui

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

In brief: Nodes in *separate* JVMs are shutting down by the computing task *StopGridTask* which has sent from *local* JVM *synchronously* that means *local* node must wait for task's finish. At the same time when a node in *separate* JVM executes the received *StopGridTask* which *synchronously* c

[jira] [Created] (IGNITE-7969) Fluky failure of IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup

Aleksey Plekhanov created IGNITE-7969: - Summary: Fluky failure of IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup Key: IGNITE-7969 URL: https://issues.apache.org/jira/browse/IGNIT

[GitHub] ignite pull request #3640: IGNITE-7965: Robin-hood hashing may fail with neg...

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

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

Please address comments in PR. I did not fully understood why sync GridStopMessage message was lost, but async will be successfull. Probably we need discuss it briefly. чт, 1 мар. 2018 г. в 12:11, Vyacheslav Daradur : > Thank you, Dmitry! > > I'll join this review soon. > > On Thu, Mar 1, 2018 a

Re: Partition recovery issue on partition loss.

Hi Andrew Mashenkov, would you like to pick up issue? Sincerely, Dmitriy Pavlov чт, 15 мар. 2018 г. в 6:23, Dmitriy Setrakyan : > Completely agree, we must fix this. I like the proposed design. We should > also specify that resetLostPartitions() method should return true and > false. > > Val, d

[GitHub] ignite pull request #3642: IGNITE-7961

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3642 IGNITE-7961 Benchmarks for rebalance. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7961 Alternatively you can

Re: Atomic sequence and topology exception

Hi Pavel, would you like to prepare fix/PR for this ticket? Sincerely, Dmitriy Pavlov чт, 15 мар. 2018 г. в 16:36, Vinokurov Pavel : > Alexey, > > Thank you for your explanation. > I have created the ticket > https://issues.apache.org/jira/browse/IGNITE-7968 > with attached reproducer. > > 2018

Re: Ignite Platform .NET Inspections problems

Hi Pavel, Let me say thank you from me too. All test fixes helps us to run review more easy. Sincerely, Dmitriy Pavlov чт, 15 мар. 2018 г., 16:49 Pavel Tupitsyn : > Suppressed these two as well > > On Thu, Mar 15, 2018 at 4:45 PM, Petr Ivanov wrote: > > > BTW, preliminary run still shows 2 fai

Re: Ignite Platform .NET Inspections problems

Suppressed these two as well On Thu, Mar 15, 2018 at 4:45 PM, Petr Ivanov wrote: > BTW, preliminary run still shows 2 failed inspections [1] > > > [1] https://ci.ignite.apache.org/viewLog.html?buildId=1138826 > > > > On 15 Mar 2018, at 15:41, Petr Ivanov wrote: > > > > I see. Will wait for resu

Re: Ignite Platform .NET Inspections problems

BTW, preliminary run still shows 2 failed inspections [1] [1] https://ci.ignite.apache.org/viewLog.html?buildId=1138826 > On 15 Mar 2018, at 15:41, Petr Ivanov wrote: > > I see. Will wait for result tomorrow. > > > >> On 15 Mar 2018, at 15:40, Pavel Tupitsyn wrote: >> >> Just waiting for

Re: Atomic sequence and topology exception

Alexey, Thank you for your explanation. I have created the ticket https://issues.apache.org/jira/browse/IGNITE-7968 with attached reproducer. 2018-03-15 10:23 GMT+03:00 Alexey Goncharuk : > Pavel, > > The exception from an AtomicSequence looks like a bug to me. Ignite should > retry all operatio

[jira] [Created] (IGNITE-7968) IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed to acquire lock for keys

Pavel Vinokurov created IGNITE-7968: --- Summary: IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed to acquire lock for keys Key: IGNITE-7968 URL: https://issues.apache.org/jira/browse/IG

[GitHub] ignite pull request #3641: Keep marshaller mappings in consistent state: bac...

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/3641 Keep marshaller mappings in consistent state: backport to 2.3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite

[jira] [Created] (IGNITE-7967) DataRegionMetrics#totalAllocatedPages is invalid if metrics were enabled during runtime

Alexey Goncharuk created IGNITE-7967: Summary: DataRegionMetrics#totalAllocatedPages is invalid if metrics were enabled during runtime Key: IGNITE-7967 URL: https://issues.apache.org/jira/browse/IGNITE-7967

Re: Ignite Platform .NET Inspections problems

I see. Will wait for result tomorrow. > On 15 Mar 2018, at 15:40, Pavel Tupitsyn wrote: > > Just waiting for automatic build in master branch > > On Thu, Mar 15, 2018 at 3:39 PM, Petr Ivanov wrote: > >> Nice news, Pavel! >> >> Can you point to the exact build where you are checking changes

Re: Ignite Platform .NET Inspections problems

Just waiting for automatic build in master branch On Thu, Mar 15, 2018 at 3:39 PM, Petr Ivanov wrote: > Nice news, Pavel! > > Can you point to the exact build where you are checking changes, please? > > > > > On 15 Mar 2018, at 15:34, Pavel Tupitsyn wrote: > > > > Hi Petr, > > > > I've fixed th

Re: Ignite Platform .NET Inspections problems

Nice news, Pavel! Can you point to the exact build where you are checking changes, please? > On 15 Mar 2018, at 15:34, Pavel Tupitsyn wrote: > > Hi Petr, > > I've fixed that yesterday [1], waiting for the build to verify. > > [1] > https://github.com/apache/ignite/commit/a69e1acba8a69f1818f

Re: Ignite Platform .NET Inspections problems

Hi Petr, I've fixed that yesterday [1], waiting for the build to verify. [1] https://github.com/apache/ignite/commit/a69e1acba8a69f1818fa9182a1167302f81b93ec On Thu, Mar 15, 2018 at 1:07 PM, Petr Ivanov wrote: > HI, Pavel. > > > After TeamCity update from 2017.1.3 to 2017.2.2 build Ignite Plat

Re: IEP-14: Ignite failures handling (Discussion)

Hi Dmitriy, It seems, here everyone agrees that killing the process will give a more guaranteed result. The question is that the majority in the community does not consider this to be acceptable in case Ignite as started as embedded lib (e.g. from Java, using Ignition.start()) What can help to ac

[jira] [Created] (IGNITE-7966) MVCC TX Review cache/Ignite configuration for MVCC needs

Igor Seliverstov created IGNITE-7966: Summary: MVCC TX Review cache/Ignite configuration for MVCC needs Key: IGNITE-7966 URL: https://issues.apache.org/jira/browse/IGNITE-7966 Project: Ignite

[GitHub] ignite pull request #3640: IGNITE-7965: Robin-hood hashing may fail with neg...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3640 IGNITE-7965: Robin-hood hashing may fail with negative index in case … …backward shift finished with full table scan You can merge this pull request into a Git repository by running: $ gi

Re: IGNITE-5357 is ready for review (Replicated cache reads load balancing)

Dmitry, I'm looking forward to the news. Thanks in advance! On Thu, Mar 15, 2018 at 1:10 PM, Dmitry Pavlov wrote: > I would like to take a look to code now, if you don't mind. > > But I need to check if there is critical bug introduced to Ignite by my > recent fix. So I need some time to researc

Re: Stop nodes after test by default - IGNITE-6842

Dmtry, Can we proceed with this change? I've done with fixing review comments and tests that you mentioned before. TC: https://ci.ignite.apache.org/viewLog.html?buildId=1138151 JIRA: https://issues.apache.org/jira/browse/IGNITE-6842 Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-C

[jira] [Created] (IGNITE-7965) Robin-hood hashing may fail with negative index in case backward shift finished with full table scan

Dmitriy Pavlov created IGNITE-7965: -- Summary: Robin-hood hashing may fail with negative index in case backward shift finished with full table scan Key: IGNITE-7965 URL: https://issues.apache.org/jira/browse/IGNIT

Re: Why does DataStreamer swallow exceptions?

Hello! I have filed an issue https://issues.apache.org/jira/browse/IGNITE-7962 - going to work on it soon. I have also filed a ticket about usability issue: https://issues.apache.org/jira/browse/IGNITE-7963 Feedback is appreciated. Regards, -- Ilya Kasnacheev 2018-03-14 23:35 GMT+03:00 Valent

[jira] [Created] (IGNITE-7963) Futures from DataStreamer.addData() fail to complete if DataStreamer.flush() is never called

Ilya Kasnacheev created IGNITE-7963: --- Summary: Futures from DataStreamer.addData() fail to complete if DataStreamer.flush() is never called Key: IGNITE-7963 URL: https://issues.apache.org/jira/browse/IGNITE-7963

[jira] [Created] (IGNITE-7964) Read a key from metastorage may hang on node restart

Sergey Chugunov created IGNITE-7964: --- Summary: Read a key from metastorage may hang on node restart Key: IGNITE-7964 URL: https://issues.apache.org/jira/browse/IGNITE-7964 Project: Ignite I

[jira] [Created] (IGNITE-7962) More cases of suppressed exceptions in IsolatedUpdater

Ilya Kasnacheev created IGNITE-7962: --- Summary: More cases of suppressed exceptions in IsolatedUpdater Key: IGNITE-7962 URL: https://issues.apache.org/jira/browse/IGNITE-7962 Project: Ignite

Re: IGNITE-5357 is ready for review (Replicated cache reads load balancing)

I would like to take a look to code now, if you don't mind. But I need to check if there is critical bug introduced to Ignite by my recent fix. So I need some time to research bug, and then can come back to review. чт, 15 мар. 2018 г. в 13:04, Vyacheslav Daradur : > So, what's the next step? > >

Ignite Platform .NET Inspections problems

HI, Pavel. After TeamCity update from 2017.1.3 to 2017.2.2 build Ignite Platform .NET Inspections [1] started to show 12-14 failed inspections. Can you help and check settings for this build, please? Or give any recommendations on how to fix this? Thanks! [1] https://ci.ignite.apache.org/vi

Re: IGNITE-5357 is ready for review (Replicated cache reads load balancing)

So, what's the next step? On Thu, Mar 15, 2018 at 12:27 AM, Dmitry Pavlov wrote: > Yes, I think I could move IgniteReproducingSuite to dev-utils module later. > Thank you for this idea. > > Yes, It is probably it was Queries test flaky'ness. > > I hope Vladimir, you will find some time to make qu

[jira] [Created] (IGNITE-7961) Rebalance throughput requires optimization

Ilya Lantukh created IGNITE-7961: Summary: Rebalance throughput requires optimization Key: IGNITE-7961 URL: https://issues.apache.org/jira/browse/IGNITE-7961 Project: Ignite Issue Type: Impro

[GitHub] ignite pull request #3639: IGNITE-7608

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

Re: Ignite contibutors page

I'm not mentioned on the community contributors page: https://ignite.apache.org/community/resources.html pls add me, dmitriyff (Dmitriy Shabalin) -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

readme.io weird interface element

Hi, all! Does anyone know what is this button with arrow and disk at the right corner of versions list header? [1] Seems that it does nothing. [1] https://ibb.co/eJf5uc -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-7960) Wrong type name in cache metadata on query execution

Vasiliy Sisko created IGNITE-7960: - Summary: Wrong type name in cache metadata on query execution Key: IGNITE-7960 URL: https://issues.apache.org/jira/browse/IGNITE-7960 Project: Ignite Issue

[jira] [Created] (IGNITE-7959) Deadlock at GridDhtAtomicCache.lockEntries during parallel SQL delete

Pavel Vinokurov created IGNITE-7959: --- Summary: Deadlock at GridDhtAtomicCache.lockEntries during parallel SQL delete Key: IGNITE-7959 URL: https://issues.apache.org/jira/browse/IGNITE-7959 Project:

Re: IGNITE-6879

Just found the fix is ready - I will review it today or tomorrow.

Re: IGNITE-6879

Dmitry, Roman, I can review the fix - send me a code review link when it is ready. On Wed, Mar 14, 2018 at 5:14 PM, Dmitry Pavlov wrote: > Igniters, > > it is about spring-data integration support. > > Who has intereset about styding this technology? > > Alexey Kukushkin would you like to be rev

Re: Ignite contibutors page

Dear Denis, could you please include me in list of contributors too? https://github.com/zaleslaw 2018-03-14 22:04 GMT+03:00 Denis Magda : > Turik, > > Done, you're in ;) > > On Tue, Mar 13, 2018 at 10:11 PM, techbysample wrote: > > > Denis, > > > > Please add my name as well. > > > > Best > > T

Re: Apache Ignite RPM packaging (Stage II)

*DEB package > On 15 Mar 2018, at 10:35, Petr Ivanov wrote: > > Considering that DEV package for now is almost platform independent (its a > java application more or less), that package will work almost on any > DEB-based linux, including but not limited to Ubuntu, Debian, etc. > The only res

Re: Apache Ignite RPM packaging (Stage II)

Considering that DEV package for now is almost platform independent (its a java application more or less), that package will work almost on any DEB-based linux, including but not limited to Ubuntu, Debian, etc. The only restriction is existence of systemctl (systemd) service manager — we are dep

Re: IgniteSet implementation: changes required

Dmitriy, It's technically possible to produce both kinds of sets with {{Ignite.set()}} call, but this will require to one more argument ('small' vs 'large'). Doesn't it look less inuitive than separate {{IgniteCache.asSet()}} ? And of course, we don't want to leave existing implementation broken.

Re: Atomic sequence and topology exception

Pavel, The exception from an AtomicSequence looks like a bug to me. Ignite should retry all operations that do not involve user's logic, this stands for AtomicSequence. I believe such handling already present in AtomicLong, so it should not be difficult to fix. The only case when a user must hand