[GitHub] ignite pull request #1601: Added CacheNotAvailableTest, seeing CACHE_REBALAN...

Github user sfirestone closed the pull request at: https://github.com/apache/ignite/pull/1601 --- 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

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

Updated news section on the site and tweeted about the release: https://twitter.com/ApacheIgnite/status/839208220841275392 — Denis > On Mar 6, 2017, at 4:10 PM, Denis Magda wrote: > > The Apache Ignite Community

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

Andrey, Excellent! Thanks for keeping an eye on this. Please let us know what you do the same for Zeppelin. *Raul*, *Roman*, could you update Camel and MyBatis integrations respectively? https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

JFYI Also today Vert.x 3.4.0 was released with Apache Ignite 1.9 based cluster manager for Vert.x in HA/Clustered mode. On Tue, Mar 7, 2017 at 3:10 AM, Denis Magda wrote: > The Apache Ignite Community is pleased to announce the release of Apache > Ignite 1.9.0. > > Apache

Re: Merging all network components to a single one

Personally, I’m fully for this idea. BTW, there is already a ticket for this task created by Yakov some time ago: https://issues.apache.org/jira/browse/IGNITE-3480 — Denis > On Mar 7, 2017, at 10:50 AM, Dmitriy Setrakyan

Re: Ignite 2.0 - Update Spring dependency to latest stable version

Yes, it’s planned for 2.0 release. You can assign it on yourself helping out the community to release as many improvements in 2.0 as possible. — Denis > On Mar 7, 2017, at 2:59 AM, Vyacheslav Daradur wrote: > > Hello everyone! > > There are no changes long ago: >

Re: assigning IGNITE-933

Vadim, The timeout should be such that the test completes successfully on single core machine as well as on multi-core servers. Setting timeout to 3 - 5 seconds should work. — Denis > On Mar 7, 2017, at 1:55 AM, Вадим Опольский wrote: > > Denis, > > I'm planning to

Re: IgniteSemaphore and failoverSafe flag

On Tue, Mar 7, 2017 at 1:26 AM, Alexey Goncharuk wrote: > Guys, > > I was looking at this ticket and have a question related to the lock > semantics: > > Suppose I have a node which has already acquired the lock, and then all > affinity nodes related to the lock

IGNITE-1393 - ready for review

Hello. Please, review. https://issues.apache.org/jira/browse/IGNITE-1393 [Test] AssertionError when stop node executing transaction - GridCacheStopSelfTest

[jira] [Created] (IGNITE-4798) Cluster does not finish rebalancing after nodes leaving

Semen Boikov created IGNITE-4798: Summary: Cluster does not finish rebalancing after nodes leaving Key: IGNITE-4798 URL: https://issues.apache.org/jira/browse/IGNITE-4798 Project: Ignite

[GitHub] ignite pull request #1600: Ignite 3018 fair

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1600 Ignite 3018 fair You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3018-fair Alternatively you can

[jira] [Created] (IGNITE-4797) Need to expose offheap memory allocated size metric for internal data structures

Andrey Gura created IGNITE-4797: --- Summary: Need to expose offheap memory allocated size metric for internal data structures Key: IGNITE-4797 URL: https://issues.apache.org/jira/browse/IGNITE-4797

Re: general question

I've found GridDhtCacheEntry and GridDistributedCacheEntry, so they must have been of the same logic ? пт, 3 мар. 2017 г. в 15:03, Alexander Fedotov : > Yes, DHT stands for distributed hash table. > > On Fri, Mar 3, 2017 at 3:01 PM, ALEKSEY KUZNETSOV < >

Re: PR IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

Regarding your comment in ticket. Do you mean broken factory node ought to send notifications to cache nodes through sharedCtx.io().send(...) ? пт, 3 мар. 2017 г. в 11:33, Yakov Zhdanov : > Alexey, my comments are in the ticket. Please address them. > > Thanks! > -- >

distributed transaction of non-single coordinator

Hi all! Im designing distributed transaction which can be started at one node, and continued at other one. Has anybody thoughts on it ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Maxim, all GridClockSyncProcessor related code should be remove (objects, messages, etc) On Tue, Mar 7, 2017 at 12:23 PM, Kozlov Maxim wrote: > Andrey, or better remove GridTimeSyncProcessorSelfTest class? > >> 7 марта 2017 г., в 12:21, Kozlov Maxim

Ignite 2.0 - Update Spring dependency to latest stable version

Hello everyone! There are no changes long ago: https://issues.apache.org/jira/browse/IGNITE-4211 Is it actual?

Re: Merging all network components to a single one

What tasks do discovery component responsible for ? вт, 7 мар. 2017 г. в 13:15, Yakov Zhdanov : > Guys, > > I have an idea of merging all net components to one. > > Now we have the following components interacting via network: > 1. discovery > 2. communication > 3. rest > 4.

Re: REVIEW IGNITE-2552 EvictionPolicies refactored, logic changed

Hi! I have fixed all sources. Plz, review it again пн, 6 мар. 2017 г. в 15:43, Andrey Gura : > Aleksey, thanks! > > I answered in JIRA ticket. > > On Mon, Mar 6, 2017 at 10:56 AM, ALEKSEY KUZNETSOV > wrote: > > I've fixed the comments. > >

Merging all network components to a single one

Guys, I have an idea of merging all net components to one. Now we have the following components interacting via network: 1. discovery 2. communication 3. rest 4. odbc 5. ignite-hadoop 6. time processor (being removed together with clock mode) 7. IPC communication endpoint 2-6 use GridNioServer

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Andrey, or better remove GridTimeSyncProcessorSelfTest class? > 7 марта 2017 г., в 12:21, Kozlov Maxim написал(а): > > Andrey, in GridTimeSyncProcessorSelfTest class methods: testTimeSync() and > testTimeSyncChangeCoordinator() also removed? > > >> 6 марта 2017 г., в

Re: assigning IGNITE-933

Denis, I'm planning to adjust processing time of incoming and outgoing messages by JMH benchmarks. What do you think are the parameters of commodity hardware/? RAM size? CPU speed ? or others ? Vadim 2017-03-06 22:36 GMT+03:00 Denis Magda : > Vadim, > > How do you plan to

[GitHub] ignite pull request #1599: ignite-4767

GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/1599 ignite-4767 Suppressing or logging rollback exceptions instead of hiding the origin exception You can merge this pull request into a Git repository by running: $ git pull

Re: IgniteSemaphore and failoverSafe flag

Guys, I was looking at this ticket and have a question related to the lock semantics: Suppose I have a node which has already acquired the lock, and then all affinity nodes related to the lock leave topology. In this case, if we automatically re-created the lock, we would end up having two lock