[jira] [Created] (IGNITE-4758) Introduce MemoryPolicy configuration and adapt PageMemory concept to multiple memory policies

Sergey Chugunov created IGNITE-4758: --- Summary: Introduce MemoryPolicy configuration and adapt PageMemory concept to multiple memory policies Key: IGNITE-4758 URL: https://issues.apache.org/jira/browse/IGNITE-475

IGNITE-4758 - introducing cache memory policies

Hello Ignite devs, I created new subtask under IGNITE-3477 with my vision of how *MemoryPolicy* may be implemented. In a nutshell my idea is as follows: instead of having only one instance of *

INGITE-4302 PR is ready for review

Hello Igniters, I finished my work on IGNITE-4302 *Exchange binary metadata with discovery custom messages*, pull request is open, TC results

[jira] [Created] (IGNITE-4759) Rework pug html loader to pug loader

Dmitriy Shabalin created IGNITE-4759: Summary: Rework pug html loader to pug loader Key: IGNITE-4759 URL: https://issues.apache.org/jira/browse/IGNITE-4759 Project: Ignite Issue Type: Tas

[jira] [Created] (IGNITE-4760) Hibernate L2 cache stores value in wrong cache

Semen Boikov created IGNITE-4760: Summary: Hibernate L2 cache stores value in wrong cache Key: IGNITE-4760 URL: https://issues.apache.org/jira/browse/IGNITE-4760 Project: Ignite Issue Type: B

Re: issue with Hibernate 2L cache region factory ignite-1.8

Hi, Thank you for reporting this bug, but it seems fix you suggested will not work for HibernateReadWriteAccessStrategy since single thread local is needed to use single cross-cache transaction. I created JIRA issue: https://issues.apache.org/jira/browse/IGNITE-4760. Thanks! On Sun, Feb 26, 201

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

plz review ticket again пн, 20 февр. 2017 г. в 11:14, Alexey Goncharuk : > Thanks, Aleksey, > > I will take a look this week. > > --AG > > 2017-02-20 10:25 GMT+03:00 ALEKSEY KUZNETSOV : > > > Hi! Review my PR again, plz - https://github.com/apache/ignite/pull/1517 > > > > пт, 17 февр. 2017 г. в 1

REVIEW IGNITE-2552 EvictionPolicies refactored, logic changed

Plz, review my PR : http://reviews.ignite.apache.org/ignite/review/IGNT-CR-98 or https://github.com/apache/ignite/pull/1545 -- *Best Regards,* *Kuznetsov Aleksey*

[GitHub] ignite pull request #1580: GridGain 1.9.1

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1580 GridGain 1.9.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.1 Alternatively you can review and apply th

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Valentin, Then there is no need for setting CacheConfiguration.atomicWriteOrderMode. What do you think, remove it and and related methods? > 28 февр. 2017 г., в 2:49, Valentin Kulichenko > написал(а): > > Hi Max, > > In case we remove the CLOCK mode, I think we should remove the enum too, as

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Maxim, Yes, this setting doesn't make sense anymore. So we need remove all related methods. Also there is component called GridClockSyncProcessor that also should be removed. It will lead to removing globalTime field from GridCacheVersion class and some related methods. On Tue, Feb 28, 2017 at 3

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

Alexey, Vladislav, are you agree with me, or not? I want to do it faster and move on. 2017-02-17 17:36 GMT+03:00 Александр Меньшиков : > We can check "onDone" method was called with using getState() method. If > getState()!=0 then resFlag!=0. Just look at code. > > > 2017-02-17 17:12 GMT+03:00 А

Re: IGNITE-824: [Test] GridRandomSelfTest # testPerformance was disabled.

Yakov, please look at PR. It's simple removing. 2017-02-21 19:29 GMT+03:00 Александр Меньшиков : > Done. > > PR inside: > https://issues.apache.org/jira/browse/IGNITE-824 > > > 2017-02-21 13:04 GMT+03:00 Yakov Zhdanov : > >> Alexander, you can remove the test and resolve the issue. >> >> --Yakov

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

Sorry, I mean I want to do fast work on this issue (not make code faster). Your code is strange. You can see my view in my local temp PR: https://github.com/SharplEr/ignite/pull/4/files This is what I'm meaning. I suppose "volatile" is not need here, because right now if GridFutureAdapter#onDone

[GitHub] ignite pull request #1581: IGNITE-1094 Ignite.createCache(CacheConfiguration...

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/1581 IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization You can merge this pull request into a Git repository by running: $ git pull https

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Denis, I did not get your last message. What did users expect from changing hbFreq? --Yakov 2017-02-28 4:08 GMT+03:00 Dmitriy Setrakyan : > Yakov, what do you think? > > On Mon, Feb 27, 2017 at 4:17 PM, Denis Magda wrote: > > > Frankly, I decided to initiate this discussion after talking to man

Re: IGNITE-603

Denis, I can't say for sure, but the fact test was commented out for a long time is suspicious. Alexander, can you please uncomment, fix all the compilation errors and update the ticket with test run results. Make sure you have modules/ext-data projects built and all paths mentioned in modules/cor

Re: IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

Alexander, Can you please clarify this? >I suppose "volatile" is not need here, because right now if >GridFutureAdapter#onDone() called in another thread than GridFutureAdapter#get0, it will produce AssertionError. 1) 99.999% of time GridFutureAdapter#onDone() is called in some other thread tha

[jira] [Created] (IGNITE-4761) ServiceProcessor hangs while stopping on unstable topology.

Andrew Mashenkov created IGNITE-4761: Summary: ServiceProcessor hangs while stopping on unstable topology. Key: IGNITE-4761 URL: https://issues.apache.org/jira/browse/IGNITE-4761 Project: Ignite

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

They expect exactly what the name of the TcpDiscoverySpi.heartbeatsFrequency method says - rate of heartbeats will be adjusted if you play with this parameter. However, this is not true because the frequency of heartbeats is calculated from the failure detection timeout. — Denis > On Feb 28,

Re: IGNITE-2741 - spring session design

Hi Val, Sorry for pestering, thanks for all your help. Rishi On Mon, Feb 27, 2017 at 7:22 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Rishi, > > Sorry, not yet. But this on my short list of TODOs, will try to give an > update as soon as possible. > > -Val > > On Mon, Fe

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

I had this thought when exploring this parameter at first and only was able to change my understanding when evaluating it more deeply in the source and reaching out to other users/devs. There could be an issue with new users who think increasing the hb frequency will impact inter-node failure dete

Re: Hibernate OGM for Ignite. I need a help with documentation

Hi Victor, Looks like your contribution was accepted and will be rolled out as a part of the next release: https://github.com/hibernate/hibernate-ogm/labels/Next%20release Is it so? Do you know when is the release scheduled for?

Documenting Apache Ignite 1.9 Features

Igniters, We’ve already documented most of the features and improvements except the ones below. Vovan, Igor, Alexander P., please spare some time this week preparing the docs. Once you’re done Prachi and I will do a final review. All the docs have to be ready by the time AI 1.9 gets released o

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Do we still need GridClockSyncProcessor? On Tue, Feb 28, 2017 at 5:26 AM, Andrey Gura wrote: > Maxim, > > Yes, this setting doesn't make sense anymore. So we need remove all > related methods. > > Also there is component called GridClockSyncProcessor that also should > be removed. It will lead t

Re: IGNITE-4758 - introducing cache memory policies

Thanks Sergey! Just to confirm, the same memory policy could be shared between different caches, right? D. On Tue, Feb 28, 2017 at 1:28 AM, Sergey Chugunov wrote: > Hello Ignite devs, > > I created new subtask > under IGNITE-3477

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

No, it should be removed. If somebody use entry last update time (e.g. for conflict resolving) they should store this time as entry field. On Wed, Mar 1, 2017 at 12:57 AM, Dmitriy Setrakyan wrote: > Do we still need GridClockSyncProcessor? > > On Tue, Feb 28, 2017 at 5:26 AM, Andrey Gura wrote:

[jira] [Created] (IGNITE-4762) Support transactional updates in JDBC driver

Valentin Kulichenko created IGNITE-4762: --- Summary: Support transactional updates in JDBC driver Key: IGNITE-4762 URL: https://issues.apache.org/jira/browse/IGNITE-4762 Project: Ignite I

[jira] [Created] (IGNITE-4763) Implement doSetRollbackOnly method to be implemented in SpringTransactionManager

Sumanta Ghosh created IGNITE-4763: - Summary: Implement doSetRollbackOnly method to be implemented in SpringTransactionManager Key: IGNITE-4763 URL: https://issues.apache.org/jira/browse/IGNITE-4763 Pr

[VOTE] Apache Ignite 1.9.0 RC1

Dear Sirs! We have uploaded the 1.9.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/1.9.0-rc1/ Git tag name is 1.9.0-rc1 This release includes the following changes: Ignite: * Added Data streamer mode for DML * Added Discovery SPI Implementation for Ignite Kubernetes Pods *

Re: IGNITE-4758 - introducing cache memory policies

Dmitriy, Correct, cache configuration may contain a name of memory policy to use for this cache. If memory policy is not specified, a default one is used. Thanks, Sergey. On Wed, Mar 1, 2017 at 1:02 AM, Dmitriy Setrakyan wrote: > Thanks Sergey! > > Just to confirm, the same memory policy could

Re: [VOTE] Apache Ignite 1.9.0 RC1

+1 2017-03-01 10:28 GMT+03:00 Anton Vinogradov : > Dear Sirs! > > We have uploaded the 1.9.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/1.9.0-rc1/ > > Git tag name is > 1.9.0-rc1 > > This release includes the following changes: > > Ignite: > * Added Data streamer mode fo