You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Yakov Zhdanov <yz...@apache.org> on 2015/11/02 14:35:48 UTC
Ignite-1.5 Release
Guys,
I think we can start preparation to Ignite-1.5 release which will include
many interesting features:
1. Portable object API
https://issues.apache.org/jira/browse/IGNITE-1486
2. Ignite.NET and Ignite C++
https://issues.apache.org/jira/browse/IGNITE-1282
3. Optimistic serializable transactions
https://issues.apache.org/jira/browse/IGNITE-1607
4. Distributed SQL joins - we will be able to query non-collocated data as
well
https://issues.apache.org/jira/browse/IGNITE-1232
5. Enhanced Oracle and IBM JDK interoperability
https://issues.apache.org/jira/browse/IGNITE-1526
6. MQTT streamer
https://issues.apache.org/jira/browse/IGNITE-535
7. Continuous query failover
https://issues.apache.org/jira/browse/IGNITE-426
8. Significant transactional cache performance optimizations - I will merge
these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
9. Many stability and fault-tolerance fixes.
10. I would also like to include distributed Semaphore. Vladislav, any
chance you can finish with it this week?
https://issues.apache.org/jira/browse/IGNITE-
<https://issues.apache.org/jira/browse/IGNITE-426>638
Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
please respond to this email and let us know when can we expect your
changes being merged to master and release branch?
Can someone create ignite-1.5 release branch?
--Yakov
Re: Ignite-1.5 Release
Posted by Denis Magda <dm...@gridgain.com>.
On 11/17/2015 9:37 PM, Yakov Zhdanov wrote:
> 1. Understood
> 2. Well, I understand that object gets deserialized on get from cache and
> this most probably should not cause any issue. However, code does not look
> healthy and someone may think that there is an issue - field is not
> volatile, initialized in constructor, has sync setter, but is accessed
> several times in code outside of sync. Can you please refactor this?
> 3. Yes, Denis is looking into this. And I think your issue will be fixed in
> the scope of Denis one.
I'm afraid that my changes won't fix the issue in Vladislav's
implementation.
However, when my changes are merged we will be able to rework these
semaphore failover tests and fix any issue in the semaphore impl related
to failover. I can take care of this.
--
Denis
>
> Vlad, can you please refactor [2] and I will pick it up and merge tomorrow.
>
> Thank you for your interest and contribution!
>
> --Yakov
>
> 2015-11-17 21:30 GMT+04:00 Vladisav Jelisavcic <vl...@gmail.com>:
>
>> Hi Yakov,
>> 1. Yes
>>
>> 2. if you mean that nodeMap is accessed in onNodeRemoved(UUID nodeID)
>> method of the GridCacheSemaphoreImpl class,
>> it shouldn't be a problem, but it can be changed easily not to do so;
>>
>> 3.
>>
>> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantTopologyChangeFailoverSafe()
>>
>> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantMultipleTopologyChangeFailoverSafe()
>>
>> I think the problem is with the atomicity of the simulated grid failure;
>> once stopGrid() is called for a node, other threads on this same node start
>> throwing interrupted exceptions,
>> which are in turn not handled properly in the
>> GridCacheAbstractDataStructuresFailoverSelfTest;
>> Those exceptions shouldn't be dealt with inside the GridCacheSemaphoreImpl
>> itself.
>> In a realworld node failure scenario, all those threads would fail at the
>> same time
>> (none of them would influence the rest of the grid anymore);
>>
>> I think fixing the issue Denis is working on can fix this (IGNITE-801 and
>> IGNITE-803)
>> Am i right? Does it makes sense?
>>
>>
>> Best regards,
>> Vladisav
>>
>>
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
1. Understood
2. Well, I understand that object gets deserialized on get from cache and
this most probably should not cause any issue. However, code does not look
healthy and someone may think that there is an issue - field is not
volatile, initialized in constructor, has sync setter, but is accessed
several times in code outside of sync. Can you please refactor this?
3. Yes, Denis is looking into this. And I think your issue will be fixed in
the scope of Denis one.
Vlad, can you please refactor [2] and I will pick it up and merge tomorrow.
Thank you for your interest and contribution!
--Yakov
2015-11-17 21:30 GMT+04:00 Vladisav Jelisavcic <vl...@gmail.com>:
> Hi Yakov,
> 1. Yes
>
> 2. if you mean that nodeMap is accessed in onNodeRemoved(UUID nodeID)
> method of the GridCacheSemaphoreImpl class,
> it shouldn't be a problem, but it can be changed easily not to do so;
>
> 3.
>
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantTopologyChangeFailoverSafe()
>
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantMultipleTopologyChangeFailoverSafe()
>
> I think the problem is with the atomicity of the simulated grid failure;
> once stopGrid() is called for a node, other threads on this same node start
> throwing interrupted exceptions,
> which are in turn not handled properly in the
> GridCacheAbstractDataStructuresFailoverSelfTest;
> Those exceptions shouldn't be dealt with inside the GridCacheSemaphoreImpl
> itself.
> In a realworld node failure scenario, all those threads would fail at the
> same time
> (none of them would influence the rest of the grid anymore);
>
> I think fixing the issue Denis is working on can fix this (IGNITE-801 and
> IGNITE-803)
> Am i right? Does it makes sense?
>
>
> Best regards,
> Vladisav
>
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
I meant "release branch", not "master".
On Tue, Nov 17, 2015 at 9:25 PM, Vladimir Ozerov <vo...@gridgain.com>
wrote:
> Folks,
>
> I continue working on IGNITE-1917 - marshalling microoptimizations. I did
> a bunch of things today which increased performance a bit, so that
> unmarshalling with PortableMarshaller is now a bit faster than
> OptimizedMarshaller when object has several fields, but still slower when
> there are lots of small fields.
>
> I'm going to apply the last easy optimization in the nearest time and then
> will focus on merging all pending tickets to master. Once all important
> things are merged, I'm going to spend some more efforts on performance
> again.
>
> On Tue, Nov 17, 2015 at 8:30 PM, Vladisav Jelisavcic <vl...@gmail.com>
> wrote:
>
>> Hi Yakov,
>> 1. Yes
>>
>> 2. if you mean that nodeMap is accessed in onNodeRemoved(UUID nodeID)
>> method of the GridCacheSemaphoreImpl class,
>> it shouldn't be a problem, but it can be changed easily not to do so;
>>
>> 3.
>>
>> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantTopologyChangeFailoverSafe()
>>
>> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantMultipleTopologyChangeFailoverSafe()
>>
>> I think the problem is with the atomicity of the simulated grid failure;
>> once stopGrid() is called for a node, other threads on this same node
>> start
>> throwing interrupted exceptions,
>> which are in turn not handled properly in the
>> GridCacheAbstractDataStructuresFailoverSelfTest;
>> Those exceptions shouldn't be dealt with inside the GridCacheSemaphoreImpl
>> itself.
>> In a realworld node failure scenario, all those threads would fail at the
>> same time
>> (none of them would influence the rest of the grid anymore);
>>
>> I think fixing the issue Denis is working on can fix this (IGNITE-801 and
>> IGNITE-803)
>> Am i right? Does it makes sense?
>>
>>
>> Best regards,
>> Vladisav
>>
>>
>>
>>
>> On Tue, Nov 17, 2015 at 5:40 PM, Yakov Zhdanov <yz...@apache.org>
>> wrote:
>>
>> > Vladislav,
>> >
>> > I started to review the latest changes and have couple of questions:
>> >
>> > 1. latest changes are here - https://github.com/apache/ignite/pull/120?
>> Is
>> > that correct?
>> > 2.
>> >
>> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.Sync#nodeMap
>> > is accessed in both sync and unsync context. Are you sure this is fine.
>> > 3. As far as failing test - can you please isolate it into separate
>> junit
>> > or point out existing one?
>> >
>> > --Yakov
>> >
>> > 2015-11-11 12:33 GMT+03:00 Vladisav Jelisavcic <vl...@gmail.com>:
>> >
>> > > Yakov,
>> > >
>> > > sorry for running a bit late.
>> > >
>> > > > Vladislav, do you have any updates for
>> > > > https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
>> > > >
>> > > > --Yakov
>> > >
>> > > I have problems with some fail-over scenarios;
>> > > It seems that if the two nodes are in the middle of acquiring or
>> > releasing
>> > > the semaphore,
>> > > and one of them fails, all nodes get:
>> > >
>> > > [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
>> > > <ignite-atomics-sys-cache> Failed to compare and set:
>> > >
>> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
>> > > class
>> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
>> > > Failed to acquire lock for keys (primary node left grid, retry
>> > transaction
>> > > if possible) [keys=[UserKeyCacheObjectImpl
>> [val=GridCacheInternalKeyImpl
>> > > [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
>> > > node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
>> > > ...
>> > > Caused by: class
>> > > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
>> > Failed
>> > > to acquire lock for keys (primary node left grid, retry transaction if
>> > > possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
>> > > [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
>> > > node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
>> > > at
>> > >
>> > >
>> >
>> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
>> > > ... 10 more
>> > >
>> > >
>> > > I'm still trying to find out how to exactly reproduce this behavior,
>> > > I'll send you more details once I try few more things.
>> > >
>> > > I am still using partitioned cache, does it make sense to use
>> replicated
>> > > cache instead?
>> > >
>> > >
>> > > Other than that, I'm done with everything else.
>> > >
>> > > Thanks,
>> > > Vladisav
>> > >
>> > >
>> >
>>
>
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Folks,
I continue working on IGNITE-1917 - marshalling microoptimizations. I did a
bunch of things today which increased performance a bit, so that
unmarshalling with PortableMarshaller is now a bit faster than
OptimizedMarshaller when object has several fields, but still slower when
there are lots of small fields.
I'm going to apply the last easy optimization in the nearest time and then
will focus on merging all pending tickets to master. Once all important
things are merged, I'm going to spend some more efforts on performance
again.
On Tue, Nov 17, 2015 at 8:30 PM, Vladisav Jelisavcic <vl...@gmail.com>
wrote:
> Hi Yakov,
> 1. Yes
>
> 2. if you mean that nodeMap is accessed in onNodeRemoved(UUID nodeID)
> method of the GridCacheSemaphoreImpl class,
> it shouldn't be a problem, but it can be changed easily not to do so;
>
> 3.
>
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantTopologyChangeFailoverSafe()
>
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantMultipleTopologyChangeFailoverSafe()
>
> I think the problem is with the atomicity of the simulated grid failure;
> once stopGrid() is called for a node, other threads on this same node start
> throwing interrupted exceptions,
> which are in turn not handled properly in the
> GridCacheAbstractDataStructuresFailoverSelfTest;
> Those exceptions shouldn't be dealt with inside the GridCacheSemaphoreImpl
> itself.
> In a realworld node failure scenario, all those threads would fail at the
> same time
> (none of them would influence the rest of the grid anymore);
>
> I think fixing the issue Denis is working on can fix this (IGNITE-801 and
> IGNITE-803)
> Am i right? Does it makes sense?
>
>
> Best regards,
> Vladisav
>
>
>
>
> On Tue, Nov 17, 2015 at 5:40 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Vladislav,
> >
> > I started to review the latest changes and have couple of questions:
> >
> > 1. latest changes are here - https://github.com/apache/ignite/pull/120?
> Is
> > that correct?
> > 2.
> >
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.Sync#nodeMap
> > is accessed in both sync and unsync context. Are you sure this is fine.
> > 3. As far as failing test - can you please isolate it into separate junit
> > or point out existing one?
> >
> > --Yakov
> >
> > 2015-11-11 12:33 GMT+03:00 Vladisav Jelisavcic <vl...@gmail.com>:
> >
> > > Yakov,
> > >
> > > sorry for running a bit late.
> > >
> > > > Vladislav, do you have any updates for
> > > > https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
> > > >
> > > > --Yakov
> > >
> > > I have problems with some fail-over scenarios;
> > > It seems that if the two nodes are in the middle of acquiring or
> > releasing
> > > the semaphore,
> > > and one of them fails, all nodes get:
> > >
> > > [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> > > <ignite-atomics-sys-cache> Failed to compare and set:
> > >
> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> > > class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > Failed to acquire lock for keys (primary node left grid, retry
> > transaction
> > > if possible) [keys=[UserKeyCacheObjectImpl
> [val=GridCacheInternalKeyImpl
> > > [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > > node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > ...
> > > Caused by: class
> > > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > Failed
> > > to acquire lock for keys (primary node left grid, retry transaction if
> > > possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> > > [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > > node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> > > ... 10 more
> > >
> > >
> > > I'm still trying to find out how to exactly reproduce this behavior,
> > > I'll send you more details once I try few more things.
> > >
> > > I am still using partitioned cache, does it make sense to use
> replicated
> > > cache instead?
> > >
> > >
> > > Other than that, I'm done with everything else.
> > >
> > > Thanks,
> > > Vladisav
> > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Vladisav Jelisavcic <vl...@gmail.com>.
Hi Yakov,
1. Yes
2. if you mean that nodeMap is accessed in onNodeRemoved(UUID nodeID)
method of the GridCacheSemaphoreImpl class,
it shouldn't be a problem, but it can be changed easily not to do so;
3.
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantTopologyChangeFailoverSafe()
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantMultipleTopologyChangeFailoverSafe()
I think the problem is with the atomicity of the simulated grid failure;
once stopGrid() is called for a node, other threads on this same node start
throwing interrupted exceptions,
which are in turn not handled properly in the
GridCacheAbstractDataStructuresFailoverSelfTest;
Those exceptions shouldn't be dealt with inside the GridCacheSemaphoreImpl
itself.
In a realworld node failure scenario, all those threads would fail at the
same time
(none of them would influence the rest of the grid anymore);
I think fixing the issue Denis is working on can fix this (IGNITE-801 and
IGNITE-803)
Am i right? Does it makes sense?
Best regards,
Vladisav
On Tue, Nov 17, 2015 at 5:40 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Vladislav,
>
> I started to review the latest changes and have couple of questions:
>
> 1. latest changes are here - https://github.com/apache/ignite/pull/120? Is
> that correct?
> 2.
> org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.Sync#nodeMap
> is accessed in both sync and unsync context. Are you sure this is fine.
> 3. As far as failing test - can you please isolate it into separate junit
> or point out existing one?
>
> --Yakov
>
> 2015-11-11 12:33 GMT+03:00 Vladisav Jelisavcic <vl...@gmail.com>:
>
> > Yakov,
> >
> > sorry for running a bit late.
> >
> > > Vladislav, do you have any updates for
> > > https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
> > >
> > > --Yakov
> >
> > I have problems with some fail-over scenarios;
> > It seems that if the two nodes are in the middle of acquiring or
> releasing
> > the semaphore,
> > and one of them fails, all nodes get:
> >
> > [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> > <ignite-atomics-sys-cache> Failed to compare and set:
> > o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> > class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > Failed to acquire lock for keys (primary node left grid, retry
> transaction
> > if possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> > [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > ...
> > Caused by: class
> > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> Failed
> > to acquire lock for keys (primary node left grid, retry transaction if
> > possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> > [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> > ... 10 more
> >
> >
> > I'm still trying to find out how to exactly reproduce this behavior,
> > I'll send you more details once I try few more things.
> >
> > I am still using partitioned cache, does it make sense to use replicated
> > cache instead?
> >
> >
> > Other than that, I'm done with everything else.
> >
> > Thanks,
> > Vladisav
> >
> >
>
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Vladislav,
I started to review the latest changes and have couple of questions:
1. latest changes are here - https://github.com/apache/ignite/pull/120? Is
that correct?
2. org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.Sync#nodeMap
is accessed in both sync and unsync context. Are you sure this is fine.
3. As far as failing test - can you please isolate it into separate junit
or point out existing one?
--Yakov
2015-11-11 12:33 GMT+03:00 Vladisav Jelisavcic <vl...@gmail.com>:
> Yakov,
>
> sorry for running a bit late.
>
> > Vladislav, do you have any updates for
> > https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
> >
> > --Yakov
>
> I have problems with some fail-over scenarios;
> It seems that if the two nodes are in the middle of acquiring or releasing
> the semaphore,
> and one of them fails, all nodes get:
>
> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> <ignite-atomics-sys-cache> Failed to compare and set:
> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> Failed to acquire lock for keys (primary node left grid, retry transaction
> if possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> ...
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed
> to acquire lock for keys (primary node left grid, retry transaction if
> possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> ... 10 more
>
>
> I'm still trying to find out how to exactly reproduce this behavior,
> I'll send you more details once I try few more things.
>
> I am still using partitioned cache, does it make sense to use replicated
> cache instead?
>
>
> Other than that, I'm done with everything else.
>
> Thanks,
> Vladisav
>
>
Re: Ignite-1.5 Release
Posted by Valentin Kulichenko <va...@gmail.com>.
Folks,
I made several enhancements in our direct marshalling protocol that will
reduce the amount of data transferred over the network. There are two main
changes:
- Optimized encoding of integers and longs. Now small numbers (0-127)
consume only one byte instead of four, greater number can consume 2, 3 or
more bytes (as many as needed only).
- Null objects are always written as one byte.
Additionally there are several fixes that should reduce the number of
created object during marshalling/unmarshalling.
I ran a simple test with tx puts and amount of bytes sent over the network
is around 1.5 times less than in current ignite-1.5.
Yakov, Alex, can you please review my changes in ignite-direct-marsh-opt
branch and check the performance?
-Val
On Mon, Nov 16, 2015 at 2:04 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> Would be nice to get an up to date picture. At this point this thread has
> gotten unwieldy.
>
> Yakov, would it be worthwhile start a new thread will all the tasks listed
> again?
>
> D.
>
> On Mon, Nov 16, 2015 at 1:55 PM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
> > Igniters,
> >
> > I am finalizing my optimizations in tx cache (currently there are a
> couple
> > of failing tests on CI), I am expecting these changes to be merged in
> > ignite-1.5 branch tomorrow.
> >
> > 2015-11-16 19:23 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:
> >
> > > Guys,
> > >
> > > Can everyone provide updates on ongoing issues status?
> > >
> > > Vlad, I will review Semaphore tomorrow (Russian time).
> > >
> > > Thanks!
> > >
> > > --Yakov
> > >
> > > 2015-11-14 15:38 GMT+03:00 Denis Magda <dm...@gridgain.com>:
> > >
> > > > Hi Vladislav,
> > > >
> > > > Most likely there is a minor issue in your test.
> > > >
> > > > I think Yakov would be able to run and check the test as a part of
> the
> > > > ongoing review.
> > > >
> > > > Thanks,
> > > >
> > > > Denis
> > > >
> > > > On Friday, November 13, 2015, Vladisav Jelisavcic <
> vladisavj@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Hi Denis,
> > > > >
> > > > > Thanks a lot, it looks like my test setup was wrong,
> > > > > I added semaphore tests to
> > > > GridCacheAbstractDataStructuresFailoverSelfTest
> > > > > suite.
> > > > > Now I have following problem:
> > > > > when I run tests with TOP_CHANGE_THREAD_CNT = 3
> > > > > tests fail when they reach stop() with the following exception:
> > > > >
> > > > > class org.apache.ignite.internal.IgniteInterruptedCheckedException:
> > > Node
> > > > is
> > > > > stopping: 09c5e8b8-8998-468e-960d-223220354fd3
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStop0(GridCachePartitionExchangeManager.java:382)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:113)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:946)
> > > > > at
> > > org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1823)
> > > > > at
> > org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1769)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2133)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2096)
> > > > > at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:314)
> > > > > at org.apache.ignite.Ignition.stop(Ignition.java:223)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:802)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:784)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.access$500(GridCacheAbstractDataStructuresFailoverSelfTest.java:54)
> > > > > at
> > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest$5.apply(GridCacheAbstractDataStructuresFailoverSelfTest.java:459)
> > > > >
> > > > > When I run tests with TOP_CHANGE_THEAD_CNT = 1
> > > > > everything is running ok;
> > > > >
> > > > >
> > > > > @Yakov
> > > > > I made a new commit to my IGNITE-638 branch,
> > > > > can you please take a look?
> > > > >
> > > > >
> > > > >
> > > > > Best regards,
> > > > > Vladisav
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <
> dmagda@gridgain.com
> > > > > <javascript:;>> wrote:
> > > > > >
> > > > > > > Hi Vladislav,
> > > > > > >
> > > > > > > Please see below..
> > > > > > >
> > > > > > >
> > > > > > > On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> > > > > > >
> > > > > > >> Yakov,
> > > > > > >>
> > > > > > >> sorry for running a bit late.
> > > > > > >>
> > > > > > >> Vladislav, do you have any updates for
> > > > > > >>> https://issues.apache.org/jira/browse/IGNITE-638? Or any
> > > > questions?
> > > > > > >>>
> > > > > > >>> --Yakov
> > > > > > >>>
> > > > > > >> I have problems with some fail-over scenarios;
> > > > > > >> It seems that if the two nodes are in the middle of acquiring
> or
> > > > > > releasing
> > > > > > >> the semaphore,
> > > > > > >> and one of them fails, all nodes get:
> > > > > > >>
> > > > > > >>
> > > [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> > > > > > >> <ignite-atomics-sys-cache> Failed to compare and set:
> > > > > > >>
> > > > >
> > >
> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> > > > > > >> class
> > > > > >
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > > > > >> Failed to acquire lock for keys (primary node left grid, retry
> > > > > > transaction
> > > > > > >> if possible) [keys=[UserKeyCacheObjectImpl
> > > > > [val=GridCacheInternalKeyImpl
> > > > > > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a],
> hasValBytes=true]],
> > > > > > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > > > > >> ...
> > > > > > >> Caused by: class
> > > > > > >>
> > > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > > > > Failed
> > > > > > >> to acquire lock for keys (primary node left grid, retry
> > > transaction
> > > > if
> > > > > > >> possible) [keys=[UserKeyCacheObjectImpl
> > > > [val=GridCacheInternalKeyImpl
> > > > > > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a],
> hasValBytes=true]],
> > > > > > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > > > > >> at
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> > > > > > >> ... 10 more
> > > > > > >>
> > > > > > > You have to process this exception manually at your
> > implementation
> > > > > layer
> > > > > > > since your data structure uses a transactional cache.
> > > > > > > Below is a kind of template I used when it was required to
> > process
> > > > this
> > > > > > > and some other exeptions. You can use it as-is.
> > > > > > >
> > > > > > > int retries = GridCacheAdapter.MAX_RETRIES;
> > > > > > >
> > > > > > > IgniteCheckedException err =null;
> > > > > > >
> > > > > > > for (int i =0; i < retries; i++) {
> > > > > > > try {
> > > > > > > //Your transactional code that may fail
> > > > > > > }
> > > > > > > catch (IgniteCheckedException e) {
> > > > > > > if (i == retries)
> > > > > > > throw e;
> > > > > > >
> > > > > > > if (X.hasCause(e,
> > ClusterTopologyCheckedException.class)) {
> > > > > > > ClusterTopologyCheckedException topErr =
> > > > > > > e.getCause(ClusterTopologyCheckedException.class);
> > > > > > >
> > > > > > > topErr.retryReadyFuture().get();
> > > > > > > }
> > > > > > > else if (X.hasCause(e,
> > > > IgniteTxRollbackCheckedException.class))
> > > > > > > U.sleep(1);
> > > > > > > else throw e;
> > > > > > > }
> > > > > > > }
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >> I'm still trying to find out how to exactly reproduce this
> > > behavior,
> > > > > > >> I'll send you more details once I try few more things.
> > > > > > >>
> > > > > > > There is the test suite called
> > > > > > > GridCacheAbstractDataStructuresFailoverSelfTest that checks
> > Ignite
> > > > > > atomics
> > > > > > > and data structures with fail-over scenario.
> > > > > > > The suite will let you reproduce
> ClusterTopologyCheckedException
> > > > > easily.
> > > > > > > Just add your tests there referring to the tests of other data
> > > > > > structures.
> > > > > > >
> > > > > > > Presently I'm improving this test suite under my work on
> > IGNITE-801
> > > > and
> > > > > > > IGNITE-803. If you finish your task earlier then I'll adopt
> your
> > > > tests
> > > > > > to a
> > > > > > > new test approach.
> > > > > > >
> > > > > > >
> > > > > > >> I am still using partitioned cache, does it make sense to use
> > > > > replicated
> > > > > > >> cache instead?
> > > > > > >>
> > > > > > >> Yeah, you should support this as well. Cache mode for the data
> > > > > > structures
> > > > > > > is changed using CollectionConfigurations while for atomics
> using
> > > > > > > AtomicsConfiguration.
> > > > > > >
> > > > > > > --
> > > > > > > Denis
> > > > > > >
> > > > > > >
> > > > > > > Other than that, I'm done with everything else.
> > > > > > >>
> > > > > > >> Thanks,
> > > > > > >> Vladisav
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <
> > raulk@apache.org
> > > > > <javascript:;>>
> > > > > > wrote:
> > > > > > >>
> > > > > > >> Sorry I haven't made an appearance in this thread yet.
> > > > > > >>>
> > > > > > >>> 6. MQTT streamer
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > >>>>
> > > > > > >>> Yes, it was merged to master before the ignite-1.5 was
> created.
> > > > > > >>>
> > > > > > >>> I'd like to add:
> > > > > > >>>
> > > > > > >>> Camel Streamer =>
> > > > https://issues.apache.org/jira/browse/IGNITE-1790
> > > > > > >>> -- I'll merge this as soon as I finished with the OSGi
> tickets
> > > with
> > > > > > >>> demand.
> > > > > > >>>
> > > > > > >>> OSGi Manifests, Karaf features and possible ClassLoaderCodec
> > SPI
> > > > (or
> > > > > > >>> whatever agreement we arrive to in mailing lists and Wiki)
> > > > > > >>> -- https://issues.apache.org/jira/browse/IGNITE-1527
> > > > > > >>> -- https://issues.apache.org/jira/browse/IGNITE-1877
> > > > > > >>> -- I'm working actively on these two features.
> > > > > > >>>
> > > > > > >>> *Raúl Kripalani*
> > > > > > >>> PMC & Committer @ Apache Ignite, Apache Camel | Integration,
> > Big
> > > > Data
> > > > > > and
> > > > > > >>> Messaging Engineer
> > > > > > >>> http://about.me/raulkripalani |
> > > > > > http://www.linkedin.com/in/raulkripalani
> > > > > > >>> http://blog.raulkr.net | twitter: @raulvk
> > > > > > >>>
> > > > > > >>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <
> > > yzhdanov@apache.org
> > > > > <javascript:;>>
> > > > > > >>> wrote:
> > > > > > >>>
> > > > > > >>> Guys,
> > > > > > >>>>
> > > > > > >>>> I think we can start preparation to Ignite-1.5 release which
> > > will
> > > > > > >>>> include
> > > > > > >>>> many interesting features:
> > > > > > >>>>
> > > > > > >>>> 1. Portable object API
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > >>>>
> > > > > > >>>> 2. Ignite.NET and Ignite C++
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > >>>>
> > > > > > >>>> 3. Optimistic serializable transactions
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > >>>>
> > > > > > >>>> 4. Distributed SQL joins - we will be able to query
> > > non-collocated
> > > > > > data
> > > > > > >>>>
> > > > > > >>> as
> > > > > > >>>
> > > > > > >>>> well
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > >>>>
> > > > > > >>>> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > >>>>
> > > > > > >>>> 6. MQTT streamer
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > >>>>
> > > > > > >>>> 7. Continuous query failover
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > >>>>
> > > > > > >>>> 8. Significant transactional cache performance optimizations
> > - I
> > > > > will
> > > > > > >>>>
> > > > > > >>> merge
> > > > > > >>>
> > > > > > >>>> these changes from 'ignite-1.4-slow-server-debug' today or
> > > > tomorrow.
> > > > > > >>>>
> > > > > > >>>> 9. Many stability and fault-tolerance fixes.
> > > > > > >>>>
> > > > > > >>>> 10. I would also like to include distributed Semaphore.
> > > Vladislav,
> > > > > any
> > > > > > >>>> chance you can finish with it this week?
> > > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > >>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > >>>>
> > > > > > >>>> Thanks to everyone involved! Guys, esp. assignees of
> mentioned
> > > > > issues,
> > > > > > >>>> please respond to this email and let us know when can we
> > expect
> > > > your
> > > > > > >>>> changes being merged to master and release branch?
> > > > > > >>>>
> > > > > > >>>> Can someone create ignite-1.5 release branch?
> > > > > > >>>>
> > > > > > >>>> --Yakov
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Would be nice to get an up to date picture. At this point this thread has
gotten unwieldy.
Yakov, would it be worthwhile start a new thread will all the tasks listed
again?
D.
On Mon, Nov 16, 2015 at 1:55 PM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Igniters,
>
> I am finalizing my optimizations in tx cache (currently there are a couple
> of failing tests on CI), I am expecting these changes to be merged in
> ignite-1.5 branch tomorrow.
>
> 2015-11-16 19:23 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:
>
> > Guys,
> >
> > Can everyone provide updates on ongoing issues status?
> >
> > Vlad, I will review Semaphore tomorrow (Russian time).
> >
> > Thanks!
> >
> > --Yakov
> >
> > 2015-11-14 15:38 GMT+03:00 Denis Magda <dm...@gridgain.com>:
> >
> > > Hi Vladislav,
> > >
> > > Most likely there is a minor issue in your test.
> > >
> > > I think Yakov would be able to run and check the test as a part of the
> > > ongoing review.
> > >
> > > Thanks,
> > >
> > > Denis
> > >
> > > On Friday, November 13, 2015, Vladisav Jelisavcic <vladisavj@gmail.com
> >
> > > wrote:
> > >
> > > > Hi Denis,
> > > >
> > > > Thanks a lot, it looks like my test setup was wrong,
> > > > I added semaphore tests to
> > > GridCacheAbstractDataStructuresFailoverSelfTest
> > > > suite.
> > > > Now I have following problem:
> > > > when I run tests with TOP_CHANGE_THREAD_CNT = 3
> > > > tests fail when they reach stop() with the following exception:
> > > >
> > > > class org.apache.ignite.internal.IgniteInterruptedCheckedException:
> > Node
> > > is
> > > > stopping: 09c5e8b8-8998-468e-960d-223220354fd3
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStop0(GridCachePartitionExchangeManager.java:382)
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:113)
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:946)
> > > > at
> > org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1823)
> > > > at
> org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1769)
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2133)
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2096)
> > > > at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:314)
> > > > at org.apache.ignite.Ignition.stop(Ignition.java:223)
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:802)
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:784)
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.access$500(GridCacheAbstractDataStructuresFailoverSelfTest.java:54)
> > > > at
> > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest$5.apply(GridCacheAbstractDataStructuresFailoverSelfTest.java:459)
> > > >
> > > > When I run tests with TOP_CHANGE_THEAD_CNT = 1
> > > > everything is running ok;
> > > >
> > > >
> > > > @Yakov
> > > > I made a new commit to my IGNITE-638 branch,
> > > > can you please take a look?
> > > >
> > > >
> > > >
> > > > Best regards,
> > > > Vladisav
> > > >
> > > >
> > > >
> > > >
> > > > > On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <dmagda@gridgain.com
> > > > <javascript:;>> wrote:
> > > > >
> > > > > > Hi Vladislav,
> > > > > >
> > > > > > Please see below..
> > > > > >
> > > > > >
> > > > > > On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> > > > > >
> > > > > >> Yakov,
> > > > > >>
> > > > > >> sorry for running a bit late.
> > > > > >>
> > > > > >> Vladislav, do you have any updates for
> > > > > >>> https://issues.apache.org/jira/browse/IGNITE-638? Or any
> > > questions?
> > > > > >>>
> > > > > >>> --Yakov
> > > > > >>>
> > > > > >> I have problems with some fail-over scenarios;
> > > > > >> It seems that if the two nodes are in the middle of acquiring or
> > > > > releasing
> > > > > >> the semaphore,
> > > > > >> and one of them fails, all nodes get:
> > > > > >>
> > > > > >>
> > [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> > > > > >> <ignite-atomics-sys-cache> Failed to compare and set:
> > > > > >>
> > > >
> > o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> > > > > >> class
> > > > > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > > > >> Failed to acquire lock for keys (primary node left grid, retry
> > > > > transaction
> > > > > >> if possible) [keys=[UserKeyCacheObjectImpl
> > > > [val=GridCacheInternalKeyImpl
> > > > > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > > > > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > > > >> ...
> > > > > >> Caused by: class
> > > > > >>
> > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > > > Failed
> > > > > >> to acquire lock for keys (primary node left grid, retry
> > transaction
> > > if
> > > > > >> possible) [keys=[UserKeyCacheObjectImpl
> > > [val=GridCacheInternalKeyImpl
> > > > > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > > > > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > > > >> at
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> > > > > >> ... 10 more
> > > > > >>
> > > > > > You have to process this exception manually at your
> implementation
> > > > layer
> > > > > > since your data structure uses a transactional cache.
> > > > > > Below is a kind of template I used when it was required to
> process
> > > this
> > > > > > and some other exeptions. You can use it as-is.
> > > > > >
> > > > > > int retries = GridCacheAdapter.MAX_RETRIES;
> > > > > >
> > > > > > IgniteCheckedException err =null;
> > > > > >
> > > > > > for (int i =0; i < retries; i++) {
> > > > > > try {
> > > > > > //Your transactional code that may fail
> > > > > > }
> > > > > > catch (IgniteCheckedException e) {
> > > > > > if (i == retries)
> > > > > > throw e;
> > > > > >
> > > > > > if (X.hasCause(e,
> ClusterTopologyCheckedException.class)) {
> > > > > > ClusterTopologyCheckedException topErr =
> > > > > > e.getCause(ClusterTopologyCheckedException.class);
> > > > > >
> > > > > > topErr.retryReadyFuture().get();
> > > > > > }
> > > > > > else if (X.hasCause(e,
> > > IgniteTxRollbackCheckedException.class))
> > > > > > U.sleep(1);
> > > > > > else throw e;
> > > > > > }
> > > > > > }
> > > > > >
> > > > > >
> > > > > >
> > > > > >> I'm still trying to find out how to exactly reproduce this
> > behavior,
> > > > > >> I'll send you more details once I try few more things.
> > > > > >>
> > > > > > There is the test suite called
> > > > > > GridCacheAbstractDataStructuresFailoverSelfTest that checks
> Ignite
> > > > > atomics
> > > > > > and data structures with fail-over scenario.
> > > > > > The suite will let you reproduce ClusterTopologyCheckedException
> > > > easily.
> > > > > > Just add your tests there referring to the tests of other data
> > > > > structures.
> > > > > >
> > > > > > Presently I'm improving this test suite under my work on
> IGNITE-801
> > > and
> > > > > > IGNITE-803. If you finish your task earlier then I'll adopt your
> > > tests
> > > > > to a
> > > > > > new test approach.
> > > > > >
> > > > > >
> > > > > >> I am still using partitioned cache, does it make sense to use
> > > > replicated
> > > > > >> cache instead?
> > > > > >>
> > > > > >> Yeah, you should support this as well. Cache mode for the data
> > > > > structures
> > > > > > is changed using CollectionConfigurations while for atomics using
> > > > > > AtomicsConfiguration.
> > > > > >
> > > > > > --
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > > Other than that, I'm done with everything else.
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Vladisav
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <
> raulk@apache.org
> > > > <javascript:;>>
> > > > > wrote:
> > > > > >>
> > > > > >> Sorry I haven't made an appearance in this thread yet.
> > > > > >>>
> > > > > >>> 6. MQTT streamer
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > >>>>
> > > > > >>> Yes, it was merged to master before the ignite-1.5 was created.
> > > > > >>>
> > > > > >>> I'd like to add:
> > > > > >>>
> > > > > >>> Camel Streamer =>
> > > https://issues.apache.org/jira/browse/IGNITE-1790
> > > > > >>> -- I'll merge this as soon as I finished with the OSGi tickets
> > with
> > > > > >>> demand.
> > > > > >>>
> > > > > >>> OSGi Manifests, Karaf features and possible ClassLoaderCodec
> SPI
> > > (or
> > > > > >>> whatever agreement we arrive to in mailing lists and Wiki)
> > > > > >>> -- https://issues.apache.org/jira/browse/IGNITE-1527
> > > > > >>> -- https://issues.apache.org/jira/browse/IGNITE-1877
> > > > > >>> -- I'm working actively on these two features.
> > > > > >>>
> > > > > >>> *Raúl Kripalani*
> > > > > >>> PMC & Committer @ Apache Ignite, Apache Camel | Integration,
> Big
> > > Data
> > > > > and
> > > > > >>> Messaging Engineer
> > > > > >>> http://about.me/raulkripalani |
> > > > > http://www.linkedin.com/in/raulkripalani
> > > > > >>> http://blog.raulkr.net | twitter: @raulvk
> > > > > >>>
> > > > > >>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <
> > yzhdanov@apache.org
> > > > <javascript:;>>
> > > > > >>> wrote:
> > > > > >>>
> > > > > >>> Guys,
> > > > > >>>>
> > > > > >>>> I think we can start preparation to Ignite-1.5 release which
> > will
> > > > > >>>> include
> > > > > >>>> many interesting features:
> > > > > >>>>
> > > > > >>>> 1. Portable object API
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > >>>>
> > > > > >>>> 2. Ignite.NET and Ignite C++
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > >>>>
> > > > > >>>> 3. Optimistic serializable transactions
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > >>>>
> > > > > >>>> 4. Distributed SQL joins - we will be able to query
> > non-collocated
> > > > > data
> > > > > >>>>
> > > > > >>> as
> > > > > >>>
> > > > > >>>> well
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > >>>>
> > > > > >>>> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > >>>>
> > > > > >>>> 6. MQTT streamer
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > >>>>
> > > > > >>>> 7. Continuous query failover
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > >>>>
> > > > > >>>> 8. Significant transactional cache performance optimizations
> - I
> > > > will
> > > > > >>>>
> > > > > >>> merge
> > > > > >>>
> > > > > >>>> these changes from 'ignite-1.4-slow-server-debug' today or
> > > tomorrow.
> > > > > >>>>
> > > > > >>>> 9. Many stability and fault-tolerance fixes.
> > > > > >>>>
> > > > > >>>> 10. I would also like to include distributed Semaphore.
> > Vladislav,
> > > > any
> > > > > >>>> chance you can finish with it this week?
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-
> > > > > >>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > >>>>
> > > > > >>>> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > > > issues,
> > > > > >>>> please respond to this email and let us know when can we
> expect
> > > your
> > > > > >>>> changes being merged to master and release branch?
> > > > > >>>>
> > > > > >>>> Can someone create ignite-1.5 release branch?
> > > > > >>>>
> > > > > >>>> --Yakov
> > > > > >>>>
> > > > > >>>>
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Igniters,
I am finalizing my optimizations in tx cache (currently there are a couple
of failing tests on CI), I am expecting these changes to be merged in
ignite-1.5 branch tomorrow.
2015-11-16 19:23 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:
> Guys,
>
> Can everyone provide updates on ongoing issues status?
>
> Vlad, I will review Semaphore tomorrow (Russian time).
>
> Thanks!
>
> --Yakov
>
> 2015-11-14 15:38 GMT+03:00 Denis Magda <dm...@gridgain.com>:
>
> > Hi Vladislav,
> >
> > Most likely there is a minor issue in your test.
> >
> > I think Yakov would be able to run and check the test as a part of the
> > ongoing review.
> >
> > Thanks,
> >
> > Denis
> >
> > On Friday, November 13, 2015, Vladisav Jelisavcic <vl...@gmail.com>
> > wrote:
> >
> > > Hi Denis,
> > >
> > > Thanks a lot, it looks like my test setup was wrong,
> > > I added semaphore tests to
> > GridCacheAbstractDataStructuresFailoverSelfTest
> > > suite.
> > > Now I have following problem:
> > > when I run tests with TOP_CHANGE_THREAD_CNT = 3
> > > tests fail when they reach stop() with the following exception:
> > >
> > > class org.apache.ignite.internal.IgniteInterruptedCheckedException:
> Node
> > is
> > > stopping: 09c5e8b8-8998-468e-960d-223220354fd3
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStop0(GridCachePartitionExchangeManager.java:382)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:113)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:946)
> > > at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1823)
> > > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1769)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2133)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2096)
> > > at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:314)
> > > at org.apache.ignite.Ignition.stop(Ignition.java:223)
> > > at
> > >
> > >
> >
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:802)
> > > at
> > >
> > >
> >
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:784)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.access$500(GridCacheAbstractDataStructuresFailoverSelfTest.java:54)
> > > at
> > >
> > >
> >
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest$5.apply(GridCacheAbstractDataStructuresFailoverSelfTest.java:459)
> > >
> > > When I run tests with TOP_CHANGE_THEAD_CNT = 1
> > > everything is running ok;
> > >
> > >
> > > @Yakov
> > > I made a new commit to my IGNITE-638 branch,
> > > can you please take a look?
> > >
> > >
> > >
> > > Best regards,
> > > Vladisav
> > >
> > >
> > >
> > >
> > > > On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <dmagda@gridgain.com
> > > <javascript:;>> wrote:
> > > >
> > > > > Hi Vladislav,
> > > > >
> > > > > Please see below..
> > > > >
> > > > >
> > > > > On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> > > > >
> > > > >> Yakov,
> > > > >>
> > > > >> sorry for running a bit late.
> > > > >>
> > > > >> Vladislav, do you have any updates for
> > > > >>> https://issues.apache.org/jira/browse/IGNITE-638? Or any
> > questions?
> > > > >>>
> > > > >>> --Yakov
> > > > >>>
> > > > >> I have problems with some fail-over scenarios;
> > > > >> It seems that if the two nodes are in the middle of acquiring or
> > > > releasing
> > > > >> the semaphore,
> > > > >> and one of them fails, all nodes get:
> > > > >>
> > > > >>
> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> > > > >> <ignite-atomics-sys-cache> Failed to compare and set:
> > > > >>
> > >
> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> > > > >> class
> > > > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > > >> Failed to acquire lock for keys (primary node left grid, retry
> > > > transaction
> > > > >> if possible) [keys=[UserKeyCacheObjectImpl
> > > [val=GridCacheInternalKeyImpl
> > > > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > > > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > > >> ...
> > > > >> Caused by: class
> > > > >>
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > > Failed
> > > > >> to acquire lock for keys (primary node left grid, retry
> transaction
> > if
> > > > >> possible) [keys=[UserKeyCacheObjectImpl
> > [val=GridCacheInternalKeyImpl
> > > > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > > > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > > >> at
> > > > >>
> > > > >>
> > > >
> > >
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> > > > >> ... 10 more
> > > > >>
> > > > > You have to process this exception manually at your implementation
> > > layer
> > > > > since your data structure uses a transactional cache.
> > > > > Below is a kind of template I used when it was required to process
> > this
> > > > > and some other exeptions. You can use it as-is.
> > > > >
> > > > > int retries = GridCacheAdapter.MAX_RETRIES;
> > > > >
> > > > > IgniteCheckedException err =null;
> > > > >
> > > > > for (int i =0; i < retries; i++) {
> > > > > try {
> > > > > //Your transactional code that may fail
> > > > > }
> > > > > catch (IgniteCheckedException e) {
> > > > > if (i == retries)
> > > > > throw e;
> > > > >
> > > > > if (X.hasCause(e, ClusterTopologyCheckedException.class)) {
> > > > > ClusterTopologyCheckedException topErr =
> > > > > e.getCause(ClusterTopologyCheckedException.class);
> > > > >
> > > > > topErr.retryReadyFuture().get();
> > > > > }
> > > > > else if (X.hasCause(e,
> > IgniteTxRollbackCheckedException.class))
> > > > > U.sleep(1);
> > > > > else throw e;
> > > > > }
> > > > > }
> > > > >
> > > > >
> > > > >
> > > > >> I'm still trying to find out how to exactly reproduce this
> behavior,
> > > > >> I'll send you more details once I try few more things.
> > > > >>
> > > > > There is the test suite called
> > > > > GridCacheAbstractDataStructuresFailoverSelfTest that checks Ignite
> > > > atomics
> > > > > and data structures with fail-over scenario.
> > > > > The suite will let you reproduce ClusterTopologyCheckedException
> > > easily.
> > > > > Just add your tests there referring to the tests of other data
> > > > structures.
> > > > >
> > > > > Presently I'm improving this test suite under my work on IGNITE-801
> > and
> > > > > IGNITE-803. If you finish your task earlier then I'll adopt your
> > tests
> > > > to a
> > > > > new test approach.
> > > > >
> > > > >
> > > > >> I am still using partitioned cache, does it make sense to use
> > > replicated
> > > > >> cache instead?
> > > > >>
> > > > >> Yeah, you should support this as well. Cache mode for the data
> > > > structures
> > > > > is changed using CollectionConfigurations while for atomics using
> > > > > AtomicsConfiguration.
> > > > >
> > > > > --
> > > > > Denis
> > > > >
> > > > >
> > > > > Other than that, I'm done with everything else.
> > > > >>
> > > > >> Thanks,
> > > > >> Vladisav
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <raulk@apache.org
> > > <javascript:;>>
> > > > wrote:
> > > > >>
> > > > >> Sorry I haven't made an appearance in this thread yet.
> > > > >>>
> > > > >>> 6. MQTT streamer
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > > > >>>>
> > > > >>> Yes, it was merged to master before the ignite-1.5 was created.
> > > > >>>
> > > > >>> I'd like to add:
> > > > >>>
> > > > >>> Camel Streamer =>
> > https://issues.apache.org/jira/browse/IGNITE-1790
> > > > >>> -- I'll merge this as soon as I finished with the OSGi tickets
> with
> > > > >>> demand.
> > > > >>>
> > > > >>> OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI
> > (or
> > > > >>> whatever agreement we arrive to in mailing lists and Wiki)
> > > > >>> -- https://issues.apache.org/jira/browse/IGNITE-1527
> > > > >>> -- https://issues.apache.org/jira/browse/IGNITE-1877
> > > > >>> -- I'm working actively on these two features.
> > > > >>>
> > > > >>> *Raúl Kripalani*
> > > > >>> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> > Data
> > > > and
> > > > >>> Messaging Engineer
> > > > >>> http://about.me/raulkripalani |
> > > > http://www.linkedin.com/in/raulkripalani
> > > > >>> http://blog.raulkr.net | twitter: @raulvk
> > > > >>>
> > > > >>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <
> yzhdanov@apache.org
> > > <javascript:;>>
> > > > >>> wrote:
> > > > >>>
> > > > >>> Guys,
> > > > >>>>
> > > > >>>> I think we can start preparation to Ignite-1.5 release which
> will
> > > > >>>> include
> > > > >>>> many interesting features:
> > > > >>>>
> > > > >>>> 1. Portable object API
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > >>>>
> > > > >>>> 2. Ignite.NET and Ignite C++
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > >>>>
> > > > >>>> 3. Optimistic serializable transactions
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > >>>>
> > > > >>>> 4. Distributed SQL joins - we will be able to query
> non-collocated
> > > > data
> > > > >>>>
> > > > >>> as
> > > > >>>
> > > > >>>> well
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > >>>>
> > > > >>>> 5. Enhanced Oracle and IBM JDK interoperability
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > >>>>
> > > > >>>> 6. MQTT streamer
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > > > >>>>
> > > > >>>> 7. Continuous query failover
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-426
> > > > >>>>
> > > > >>>> 8. Significant transactional cache performance optimizations - I
> > > will
> > > > >>>>
> > > > >>> merge
> > > > >>>
> > > > >>>> these changes from 'ignite-1.4-slow-server-debug' today or
> > tomorrow.
> > > > >>>>
> > > > >>>> 9. Many stability and fault-tolerance fixes.
> > > > >>>>
> > > > >>>> 10. I would also like to include distributed Semaphore.
> Vladislav,
> > > any
> > > > >>>> chance you can finish with it this week?
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-
> > > > >>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > >>>>
> > > > >>>> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > > issues,
> > > > >>>> please respond to this email and let us know when can we expect
> > your
> > > > >>>> changes being merged to master and release branch?
> > > > >>>>
> > > > >>>> Can someone create ignite-1.5 release branch?
> > > > >>>>
> > > > >>>> --Yakov
> > > > >>>>
> > > > >>>>
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
Branch ignite-1790 merged into ignite-1.5 with --squash. Like it was
requested previous on previous occasions.
On 19 Nov 2015 03:01, "Dmitriy Setrakyan" <ds...@apache.org> wrote:
> On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani <ra...@evosent.com> wrote:
>
> > I merged the Camel Streamer today and I hope to finish the first phase of
> > OSGi tomorrow.
> >
> > I'll need someone to review the latter quickly if we want it merged for
> > 1.5... No code changes in existing codebase. Just a new osgi module and
> > many POM changes mainly to generate the manifests.
> >
>
> Raul, did you create a patch or a PR? I can’t find it anywhere.
>
>
> >
> > Should be a quick task.
> >
> > Regards,
> > Raúl.
> > On 18 Nov 2015 20:38, "Vladimir Ozerov" <vo...@gridgain.com> wrote:
> >
> > > Hi Alex,
> > >
> > > Today I marged several big things into 1282 - reworked metadat and
> > > compacted footers optimization. I have on big ticket left -
> IGNITE-1917 -
> > > with marshalling microoptimizations. They should not conflict with
> > anything
> > > and I expect them to be finalized tomorrow. All optimizations are
> ready,
> > I
> > > just need to perform some cleanup and refactoring.
> > >
> > > On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> > > alexey.goncharuk@gmail.com> wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I merged performance optimizations for tx mode which gave up to 5%
> > > > improvement for tx-put benchmark to ignite-1.5.
> > > >
> > > > I also pushed finalizaing changes to Binary configuration in
> > ignite-1945
> > > > branch and currently waiting for TC. If all is ok, will cooperate
> with
> > > > Vladimir Ozerov and merge changes tomorrow.
> > > >
> > > > 2015-11-18 17:58 GMT+03:00 Semyon Boikov <sb...@gridgain.com>:
> > > >
> > > > > Hi,
> > > > >
> > > > > Yesterday I merged optimizations for tx update operations working
> > > single
> > > > > key, got ~7% improvement in tx-put benchmark.
> > > > >
> > > > > And today I finished to implement optimization for cache 'get'
> > > operation
> > > > > with single key. Got another benchmark results improvements: ~10%
> > with
> > > > > atomic-put-get, ~5% with tx-put-get. Need to verify TC and
> hopefully
> > > will
> > > > > merge these changes tomorrow.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Igniters,
I am working on IGNITE-1987 (Make binary marshaller default). I cleaned up
javadoc and examples. Changes revealed some issues related to keepBinary
flag not being propagated to continuous query listeners, I am working on
fixing them. Changes should be finalized within one day.
--AG
Re: Ignite-1.5 Release
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
Guys,
I finalized and pushed branch ignite-1753-1282 with updated
CacheJdbcPojoStore that use new classes instead of deprected
CacheTypeMetadata.
See IGNITE-1753 Rework CacheJdbcPojoStore to new API
https://issues.apache.org/jira/browse/IGNITE-1753
I will also update documentation on readme.io shortly.
Thanks.
--
Alexey Kuznetsov
Re: Ignite-1.5 Release
Posted by Denis Magda <dm...@gridgain.com>.
Folks,
Ignite Data Structures suite starts failing from time to time.
In the log I see the following assertion
[15:35:18]W: [org.apache.ignite:ignite-core]
[15:35:18,797][ERROR][ignite-#49380%sys-partitioned.GridCachePartitionedAtomicSetFailoverSelfTest2%][GridCacheIoManager]
Failed to process message
[senderId=b9100721-fd42-4948-846c-bd8d1ad00003, messageType=class
o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicUpdateRequest]
[15:35:18]W: [org.apache.ignite:ignite-core]
java.lang.AssertionError
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.nextPartCounter(GridCacheMapEntry.java:3299)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2383)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:2635)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$800(GridDhtAtomicCache.java:127)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$7.apply(GridDhtAtomicCache.java:269)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$7.apply(GridDhtAtomicCache.java:267)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:576)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:275)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:199)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:78)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:161)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:823)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:105)
[15:35:18]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:786)
[15:35:18]W: [org.apache.ignite:ignite-core] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[15:35:18]W: [org.apache.ignite:ignite-core] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[15:35:18]W: [org.apache.ignite:ignite-core] at
java.lang.Thread.run(Thread.java:745)
Nick, according to the GIT log your changes produced this. Please take a
look.
On 11/23/2015 10:44 AM, Vladimir Ozerov wrote:
> Cool! I closed IGNITE-1282.
>
> On Sun, Nov 22, 2015 at 2:03 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
>> Guys,
>>
>> I finalized and pushed ignite-1282 branch (binary object format) into
>> ignite-1.5. Even though there were no comments from the community around
>> the design on the latest stages of the development, I encourage community
>> to take a look at the changes and provide feedback.
>>
>> Also, while I was finalizing the branch, I fixed some issues that were
>> introduced by the latest optimizations and merges between ignite-1.5 and
>> ignite-1282. Even though the TC was good, it does not mean it revealed all
>> the sporadic test failures, so if you see a suspicious test, please post it
>> here on in a separate topic.
>>
>> Thanks!
>> --AG
>>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Sun, Nov 22, 2015 at 11:44 PM, Vladimir Ozerov <vo...@gridgain.com>
wrote:
> Cool! I closed IGNITE-1282.
>
>
Vladimir, let’s make sure that all closed branches are recorded here:
https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete
Thanks!
> On Sun, Nov 22, 2015 at 2:03 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
> > Guys,
> >
> > I finalized and pushed ignite-1282 branch (binary object format) into
> > ignite-1.5. Even though there were no comments from the community around
> > the design on the latest stages of the development, I encourage community
> > to take a look at the changes and provide feedback.
> >
> > Also, while I was finalizing the branch, I fixed some issues that were
> > introduced by the latest optimizations and merges between ignite-1.5 and
> > ignite-1282. Even though the TC was good, it does not mean it revealed
> all
> > the sporadic test failures, so if you see a suspicious test, please post
> it
> > here on in a separate topic.
> >
> > Thanks!
> > --AG
> >
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Cool! I closed IGNITE-1282.
On Sun, Nov 22, 2015 at 2:03 AM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Guys,
>
> I finalized and pushed ignite-1282 branch (binary object format) into
> ignite-1.5. Even though there were no comments from the community around
> the design on the latest stages of the development, I encourage community
> to take a look at the changes and provide feedback.
>
> Also, while I was finalizing the branch, I fixed some issues that were
> introduced by the latest optimizations and merges between ignite-1.5 and
> ignite-1282. Even though the TC was good, it does not mean it revealed all
> the sporadic test failures, so if you see a suspicious test, please post it
> here on in a separate topic.
>
> Thanks!
> --AG
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Guys,
I finalized and pushed ignite-1282 branch (binary object format) into
ignite-1.5. Even though there were no comments from the community around
the design on the latest stages of the development, I encourage community
to take a look at the changes and provide feedback.
Also, while I was finalizing the branch, I fixed some issues that were
introduced by the latest optimizations and merges between ignite-1.5 and
ignite-1282. Even though the TC was good, it does not mean it revealed all
the sporadic test failures, so if you see a suspicious test, please post it
here on in a separate topic.
Thanks!
--AG
Re: Ignite-1.5 Release
Posted by Valentin Kulichenko <va...@gmail.com>.
Yakov,
I finalized and merged communication optimizations to 1.5 and master.
-Val
On Fri, Nov 20, 2015 at 8:15 AM, Yakov Zhdanov <yz...@apache.org> wrote:
> Guys!
>
> Let's update status info.
>
> 1. Data grid performance optimizations.
>
> Most of the optimizations have been merged. However, there are several
> pending ones
>
>
> 2. Direct marshalling compactions: communication optimization - Valentin
>
> My understanding is that this will be merged in nearest hours. Valentin, is
> that the case?
>
>
> 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
>
> The work is mostly done and ignite-1282 will be merged to release branch in
> several hours. Alexey, please let us know when you are done.
>
> 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
>
> The problem here is that cache updates influence throughput of cache
> operations. As far as I know Semyon has investigated this and found several
> places in code that could cause this. My understanding is that he will
> benchmark and merge this fix over the weekend.
>
>
> Thanks!
>
> --Yakov
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
HI Romain,
On Tue, Nov 24, 2015 at 4:14 PM, Romain Gilles <ro...@gmail.com>
wrote:
> I have some comments for your pull request, one or two points. How does it
> works do you plan to create a pull request?
>
I personally don't create pull requests as I am a committer. The code is in
the ASF branch ignite-1270 [1].
> How can I comment if no, through the mailing list?
>
Parent ticket would be good [2], and only the crowd that's interested get
disturbed (make yourself a watcher).
> Does this branch is planed to be merge for the 1.5?
>
I sure hope so ;-) It depends on the community.
[1] https://github.com/apache/ignite/tree/ignite-1270
[2] https://issues.apache.org/jira/browse/IGNITE-1270
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
Re: Ignite-1.5 Release
Posted by Romain Gilles <ro...@gmail.com>.
Hi Raul and Igniters,
I have some comments for your pull request, one or two points. How does it
works do you plan to create a pull request? How can I comment if no,
through the mailing list?
Does this branch is planed to be merge for the 1.5?
Thanks in advance.
Romain.
Le mar. 24 nov. 2015 à 10:33, Dmitriy Setrakyan <ds...@apache.org> a
écrit :
> Hi Raul,
>
> Thanks for taking on OSGI integration. I have reviewed the documentation
> and it looks good.
>
> At the risk of sounding pedantic, I think this link is best included as
> part of some other OSGI documentation page (no?):
> https://dash.readme.iro/project/apacheignite/v1.5/docs/introduction
> <https://dash.readme.io/project/apacheignite/v1.5/docs/introduction>
>
> Looking forward to seeing a final version.
>
> D.
>
> On Fri, Nov 20, 2015 at 10:47 PM, Raul Kripalani <ra...@apache.org> wrote:
>
> > Igniters,
> >
> > OSGi integration is basically done. I need to give it another review
> pass.
> > I also want to see if I can OSGi-fy the new modules quickly (twitter,
> > flume, etc).
> >
> > Meanwhile I've worked on the documentation and it's pretty much done:
> >
> > *
> >
> >
> https://dash.readme.io/project/apacheignite/v1.5/docs/installation-in-apache-karaf
> > *
> >
> >
> https://dash.readme.io/project/apacheignite/v1.5/docs/installing-in-an-osgi-container
> > * https://dash.readme.io/project/apacheignite/v1.5/docs/introduction
> >
> > I expect to finish everything by Monday evening CET.
> >
> > Could someone please review it on Tuesday for merge into 1.5 next week?
> >
> > Branch is ignite-1270 in case you wanna peek.
> >
> > Thanks,
> >
> > *Raúl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Fri, Nov 20, 2015 at 4:15 PM, Yakov Zhdanov <yz...@apache.org>
> > wrote:
> >
> > > Guys!
> > >
> > > Let's update status info.
> > >
> > > 1. Data grid performance optimizations.
> > >
> > > Most of the optimizations have been merged. However, there are several
> > > pending ones
> > >
> > >
> > > 2. Direct marshalling compactions: communication optimization -
> Valentin
> > >
> > > My understanding is that this will be merged in nearest hours.
> Valentin,
> > is
> > > that the case?
> > >
> > >
> > > 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
> > >
> > > The work is mostly done and ignite-1282 will be merged to release
> branch
> > in
> > > several hours. Alexey, please let us know when you are done.
> > >
> > > 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
> > >
> > > The problem here is that cache updates influence throughput of cache
> > > operations. As far as I know Semyon has investigated this and found
> > several
> > > places in code that could cause this. My understanding is that he will
> > > benchmark and merge this fix over the weekend.
> > >
> > >
> > > Thanks!
> > >
> > > --Yakov
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Nikolay Tikhonov <nt...@gridgain.com>.
I'm fully agree with Yakov. We plain to release massive changes and I think
that it's good chance for community to play with new features and we can
get more feedback.
On Mon, Nov 30, 2015 at 7:32 PM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> +1 for EA
>
> On Mon, Nov 30, 2015 at 11:30 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Guys,
> >
> > Our plan was to release over the weekend, but unfortunately that didn’t
> > happen due to a few bugs. And even though we have fixed all the
> discovered
> > issues I am still not comfortable with releasing the final version.
> Having
> > the great number of functionality introduced in 1.5 including (but not
> > limited to) - .net and cpp platforms, marshalling changes to support
> > platforms and massive optimizations - I would ask community whether we
> can
> > release 1.5.0-EA and have folks to play with it for a week or so and then
> > release the final version.
> >
> > Please let me know your opinion. If community agrees I will submit
> 1.5.0-EA
> > for vote in a few hours.
> >
> > --Yakov
> >
> > 2015-11-28 13:57 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:
> >
> > > Guys,
> > >
> > > Small update. We are very close to submit Ignite-1.5-RC1. We currently
> > > fixing TeamCity in ignite-1.5 branch.
> > >
> > > --Yakov
> > >
> > > 2015-11-25 3:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> > >
> > >> On Wed, Nov 25, 2015 at 3:09 AM, Raul Kripalani <ra...@apache.org>
> > wrote:
> > >>
> > >> > It's integrated, i.e. it deploys on an OSGi container. And the
> Ignite
> > >> part
> > >> > works. But at soon as it delegates to Spring to parse the context
> XML,
> > >> the
> > >> > latter complains about namespace handlers not being found.
> > >> >
> > >> > Spring DM looks into bundles to find NS handlers. So without Spring
> DM
> > >> such
> > >> > problems are expected.
> > >> >
> > >> > Maybe it does work after all if we refrain from using certain
> > namespace
> > >> > like util. I'll have to check that tomorrow.
> > >> >
> > >>
> > >> Thanks! Dropping support for Spring XML configuration in OSGI would
> be a
> > >> huge loss. Would be great if you could investigate it and see what it
> > >> would
> > >> take.
> > >>
> > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Ignite-1.5 Release
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
+1 for EA
On Mon, Nov 30, 2015 at 11:30 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Guys,
>
> Our plan was to release over the weekend, but unfortunately that didn’t
> happen due to a few bugs. And even though we have fixed all the discovered
> issues I am still not comfortable with releasing the final version. Having
> the great number of functionality introduced in 1.5 including (but not
> limited to) - .net and cpp platforms, marshalling changes to support
> platforms and massive optimizations - I would ask community whether we can
> release 1.5.0-EA and have folks to play with it for a week or so and then
> release the final version.
>
> Please let me know your opinion. If community agrees I will submit 1.5.0-EA
> for vote in a few hours.
>
> --Yakov
>
> 2015-11-28 13:57 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:
>
> > Guys,
> >
> > Small update. We are very close to submit Ignite-1.5-RC1. We currently
> > fixing TeamCity in ignite-1.5 branch.
> >
> > --Yakov
> >
> > 2015-11-25 3:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> >
> >> On Wed, Nov 25, 2015 at 3:09 AM, Raul Kripalani <ra...@apache.org>
> wrote:
> >>
> >> > It's integrated, i.e. it deploys on an OSGi container. And the Ignite
> >> part
> >> > works. But at soon as it delegates to Spring to parse the context XML,
> >> the
> >> > latter complains about namespace handlers not being found.
> >> >
> >> > Spring DM looks into bundles to find NS handlers. So without Spring DM
> >> such
> >> > problems are expected.
> >> >
> >> > Maybe it does work after all if we refrain from using certain
> namespace
> >> > like util. I'll have to check that tomorrow.
> >> >
> >>
> >> Thanks! Dropping support for Spring XML configuration in OSGI would be a
> >> huge loss. Would be great if you could investigate it and see what it
> >> would
> >> take.
> >>
> >
> >
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
If so we will have EA2.
--Yakov
2015-11-30 20:13 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> On Mon, Nov 30, 2015 at 9:12 AM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Dmitry, it will be 1.5.0-EA.
> >
>
> How about 1.5.0-EA1? We may have more than one EA release.
Re: Ignite-1.5 Release
Posted by Sergey Kozlov <sk...@gridgain.com>.
Next EA will be EA2 but I hope it will be RC1
On Mon, Nov 30, 2015 at 8:13 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> On Mon, Nov 30, 2015 at 9:12 AM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Dmitry, it will be 1.5.0-EA.
> >
>
> How about 1.5.0-EA1? We may have more than one EA release.
>
>
> >
> > --Yakov
> >
> > 2015-11-30 20:10 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > On Mon, Nov 30, 2015 at 9:09 AM, Yakov Zhdanov <yz...@apache.org>
> > > wrote:
> > >
> > > > Guys, common practice when dealing with EA builds is to have EA (or
> > EA1),
> > > > EA2, etc versions. So, I would prefer to follow this process.
> > > >
> > >
> > > Yakov, what would be the final version of the downloadable EA release?
> > >
> > >
> > > >
> > > > --Yakov
> > > >
> > > > 2015-11-30 20:04 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org
> >:
> > > >
> > > > > On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani <ra...@apache.org>
> > > > wrote:
> > > > >
> > > > > > On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov <
> > yzhdanov@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Please let me know your opinion. If community agrees I will
> > submit
> > > > > > 1.5.0-EA
> > > > > > > for vote in a few hours.
> > > > > > >
> > > > > >
> > > > >
> > > > > > Would this be an EA or a RC?
> > > > > >
> > > > >
> > > > > I think we should definitely release an early access, prior to a
> > final
> > > > > release. However, as Raul pointed out, it should be 1.5.0-RC1
> > version.
> > > > >
> > > > >
> > > > > > Regards,
> > > > > >
> > > > > > *Raúl Kripalani*
> > > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> > Data
> > > > and
> > > > > > Messaging Engineer
> > > > > > http://about.me/raulkripalani |
> > > > http://www.linkedin.com/in/raulkripalani
> > > > > > http://blog.raulkr.net | twitter: @raulvk
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Sergey Kozlov
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Mon, Nov 30, 2015 at 9:12 AM, Yakov Zhdanov <yz...@apache.org> wrote:
> Dmitry, it will be 1.5.0-EA.
>
How about 1.5.0-EA1? We may have more than one EA release.
>
> --Yakov
>
> 2015-11-30 20:10 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
>
> > On Mon, Nov 30, 2015 at 9:09 AM, Yakov Zhdanov <yz...@apache.org>
> > wrote:
> >
> > > Guys, common practice when dealing with EA builds is to have EA (or
> EA1),
> > > EA2, etc versions. So, I would prefer to follow this process.
> > >
> >
> > Yakov, what would be the final version of the downloadable EA release?
> >
> >
> > >
> > > --Yakov
> > >
> > > 2015-11-30 20:04 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> > >
> > > > On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani <ra...@apache.org>
> > > wrote:
> > > >
> > > > > On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov <
> yzhdanov@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Please let me know your opinion. If community agrees I will
> submit
> > > > > 1.5.0-EA
> > > > > > for vote in a few hours.
> > > > > >
> > > > >
> > > >
> > > > > Would this be an EA or a RC?
> > > > >
> > > >
> > > > I think we should definitely release an early access, prior to a
> final
> > > > release. However, as Raul pointed out, it should be 1.5.0-RC1
> version.
> > > >
> > > >
> > > > > Regards,
> > > > >
> > > > > *Raúl Kripalani*
> > > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> Data
> > > and
> > > > > Messaging Engineer
> > > > > http://about.me/raulkripalani |
> > > http://www.linkedin.com/in/raulkripalani
> > > > > http://blog.raulkr.net | twitter: @raulvk
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Dmitry, it will be 1.5.0-EA.
--Yakov
2015-11-30 20:10 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> On Mon, Nov 30, 2015 at 9:09 AM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Guys, common practice when dealing with EA builds is to have EA (or EA1),
> > EA2, etc versions. So, I would prefer to follow this process.
> >
>
> Yakov, what would be the final version of the downloadable EA release?
>
>
> >
> > --Yakov
> >
> > 2015-11-30 20:04 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani <ra...@apache.org>
> > wrote:
> > >
> > > > On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov <yz...@apache.org>
> > > > wrote:
> > > >
> > > > > Please let me know your opinion. If community agrees I will submit
> > > > 1.5.0-EA
> > > > > for vote in a few hours.
> > > > >
> > > >
> > >
> > > > Would this be an EA or a RC?
> > > >
> > >
> > > I think we should definitely release an early access, prior to a final
> > > release. However, as Raul pointed out, it should be 1.5.0-RC1 version.
> > >
> > >
> > > > Regards,
> > > >
> > > > *Raúl Kripalani*
> > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> > and
> > > > Messaging Engineer
> > > > http://about.me/raulkripalani |
> > http://www.linkedin.com/in/raulkripalani
> > > > http://blog.raulkr.net | twitter: @raulvk
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Mon, Nov 30, 2015 at 9:09 AM, Yakov Zhdanov <yz...@apache.org> wrote:
> Guys, common practice when dealing with EA builds is to have EA (or EA1),
> EA2, etc versions. So, I would prefer to follow this process.
>
Yakov, what would be the final version of the downloadable EA release?
>
> --Yakov
>
> 2015-11-30 20:04 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
>
> > On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani <ra...@apache.org>
> wrote:
> >
> > > On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov <yz...@apache.org>
> > > wrote:
> > >
> > > > Please let me know your opinion. If community agrees I will submit
> > > 1.5.0-EA
> > > > for vote in a few hours.
> > > >
> > >
> >
> > > Would this be an EA or a RC?
> > >
> >
> > I think we should definitely release an early access, prior to a final
> > release. However, as Raul pointed out, it should be 1.5.0-RC1 version.
> >
> >
> > > Regards,
> > >
> > > *Raúl Kripalani*
> > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> and
> > > Messaging Engineer
> > > http://about.me/raulkripalani |
> http://www.linkedin.com/in/raulkripalani
> > > http://blog.raulkr.net | twitter: @raulvk
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Guys, common practice when dealing with EA builds is to have EA (or EA1),
EA2, etc versions. So, I would prefer to follow this process.
--Yakov
2015-11-30 20:04 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani <ra...@apache.org> wrote:
>
> > On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov <yz...@apache.org>
> > wrote:
> >
> > > Please let me know your opinion. If community agrees I will submit
> > 1.5.0-EA
> > > for vote in a few hours.
> > >
> >
>
> > Would this be an EA or a RC?
> >
>
> I think we should definitely release an early access, prior to a final
> release. However, as Raul pointed out, it should be 1.5.0-RC1 version.
>
>
> > Regards,
> >
> > *Raúl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani <ra...@apache.org> wrote:
> On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Please let me know your opinion. If community agrees I will submit
> 1.5.0-EA
> > for vote in a few hours.
> >
>
> Would this be an EA or a RC?
>
I think we should definitely release an early access, prior to a final
release. However, as Raul pointed out, it should be 1.5.0-RC1 version.
> Regards,
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
Re: Ignite-1.5 Release
Posted by Ognen Duzlevski <og...@gmail.com>.
On Mon, Nov 30, 2015 at 12:39 PM, Raul Kripalani <ra...@apache.org> wrote:
>
> We have opposite views here. To me, early access versions are ephemeral.
> They are only legit until the final version is released. By doing that, you
> run the risk that "forgetful" users who once tried an EA, keep using it
> forever even after GA is released.
>
Apache Ignite is a product for professionals - engineers etc. If someone
"forgets" that their production is running the EA version, well, they need
to look for a different profession ;). Comparing it to Windows 12 EA is
silly, IMHO, since most people using Windows are technically not at the
same level, they are far below.
My $.02.
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Guys, there is obviously a difference of opinions here. If I can make a
suggestion, let’s agree on the versioning scheme and proceed. I like Raul’s
suggestion for EA-01/02/03/etc… If there are no objections, let’s follow
this scheme going forward.
D.
On Mon, Nov 30, 2015 at 3:11 PM, Raul Kripalani <ra...@apache.org> wrote:
> On Mon, Nov 30, 2015 at 8:41 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Raul, I don't see anything wrong with this approach. EA2 can follow EA.
> > Versioning of EAs does not matter too much to me :)
> >
>
> If you are wanting to push EAs to Central, then we must have a predictable
> versioning scheme. Publishing to Central makes the release perpetual. So
> EA2 after EA is not predictable. If you insist on this idea, I would use
> EA-01, EA-02, EA-03, etc.
>
> Let's design things out well and avoid being haphazard.
>
>
> > You can download EAP build of IntellijIdea, although Idea 14 is available
> > now for more than 1 year already.
> >
>
> You know for a fact that IntelliJ's EAPs are removed once they are no
> longer relevant. Because they own their file server and can remove them
> whenever they want. That's why only 15 EAP and 14.1 EAP are available.
>
> Haven't you thought why 13 EAP, 12 EAP, etc. are no longer available?
>
>
> > Btw, here is one more example of keeping EA versions in repo -
> > http://mvnrepository.com/artifact/com.sun.jersey/jersey-client
> >
>
> You are talking about releases from 2012 and older. Haven't you realised
> why they stopped doing that? Please don't bend reality to make it fit your
> arguments.
>
> Hibernate seems to keep all versions in maven -
> > http://mvnrepository.com/artifact/org.hibernate/hibernate-core
> >
>
> Yes, and they publish Betas, Service Packs, Release Candidates, etc. They
> have a complex, pragmatic and well-defined lifecycle.
> We are just talking about EAs in a very particular situation. It's going to
> be extremely random to look back and see:
>
> Ignite 1.2.0
> Ignite 1.3.0
> Ignite 1.4.0
> Ignite 1.5.0-EA
> Ignite 1.5.0
> Ignite 1.6.0
>
> If we want to define a full lifecycle with public milestones, I'm all up
> for it. It does create lots of complexity and release work, though. But
> publishing an EA to Central just because in this particular release we
> changed something big, to me it's a NO-NO.
>
>
> > Personally I do not insist on releasing this in maven, but I don't think
> > this is anything extraordinary.
> >
> > Guys, any more opinions?
> >
>
> I would like to hear the opinions of people outside of GG. @Cos, @Brane?
>
> And please Yakov, let's respect the community and don't take decisions by
> ourself without consensus and without giving people the opportunity to
> speak their mind.
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
On Mon, Nov 30, 2015 at 8:41 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Raul, I don't see anything wrong with this approach. EA2 can follow EA.
> Versioning of EAs does not matter too much to me :)
>
If you are wanting to push EAs to Central, then we must have a predictable
versioning scheme. Publishing to Central makes the release perpetual. So
EA2 after EA is not predictable. If you insist on this idea, I would use
EA-01, EA-02, EA-03, etc.
Let's design things out well and avoid being haphazard.
> You can download EAP build of IntellijIdea, although Idea 14 is available
> now for more than 1 year already.
>
You know for a fact that IntelliJ's EAPs are removed once they are no
longer relevant. Because they own their file server and can remove them
whenever they want. That's why only 15 EAP and 14.1 EAP are available.
Haven't you thought why 13 EAP, 12 EAP, etc. are no longer available?
> Btw, here is one more example of keeping EA versions in repo -
> http://mvnrepository.com/artifact/com.sun.jersey/jersey-client
>
You are talking about releases from 2012 and older. Haven't you realised
why they stopped doing that? Please don't bend reality to make it fit your
arguments.
Hibernate seems to keep all versions in maven -
> http://mvnrepository.com/artifact/org.hibernate/hibernate-core
>
Yes, and they publish Betas, Service Packs, Release Candidates, etc. They
have a complex, pragmatic and well-defined lifecycle.
We are just talking about EAs in a very particular situation. It's going to
be extremely random to look back and see:
Ignite 1.2.0
Ignite 1.3.0
Ignite 1.4.0
Ignite 1.5.0-EA
Ignite 1.5.0
Ignite 1.6.0
If we want to define a full lifecycle with public milestones, I'm all up
for it. It does create lots of complexity and release work, though. But
publishing an EA to Central just because in this particular release we
changed something big, to me it's a NO-NO.
> Personally I do not insist on releasing this in maven, but I don't think
> this is anything extraordinary.
>
> Guys, any more opinions?
>
I would like to hear the opinions of people outside of GG. @Cos, @Brane?
And please Yakov, let's respect the community and don't take decisions by
ourself without consensus and without giving people the opportunity to
speak their mind.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Raul, I don't see anything wrong with this approach. EA2 can follow EA.
Versioning of EAs does not matter too much to me :)
You can download EAP build of IntellijIdea, although Idea 14 is available
now for more than 1 year already.
Btw, here is one more example of keeping EA versions in repo -
http://mvnrepository.com/artifact/com.sun.jersey/jersey-client
Hibernate seems to keep all versions in maven -
http://mvnrepository.com/artifact/org.hibernate/hibernate-core
Personally I do not insist on releasing this in maven, but I don't think
this is anything extraordinary.
Guys, any more opinions?
--Yakov
2015-11-30 22:12 GMT+03:00 Raul Kripalani <ra...@evosent.com>:
> Any others? I need some more convincing :)
>
> That Hazelcast does it doesn't mean that it's correct SW Engineering
> practice. Perhaps they don't have a public Maven repo (probably that's the
> reason) where they can publish their EA in a staging area. The ASF does
> (advantage) and therefore we can use this facility.
>
> Moreover that nomenclature is horrible. It ties them up to a single EA.
> What if it comes out with a blocking bug that impedes testing? They'd need
> to release a second EA, and that's not taken into account.
> On 30 Nov 2015 18:50, "Sergey Kozlov" <sk...@gridgain.com> wrote:
>
> > Hi
> >
> > Some companies provide EA releases in maven:
> >
> >
> >
> https://oss.sonatype.org/content/repositories/releases/com/hazelcast/hazelcast/3.6-EA/
> >
> >
> > On Mon, Nov 30, 2015 at 9:39 PM, Raul Kripalani <ra...@apache.org>
> wrote:
> >
> > > On Mon, Nov 30, 2015 at 5:23 PM, Yakov Zhdanov <yz...@apache.org>
> > > wrote:
> > >
> > > > 1. I see nothing wrong in having EA perpetually available. I would
> even
> > > > prefer all vendors to keep all EA versions available just for
> tracking
> > > and
> > > > history purposes.
> > > >
> > >
> > > We have opposite views here. To me, early access versions are
> ephemeral.
> > > They are only legit until the final version is released. By doing that,
> > you
> > > run the risk that "forgetful" users who once tried an EA, keep using it
> > > forever even after GA is released.
> > >
> > > In other words, what you are proposing to do – to push an EA to Maven
> > > Central – is equivalent to Microsoft packaging Windows 11 Early Access
> > in a
> > > box and putting it on sale forever. And keeping it on sale even after
> > > Windows 11 GA, Windows 12 GA, Windows 13 GA (Americans would probably
> > skip
> > > that :)), etc. are released decades after.
> > >
> > > No company or project does that, to my knowledge. I would consider it
> an
> > > anti-pattern.
> > >
> > > Regards,
> > >
> > > *Raúl Kripalani*
> > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> and
> > > Messaging Engineer
> > > http://about.me/raulkripalani |
> http://www.linkedin.com/in/raulkripalani
> > > http://blog.raulkr.net | twitter: @raulvk
> > >
> >
> >
> >
> > --
> > Sergey Kozlov
> >
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@evosent.com>.
Any others? I need some more convincing :)
That Hazelcast does it doesn't mean that it's correct SW Engineering
practice. Perhaps they don't have a public Maven repo (probably that's the
reason) where they can publish their EA in a staging area. The ASF does
(advantage) and therefore we can use this facility.
Moreover that nomenclature is horrible. It ties them up to a single EA.
What if it comes out with a blocking bug that impedes testing? They'd need
to release a second EA, and that's not taken into account.
On 30 Nov 2015 18:50, "Sergey Kozlov" <sk...@gridgain.com> wrote:
> Hi
>
> Some companies provide EA releases in maven:
>
>
> https://oss.sonatype.org/content/repositories/releases/com/hazelcast/hazelcast/3.6-EA/
>
>
> On Mon, Nov 30, 2015 at 9:39 PM, Raul Kripalani <ra...@apache.org> wrote:
>
> > On Mon, Nov 30, 2015 at 5:23 PM, Yakov Zhdanov <yz...@apache.org>
> > wrote:
> >
> > > 1. I see nothing wrong in having EA perpetually available. I would even
> > > prefer all vendors to keep all EA versions available just for tracking
> > and
> > > history purposes.
> > >
> >
> > We have opposite views here. To me, early access versions are ephemeral.
> > They are only legit until the final version is released. By doing that,
> you
> > run the risk that "forgetful" users who once tried an EA, keep using it
> > forever even after GA is released.
> >
> > In other words, what you are proposing to do – to push an EA to Maven
> > Central – is equivalent to Microsoft packaging Windows 11 Early Access
> in a
> > box and putting it on sale forever. And keeping it on sale even after
> > Windows 11 GA, Windows 12 GA, Windows 13 GA (Americans would probably
> skip
> > that :)), etc. are released decades after.
> >
> > No company or project does that, to my knowledge. I would consider it an
> > anti-pattern.
> >
> > Regards,
> >
> > *Raúl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
>
>
>
> --
> Sergey Kozlov
>
Re: Ignite-1.5 Release
Posted by Sergey Kozlov <sk...@gridgain.com>.
Hi
Some companies provide EA releases in maven:
https://oss.sonatype.org/content/repositories/releases/com/hazelcast/hazelcast/3.6-EA/
On Mon, Nov 30, 2015 at 9:39 PM, Raul Kripalani <ra...@apache.org> wrote:
> On Mon, Nov 30, 2015 at 5:23 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > 1. I see nothing wrong in having EA perpetually available. I would even
> > prefer all vendors to keep all EA versions available just for tracking
> and
> > history purposes.
> >
>
> We have opposite views here. To me, early access versions are ephemeral.
> They are only legit until the final version is released. By doing that, you
> run the risk that "forgetful" users who once tried an EA, keep using it
> forever even after GA is released.
>
> In other words, what you are proposing to do – to push an EA to Maven
> Central – is equivalent to Microsoft packaging Windows 11 Early Access in a
> box and putting it on sale forever. And keeping it on sale even after
> Windows 11 GA, Windows 12 GA, Windows 13 GA (Americans would probably skip
> that :)), etc. are released decades after.
>
> No company or project does that, to my knowledge. I would consider it an
> anti-pattern.
>
> Regards,
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
--
Sergey Kozlov
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
On Mon, Nov 30, 2015 at 5:23 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> 1. I see nothing wrong in having EA perpetually available. I would even
> prefer all vendors to keep all EA versions available just for tracking and
> history purposes.
>
We have opposite views here. To me, early access versions are ephemeral.
They are only legit until the final version is released. By doing that, you
run the risk that "forgetful" users who once tried an EA, keep using it
forever even after GA is released.
In other words, what you are proposing to do – to push an EA to Maven
Central – is equivalent to Microsoft packaging Windows 11 Early Access in a
box and putting it on sale forever. And keeping it on sale even after
Windows 11 GA, Windows 12 GA, Windows 13 GA (Americans would probably skip
that :)), etc. are released decades after.
No company or project does that, to my knowledge. I would consider it an
anti-pattern.
Regards,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Raul, I see your point. However
1. I see nothing wrong in having EA perpetually available. I would even
prefer all vendors to keep all EA versions available just for tracking and
history purposes.
2. Even if we choose not to do maven release we can still go with EA and
just leave staging repo unreleased.
--Yakov
2015-11-30 20:17 GMT+03:00 Raul Kripalani <ra...@apache.org>:
> On Mon, Nov 30, 2015 at 5:05 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Raul, every build submitted for vote is RC (so, on first iteration this
> > will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get
> > official release. My idea is to have EA available via maven and from the
> > website.
> >
>
> Aha, I see. I'm not sure I like the idea of pushing the EA to Maven Central
> and making it live there perpetually. After 3 years, we would still have an
> 1.5.0.EA there.
> Red Hat is a company that uses EAs quite often. They have a separate Maven
> repo for them, from which they prune the EAs once they become GA.
>
> I prefer that we publish a RC1 to a staging repo and inform our users via
> mailing list. All they'd have to do to take 1.5.0-RC1 for a spin is add the
> staging repo to their pom.xml.
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Mon, Nov 30, 2015 at 9:17 AM, Raul Kripalani <ra...@apache.org> wrote:
> On Mon, Nov 30, 2015 at 5:05 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Raul, every build submitted for vote is RC (so, on first iteration this
> > will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get
> > official release. My idea is to have EA available via maven and from the
> > website.
> >
>
> Aha, I see. I'm not sure I like the idea of pushing the EA to Maven Central
> and making it live there perpetually. After 3 years, we would still have an
> 1.5.0.EA there.
> Red Hat is a company that uses EAs quite often. They have a separate Maven
> repo for them, from which they prune the EAs once they become GA.
>
> I prefer that we publish a RC1 to a staging repo and inform our users via
> mailing list. All they'd have to do to take 1.5.0-RC1 for a spin is add the
> staging repo to their pom.xml.
>
Raul, personally, I am more in favor of adding the EA to Maven. Having it
there forever does not really scare me. It will be a lot easier for the
community to take the release for a spin without having some special
instructions. Moreover, I imagine that many users will jump on it as well,
as it sounds like the release is pretty close to the production-ready state.
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
On Mon, Nov 30, 2015 at 5:05 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Raul, every build submitted for vote is RC (so, on first iteration this
> will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get
> official release. My idea is to have EA available via maven and from the
> website.
>
Aha, I see. I'm not sure I like the idea of pushing the EA to Maven Central
and making it live there perpetually. After 3 years, we would still have an
1.5.0.EA there.
Red Hat is a company that uses EAs quite often. They have a separate Maven
repo for them, from which they prune the EAs once they become GA.
I prefer that we publish a RC1 to a staging repo and inform our users via
mailing list. All they'd have to do to take 1.5.0-RC1 for a spin is add the
staging repo to their pom.xml.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Raul, every build submitted for vote is RC (so, on first iteration this
will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get
official release. My idea is to have EA available via maven and from the
website.
--Yakov
2015-11-30 19:57 GMT+03:00 Raul Kripalani <ra...@apache.org>:
> On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Please let me know your opinion. If community agrees I will submit
> 1.5.0-EA
> > for vote in a few hours.
> >
>
> Would this be an EA or a RC?
>
> Regards,
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Agree, +1 for the EA. We are preparing to change the default marshaller, so
it will be great to obtain the feedback from the community and see if we
missed something.
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Please let me know your opinion. If community agrees I will submit 1.5.0-EA
> for vote in a few hours.
>
Would this be an EA or a RC?
Regards,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Guys,
Our plan was to release over the weekend, but unfortunately that didn’t
happen due to a few bugs. And even though we have fixed all the discovered
issues I am still not comfortable with releasing the final version. Having
the great number of functionality introduced in 1.5 including (but not
limited to) - .net and cpp platforms, marshalling changes to support
platforms and massive optimizations - I would ask community whether we can
release 1.5.0-EA and have folks to play with it for a week or so and then
release the final version.
Please let me know your opinion. If community agrees I will submit 1.5.0-EA
for vote in a few hours.
--Yakov
2015-11-28 13:57 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:
> Guys,
>
> Small update. We are very close to submit Ignite-1.5-RC1. We currently
> fixing TeamCity in ignite-1.5 branch.
>
> --Yakov
>
> 2015-11-25 3:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
>
>> On Wed, Nov 25, 2015 at 3:09 AM, Raul Kripalani <ra...@apache.org> wrote:
>>
>> > It's integrated, i.e. it deploys on an OSGi container. And the Ignite
>> part
>> > works. But at soon as it delegates to Spring to parse the context XML,
>> the
>> > latter complains about namespace handlers not being found.
>> >
>> > Spring DM looks into bundles to find NS handlers. So without Spring DM
>> such
>> > problems are expected.
>> >
>> > Maybe it does work after all if we refrain from using certain namespace
>> > like util. I'll have to check that tomorrow.
>> >
>>
>> Thanks! Dropping support for Spring XML configuration in OSGI would be a
>> huge loss. Would be great if you could investigate it and see what it
>> would
>> take.
>>
>
>
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Guys,
Small update. We are very close to submit Ignite-1.5-RC1. We currently
fixing TeamCity in ignite-1.5 branch.
--Yakov
2015-11-25 3:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> On Wed, Nov 25, 2015 at 3:09 AM, Raul Kripalani <ra...@apache.org> wrote:
>
> > It's integrated, i.e. it deploys on an OSGi container. And the Ignite
> part
> > works. But at soon as it delegates to Spring to parse the context XML,
> the
> > latter complains about namespace handlers not being found.
> >
> > Spring DM looks into bundles to find NS handlers. So without Spring DM
> such
> > problems are expected.
> >
> > Maybe it does work after all if we refrain from using certain namespace
> > like util. I'll have to check that tomorrow.
> >
>
> Thanks! Dropping support for Spring XML configuration in OSGI would be a
> huge loss. Would be great if you could investigate it and see what it would
> take.
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Wed, Nov 25, 2015 at 3:09 AM, Raul Kripalani <ra...@apache.org> wrote:
> It's integrated, i.e. it deploys on an OSGi container. And the Ignite part
> works. But at soon as it delegates to Spring to parse the context XML, the
> latter complains about namespace handlers not being found.
>
> Spring DM looks into bundles to find NS handlers. So without Spring DM such
> problems are expected.
>
> Maybe it does work after all if we refrain from using certain namespace
> like util. I'll have to check that tomorrow.
>
Thanks! Dropping support for Spring XML configuration in OSGI would be a
huge loss. Would be great if you could investigate it and see what it would
take.
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
It's integrated, i.e. it deploys on an OSGi container. And the Ignite part
works. But at soon as it delegates to Spring to parse the context XML, the
latter complains about namespace handlers not being found.
Spring DM looks into bundles to find NS handlers. So without Spring DM such
problems are expected.
Maybe it does work after all if we refrain from using certain namespace
like util. I'll have to check that tomorrow.
Raúl.
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Tue, Nov 24, 2015 at 11:16 PM, Raul Kripalani <ra...@apache.org> wrote:
> On Tue, Nov 24, 2015 at 9:32 AM, Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
> > At the risk of sounding pedantic, I think this link is best included as
> > part of some other OSGI documentation page (no?):
> > https://dash.readme.io/project/apacheignite/v1.5/docs/introduction
> >
>
> The page slug/permalink was incorrect. I updated it and it's now
>
> https://dash.readme.io/project/apacheignite/v1.5/docs/osgi-supported-modules
> .
>
> I wanted to include this as an explicit section so that it catches the
> user's attention in order to set their expectations accurately about what's
> supported and what isn't. I prefer to avoid surprises in case they didn't
> see that section if it's "buried" elsewhere.
>
Agree. Btw, is ignite-spring module supported? I thought you mentioned that
it is not in another email.
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
On Tue, Nov 24, 2015 at 9:32 AM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> At the risk of sounding pedantic, I think this link is best included as
> part of some other OSGI documentation page (no?):
> https://dash.readme.io/project/apacheignite/v1.5/docs/introduction
>
The page slug/permalink was incorrect. I updated it and it's now
https://dash.readme.io/project/apacheignite/v1.5/docs/osgi-supported-modules
.
I wanted to include this as an explicit section so that it catches the
user's attention in order to set their expectations accurately about what's
supported and what isn't. I prefer to avoid surprises in case they didn't
see that section if it's "buried" elsewhere.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Hi Raul,
Thanks for taking on OSGI integration. I have reviewed the documentation
and it looks good.
At the risk of sounding pedantic, I think this link is best included as
part of some other OSGI documentation page (no?):
https://dash.readme.io/project/apacheignite/v1.5/docs/introduction
Looking forward to seeing a final version.
D.
On Fri, Nov 20, 2015 at 10:47 PM, Raul Kripalani <ra...@apache.org> wrote:
> Igniters,
>
> OSGi integration is basically done. I need to give it another review pass.
> I also want to see if I can OSGi-fy the new modules quickly (twitter,
> flume, etc).
>
> Meanwhile I've worked on the documentation and it's pretty much done:
>
> *
>
> https://dash.readme.io/project/apacheignite/v1.5/docs/installation-in-apache-karaf
> *
>
> https://dash.readme.io/project/apacheignite/v1.5/docs/installing-in-an-osgi-container
> * https://dash.readme.io/project/apacheignite/v1.5/docs/introduction
>
> I expect to finish everything by Monday evening CET.
>
> Could someone please review it on Tuesday for merge into 1.5 next week?
>
> Branch is ignite-1270 in case you wanna peek.
>
> Thanks,
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Fri, Nov 20, 2015 at 4:15 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Guys!
> >
> > Let's update status info.
> >
> > 1. Data grid performance optimizations.
> >
> > Most of the optimizations have been merged. However, there are several
> > pending ones
> >
> >
> > 2. Direct marshalling compactions: communication optimization - Valentin
> >
> > My understanding is that this will be merged in nearest hours. Valentin,
> is
> > that the case?
> >
> >
> > 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
> >
> > The work is mostly done and ignite-1282 will be merged to release branch
> in
> > several hours. Alexey, please let us know when you are done.
> >
> > 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
> >
> > The problem here is that cache updates influence throughput of cache
> > operations. As far as I know Semyon has investigated this and found
> several
> > places in code that could cause this. My understanding is that he will
> > benchmark and merge this fix over the weekend.
> >
> >
> > Thanks!
> >
> > --Yakov
> >
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
Igniters,
OSGi integration is basically done. I need to give it another review pass.
I also want to see if I can OSGi-fy the new modules quickly (twitter,
flume, etc).
Meanwhile I've worked on the documentation and it's pretty much done:
*
https://dash.readme.io/project/apacheignite/v1.5/docs/installation-in-apache-karaf
*
https://dash.readme.io/project/apacheignite/v1.5/docs/installing-in-an-osgi-container
* https://dash.readme.io/project/apacheignite/v1.5/docs/introduction
I expect to finish everything by Monday evening CET.
Could someone please review it on Tuesday for merge into 1.5 next week?
Branch is ignite-1270 in case you wanna peek.
Thanks,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Fri, Nov 20, 2015 at 4:15 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Guys!
>
> Let's update status info.
>
> 1. Data grid performance optimizations.
>
> Most of the optimizations have been merged. However, there are several
> pending ones
>
>
> 2. Direct marshalling compactions: communication optimization - Valentin
>
> My understanding is that this will be merged in nearest hours. Valentin, is
> that the case?
>
>
> 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
>
> The work is mostly done and ignite-1282 will be merged to release branch in
> several hours. Alexey, please let us know when you are done.
>
> 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
>
> The problem here is that cache updates influence throughput of cache
> operations. As far as I know Semyon has investigated this and found several
> places in code that could cause this. My understanding is that he will
> benchmark and merge this fix over the weekend.
>
>
> Thanks!
>
> --Yakov
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Folks,
There is a couple of sporadical hangs in the branch, need more time to
investigate and fix. Will take a look tomorrow SPb time.
2015-11-20 21:11 GMT+03:00 Alexey Goncharuk <al...@gmail.com>:
> Yakov,
>
> I still see some of the tests fail on TC in ignite-1282 branch. Some of
> them are related to branch-local changes, some of them are related to the
> latest optimizations that were merged to ignite-1.5 (for example, there was
> a deadlock in restart tests introduced by local collection synchronization
> in MVCC manager).
>
> I pushed the changes to TC, so I will give another update in a couple of
> hours.
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Yakov,
I still see some of the tests fail on TC in ignite-1282 branch. Some of
them are related to branch-local changes, some of them are related to the
latest optimizations that were merged to ignite-1.5 (for example, there was
a deadlock in restart tests introduced by local collection synchronization
in MVCC manager).
I pushed the changes to TC, so I will give another update in a couple of
hours.
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Guys!
Let's update status info.
1. Data grid performance optimizations.
Most of the optimizations have been merged. However, there are several
pending ones
2. Direct marshalling compactions: communication optimization - Valentin
My understanding is that this will be merged in nearest hours. Valentin, is
that the case?
3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
The work is mostly done and ignite-1282 will be merged to release branch in
several hours. Alexey, please let us know when you are done.
4. Data grid performance optimizations: SQL queries - Sergi and Semyon
The problem here is that cache updates influence throughput of cache
operations. As far as I know Semyon has investigated this and found several
places in code that could cause this. My understanding is that he will
benchmark and merge this fix over the weekend.
Thanks!
--Yakov
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
One more update from my side:
- Merged all pending optimizations (*IGNITE-1917*)
- Fixed several minor bugs and performed several small refactorings in
binary serialization.
- Implemented one major optimization in deserialization logic decreasing
amount of reads in footer (*IGNITE-1961*). This finally allowed us to
outperform OptimziedMarshalled in almost all scenarios. Not merged yet,
need to perform more tests.
No blocking issues from my side for now which could prevent IGNITE-1282 ->
1.5 merge.
On Thu, Nov 19, 2015 at 10:19 PM, Vladimir Ozerov <vo...@gridgain.com>
wrote:
> My update about portable micro-optimizations:
> - Distributed benchmarks didn't show any statistically significant
> difference between my branch and 1282, results are sliiiiightly better. I
> believe the only way to feel improvements in serialization is to create
> benchmark which loads CPU well. Ignite Yardstick benchmarks cannot do that.
> - Tests are fine, so I will merge my optimizations tomorrow.
>
> In addition I am working on several other minor fixes to portables.
>
> On Thu, Nov 19, 2015 at 10:07 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> > wrote:
>
>> On Thu, Nov 19, 2015 at 10:59 AM, Raul Kripalani <ra...@apache.org>
>> wrote:
>>
>> > Can someone please clarify the *exact* release schedule?
>> >
>> > I hear that the merges may be completed tomorrow Friday, but the release
>> > will be built next Friday. Is this correct?
>> >
>> > I'm finishing my work on the OSGi integration (three modules), which I'd
>> > like to get into 1.5. I'm pretty much done, and I'm just finishing
>> > Javadocs, README, etc.
>> >
>> > I also want to create 2 unit tests for the two different classloading
>> > strategies I've built, but it'll require a bit of fiddling with Pax Exam
>> > and TinyBundles.
>> >
>>
>> Thanks Raul! I think the best approach for your changes would be to finish
>> them up first (including the documentation). Whenever done, I believe it
>> should be your call, whether you would consider it safe for these changes
>> to be merged.
>>
>>
>> >
>> > *Raúl Kripalani*
>> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
>> and
>> > Messaging Engineer
>> > http://about.me/raulkripalani |
>> http://www.linkedin.com/in/raulkripalani
>> > http://blog.raulkr.net | twitter: @raulvk
>> >
>> > On Thu, Nov 19, 2015 at 2:29 PM, Yakov Zhdanov <yz...@apache.org>
>> > wrote:
>> >
>> > > Hey guys!
>> > >
>> > > We are getting closer to the release! Thanks to everyone making this
>> > > closer!
>> > >
>> > > Let's update status info.
>> > >
>> > > My understanding is that the following major parts are still not
>> merged.
>> > > Can everyone mentioned provide ticket number(s) and estimates on when
>> the
>> > > functionality will be merged.
>> > >
>> > > 1. Data grid performance optimizations: single get/put - Semyon
>> > > 2. Direct marshalling compactions: communication optimization -
>> Valentin
>> > > 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
>> > > 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
>> > >
>> > > Thanks!
>> > >
>> > > --Yakov
>> > >
>> >
>>
>
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
My update about portable micro-optimizations:
- Distributed benchmarks didn't show any statistically significant
difference between my branch and 1282, results are sliiiiightly better. I
believe the only way to feel improvements in serialization is to create
benchmark which loads CPU well. Ignite Yardstick benchmarks cannot do that.
- Tests are fine, so I will merge my optimizations tomorrow.
In addition I am working on several other minor fixes to portables.
On Thu, Nov 19, 2015 at 10:07 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> On Thu, Nov 19, 2015 at 10:59 AM, Raul Kripalani <ra...@apache.org> wrote:
>
> > Can someone please clarify the *exact* release schedule?
> >
> > I hear that the merges may be completed tomorrow Friday, but the release
> > will be built next Friday. Is this correct?
> >
> > I'm finishing my work on the OSGi integration (three modules), which I'd
> > like to get into 1.5. I'm pretty much done, and I'm just finishing
> > Javadocs, README, etc.
> >
> > I also want to create 2 unit tests for the two different classloading
> > strategies I've built, but it'll require a bit of fiddling with Pax Exam
> > and TinyBundles.
> >
>
> Thanks Raul! I think the best approach for your changes would be to finish
> them up first (including the documentation). Whenever done, I believe it
> should be your call, whether you would consider it safe for these changes
> to be merged.
>
>
> >
> > *Raúl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Thu, Nov 19, 2015 at 2:29 PM, Yakov Zhdanov <yz...@apache.org>
> > wrote:
> >
> > > Hey guys!
> > >
> > > We are getting closer to the release! Thanks to everyone making this
> > > closer!
> > >
> > > Let's update status info.
> > >
> > > My understanding is that the following major parts are still not
> merged.
> > > Can everyone mentioned provide ticket number(s) and estimates on when
> the
> > > functionality will be merged.
> > >
> > > 1. Data grid performance optimizations: single get/put - Semyon
> > > 2. Direct marshalling compactions: communication optimization -
> Valentin
> > > 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
> > > 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
> > >
> > > Thanks!
> > >
> > > --Yakov
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Thu, Nov 19, 2015 at 10:59 AM, Raul Kripalani <ra...@apache.org> wrote:
> Can someone please clarify the *exact* release schedule?
>
> I hear that the merges may be completed tomorrow Friday, but the release
> will be built next Friday. Is this correct?
>
> I'm finishing my work on the OSGi integration (three modules), which I'd
> like to get into 1.5. I'm pretty much done, and I'm just finishing
> Javadocs, README, etc.
>
> I also want to create 2 unit tests for the two different classloading
> strategies I've built, but it'll require a bit of fiddling with Pax Exam
> and TinyBundles.
>
Thanks Raul! I think the best approach for your changes would be to finish
them up first (including the documentation). Whenever done, I believe it
should be your call, whether you would consider it safe for these changes
to be merged.
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Thu, Nov 19, 2015 at 2:29 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
> > Hey guys!
> >
> > We are getting closer to the release! Thanks to everyone making this
> > closer!
> >
> > Let's update status info.
> >
> > My understanding is that the following major parts are still not merged.
> > Can everyone mentioned provide ticket number(s) and estimates on when the
> > functionality will be merged.
> >
> > 1. Data grid performance optimizations: single get/put - Semyon
> > 2. Direct marshalling compactions: communication optimization - Valentin
> > 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
> > 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
> >
> > Thanks!
> >
> > --Yakov
> >
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
Can someone please clarify the *exact* release schedule?
I hear that the merges may be completed tomorrow Friday, but the release
will be built next Friday. Is this correct?
I'm finishing my work on the OSGi integration (three modules), which I'd
like to get into 1.5. I'm pretty much done, and I'm just finishing
Javadocs, README, etc.
I also want to create 2 unit tests for the two different classloading
strategies I've built, but it'll require a bit of fiddling with Pax Exam
and TinyBundles.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Nov 19, 2015 at 2:29 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Hey guys!
>
> We are getting closer to the release! Thanks to everyone making this
> closer!
>
> Let's update status info.
>
> My understanding is that the following major parts are still not merged.
> Can everyone mentioned provide ticket number(s) and estimates on when the
> functionality will be merged.
>
> 1. Data grid performance optimizations: single get/put - Semyon
> 2. Direct marshalling compactions: communication optimization - Valentin
> 3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
> 4. Data grid performance optimizations: SQL queries - Sergi and Semyon
>
> Thanks!
>
> --Yakov
>
Re: Ignite-1.5 Release
Posted by Nikolay Tikhonov <nt...@gridgain.com>.
I've merged changes related to IGNITE-426 (Make sure continuous queries
notifications are not missed in case primary node fails
) task.
On Thu, Nov 19, 2015 at 5:53 PM, Anton Vinogradov <av...@gridgain.com>
wrote:
> Twitter intergration
> *https://issues.apache.org/jira/browse/IGNITE-530
> <https://issues.apache.org/jira/browse/IGNITE-530>*
>
> is done too
>
> On Thu, Nov 19, 2015 at 5:32 PM, Semyon Boikov <sb...@gridgain.com>
> wrote:
>
> > Just merged single get optimizations (improvements in the last benchmarks
> > run: ~10% for atomic-put-get, ~5% for tx-put-get).
> >
>
Re: Ignite-1.5 Release
Posted by Anton Vinogradov <av...@gridgain.com>.
Twitter intergration
*https://issues.apache.org/jira/browse/IGNITE-530
<https://issues.apache.org/jira/browse/IGNITE-530>*
is done too
On Thu, Nov 19, 2015 at 5:32 PM, Semyon Boikov <sb...@gridgain.com> wrote:
> Just merged single get optimizations (improvements in the last benchmarks
> run: ~10% for atomic-put-get, ~5% for tx-put-get).
>
Re: Ignite-1.5 Release
Posted by Semyon Boikov <sb...@gridgain.com>.
Just merged single get optimizations (improvements in the last benchmarks
run: ~10% for atomic-put-get, ~5% for tx-put-get).
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Hey guys!
We are getting closer to the release! Thanks to everyone making this closer!
Let's update status info.
My understanding is that the following major parts are still not merged.
Can everyone mentioned provide ticket number(s) and estimates on when the
functionality will be merged.
1. Data grid performance optimizations: single get/put - Semyon
2. Direct marshalling compactions: communication optimization - Valentin
3. Introduce new binary format - Alexey Goncharuk and Vladimir Ozerov
4. Data grid performance optimizations: SQL queries - Sergi and Semyon
Thanks!
--Yakov
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
The code was already reviewed and merged with squash. IGNITE-1790.
On 19 Nov 2015 08:30, "Romain Gilles" <ro...@gmail.com> wrote:
> Hi Raul,
> Could you please give the pull request or the branch or the ignite ticket
> number?
> I will be please to have a look to your pull request.
>
> Thanks,
>
> Romain
>
> Le jeu. 19 nov. 2015 à 04:01, Dmitriy Setrakyan <ds...@apache.org> a
> écrit :
>
> > On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani <ra...@evosent.com>
> wrote:
> >
> > > I merged the Camel Streamer today and I hope to finish the first phase
> of
> > > OSGi tomorrow.
> > >
> > > I'll need someone to review the latter quickly if we want it merged for
> > > 1.5... No code changes in existing codebase. Just a new osgi module and
> > > many POM changes mainly to generate the manifests.
> > >
> >
> > Raul, did you create a patch or a PR? I can’t find it anywhere.
> >
> >
> > >
> > > Should be a quick task.
> > >
> > > Regards,
> > > Raúl.
> > > On 18 Nov 2015 20:38, "Vladimir Ozerov" <vo...@gridgain.com> wrote:
> > >
> > > > Hi Alex,
> > > >
> > > > Today I marged several big things into 1282 - reworked metadat and
> > > > compacted footers optimization. I have on big ticket left -
> > IGNITE-1917 -
> > > > with marshalling microoptimizations. They should not conflict with
> > > anything
> > > > and I expect them to be finalized tomorrow. All optimizations are
> > ready,
> > > I
> > > > just need to perform some cleanup and refactoring.
> > > >
> > > > On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> > > > alexey.goncharuk@gmail.com> wrote:
> > > >
> > > > > Hi folks,
> > > > >
> > > > > I merged performance optimizations for tx mode which gave up to 5%
> > > > > improvement for tx-put benchmark to ignite-1.5.
> > > > >
> > > > > I also pushed finalizaing changes to Binary configuration in
> > > ignite-1945
> > > > > branch and currently waiting for TC. If all is ok, will cooperate
> > with
> > > > > Vladimir Ozerov and merge changes tomorrow.
> > > > >
> > > > > 2015-11-18 17:58 GMT+03:00 Semyon Boikov <sb...@gridgain.com>:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Yesterday I merged optimizations for tx update operations working
> > > > single
> > > > > > key, got ~7% improvement in tx-put benchmark.
> > > > > >
> > > > > > And today I finished to implement optimization for cache 'get'
> > > > operation
> > > > > > with single key. Got another benchmark results improvements: ~10%
> > > with
> > > > > > atomic-put-get, ~5% with tx-put-get. Need to verify TC and
> > hopefully
> > > > will
> > > > > > merge these changes tomorrow.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Romain Gilles <ro...@gmail.com>.
Hi Raul,
Could you please give the pull request or the branch or the ignite ticket
number?
I will be please to have a look to your pull request.
Thanks,
Romain
Le jeu. 19 nov. 2015 à 04:01, Dmitriy Setrakyan <ds...@apache.org> a
écrit :
> On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani <ra...@evosent.com> wrote:
>
> > I merged the Camel Streamer today and I hope to finish the first phase of
> > OSGi tomorrow.
> >
> > I'll need someone to review the latter quickly if we want it merged for
> > 1.5... No code changes in existing codebase. Just a new osgi module and
> > many POM changes mainly to generate the manifests.
> >
>
> Raul, did you create a patch or a PR? I can’t find it anywhere.
>
>
> >
> > Should be a quick task.
> >
> > Regards,
> > Raúl.
> > On 18 Nov 2015 20:38, "Vladimir Ozerov" <vo...@gridgain.com> wrote:
> >
> > > Hi Alex,
> > >
> > > Today I marged several big things into 1282 - reworked metadat and
> > > compacted footers optimization. I have on big ticket left -
> IGNITE-1917 -
> > > with marshalling microoptimizations. They should not conflict with
> > anything
> > > and I expect them to be finalized tomorrow. All optimizations are
> ready,
> > I
> > > just need to perform some cleanup and refactoring.
> > >
> > > On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> > > alexey.goncharuk@gmail.com> wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I merged performance optimizations for tx mode which gave up to 5%
> > > > improvement for tx-put benchmark to ignite-1.5.
> > > >
> > > > I also pushed finalizaing changes to Binary configuration in
> > ignite-1945
> > > > branch and currently waiting for TC. If all is ok, will cooperate
> with
> > > > Vladimir Ozerov and merge changes tomorrow.
> > > >
> > > > 2015-11-18 17:58 GMT+03:00 Semyon Boikov <sb...@gridgain.com>:
> > > >
> > > > > Hi,
> > > > >
> > > > > Yesterday I merged optimizations for tx update operations working
> > > single
> > > > > key, got ~7% improvement in tx-put benchmark.
> > > > >
> > > > > And today I finished to implement optimization for cache 'get'
> > > operation
> > > > > with single key. Got another benchmark results improvements: ~10%
> > with
> > > > > atomic-put-get, ~5% with tx-put-get. Need to verify TC and
> hopefully
> > > will
> > > > > merge these changes tomorrow.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani <ra...@evosent.com> wrote:
> I merged the Camel Streamer today and I hope to finish the first phase of
> OSGi tomorrow.
>
> I'll need someone to review the latter quickly if we want it merged for
> 1.5... No code changes in existing codebase. Just a new osgi module and
> many POM changes mainly to generate the manifests.
>
Raul, did you create a patch or a PR? I can’t find it anywhere.
>
> Should be a quick task.
>
> Regards,
> Raúl.
> On 18 Nov 2015 20:38, "Vladimir Ozerov" <vo...@gridgain.com> wrote:
>
> > Hi Alex,
> >
> > Today I marged several big things into 1282 - reworked metadat and
> > compacted footers optimization. I have on big ticket left - IGNITE-1917 -
> > with marshalling microoptimizations. They should not conflict with
> anything
> > and I expect them to be finalized tomorrow. All optimizations are ready,
> I
> > just need to perform some cleanup and refactoring.
> >
> > On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> > alexey.goncharuk@gmail.com> wrote:
> >
> > > Hi folks,
> > >
> > > I merged performance optimizations for tx mode which gave up to 5%
> > > improvement for tx-put benchmark to ignite-1.5.
> > >
> > > I also pushed finalizaing changes to Binary configuration in
> ignite-1945
> > > branch and currently waiting for TC. If all is ok, will cooperate with
> > > Vladimir Ozerov and merge changes tomorrow.
> > >
> > > 2015-11-18 17:58 GMT+03:00 Semyon Boikov <sb...@gridgain.com>:
> > >
> > > > Hi,
> > > >
> > > > Yesterday I merged optimizations for tx update operations working
> > single
> > > > key, got ~7% improvement in tx-put benchmark.
> > > >
> > > > And today I finished to implement optimization for cache 'get'
> > operation
> > > > with single key. Got another benchmark results improvements: ~10%
> with
> > > > atomic-put-get, ~5% with tx-put-get. Need to verify TC and hopefully
> > will
> > > > merge these changes tomorrow.
> > > >
> > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@evosent.com>.
I merged the Camel Streamer today and I hope to finish the first phase of
OSGi tomorrow.
I'll need someone to review the latter quickly if we want it merged for
1.5... No code changes in existing codebase. Just a new osgi module and
many POM changes mainly to generate the manifests.
Should be a quick task.
Regards,
Raúl.
On 18 Nov 2015 20:38, "Vladimir Ozerov" <vo...@gridgain.com> wrote:
> Hi Alex,
>
> Today I marged several big things into 1282 - reworked metadat and
> compacted footers optimization. I have on big ticket left - IGNITE-1917 -
> with marshalling microoptimizations. They should not conflict with anything
> and I expect them to be finalized tomorrow. All optimizations are ready, I
> just need to perform some cleanup and refactoring.
>
> On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
> > Hi folks,
> >
> > I merged performance optimizations for tx mode which gave up to 5%
> > improvement for tx-put benchmark to ignite-1.5.
> >
> > I also pushed finalizaing changes to Binary configuration in ignite-1945
> > branch and currently waiting for TC. If all is ok, will cooperate with
> > Vladimir Ozerov and merge changes tomorrow.
> >
> > 2015-11-18 17:58 GMT+03:00 Semyon Boikov <sb...@gridgain.com>:
> >
> > > Hi,
> > >
> > > Yesterday I merged optimizations for tx update operations working
> single
> > > key, got ~7% improvement in tx-put benchmark.
> > >
> > > And today I finished to implement optimization for cache 'get'
> operation
> > > with single key. Got another benchmark results improvements: ~10% with
> > > atomic-put-get, ~5% with tx-put-get. Need to verify TC and hopefully
> will
> > > merge these changes tomorrow.
> > >
> > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Hi Alex,
Today I marged several big things into 1282 - reworked metadat and
compacted footers optimization. I have on big ticket left - IGNITE-1917 -
with marshalling microoptimizations. They should not conflict with anything
and I expect them to be finalized tomorrow. All optimizations are ready, I
just need to perform some cleanup and refactoring.
On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Hi folks,
>
> I merged performance optimizations for tx mode which gave up to 5%
> improvement for tx-put benchmark to ignite-1.5.
>
> I also pushed finalizaing changes to Binary configuration in ignite-1945
> branch and currently waiting for TC. If all is ok, will cooperate with
> Vladimir Ozerov and merge changes tomorrow.
>
> 2015-11-18 17:58 GMT+03:00 Semyon Boikov <sb...@gridgain.com>:
>
> > Hi,
> >
> > Yesterday I merged optimizations for tx update operations working single
> > key, got ~7% improvement in tx-put benchmark.
> >
> > And today I finished to implement optimization for cache 'get' operation
> > with single key. Got another benchmark results improvements: ~10% with
> > atomic-put-get, ~5% with tx-put-get. Need to verify TC and hopefully will
> > merge these changes tomorrow.
> >
> >
> >
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Hi folks,
I merged performance optimizations for tx mode which gave up to 5%
improvement for tx-put benchmark to ignite-1.5.
I also pushed finalizaing changes to Binary configuration in ignite-1945
branch and currently waiting for TC. If all is ok, will cooperate with
Vladimir Ozerov and merge changes tomorrow.
2015-11-18 17:58 GMT+03:00 Semyon Boikov <sb...@gridgain.com>:
> Hi,
>
> Yesterday I merged optimizations for tx update operations working single
> key, got ~7% improvement in tx-put benchmark.
>
> And today I finished to implement optimization for cache 'get' operation
> with single key. Got another benchmark results improvements: ~10% with
> atomic-put-get, ~5% with tx-put-get. Need to verify TC and hopefully will
> merge these changes tomorrow.
>
>
>
Re: Ignite-1.5 Release
Posted by Semyon Boikov <sb...@gridgain.com>.
Hi,
Yesterday I merged optimizations for tx update operations working single
key, got ~7% improvement in tx-put benchmark.
And today I finished to implement optimization for cache 'get' operation
with single key. Got another benchmark results improvements: ~10% with
atomic-put-get, ~5% with tx-put-get. Need to verify TC and hopefully will
merge these changes tomorrow.
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Guys,
Can everyone provide updates on ongoing issues status?
Vlad, I will review Semaphore tomorrow (Russian time).
Thanks!
--Yakov
2015-11-14 15:38 GMT+03:00 Denis Magda <dm...@gridgain.com>:
> Hi Vladislav,
>
> Most likely there is a minor issue in your test.
>
> I think Yakov would be able to run and check the test as a part of the
> ongoing review.
>
> Thanks,
>
> Denis
>
> On Friday, November 13, 2015, Vladisav Jelisavcic <vl...@gmail.com>
> wrote:
>
> > Hi Denis,
> >
> > Thanks a lot, it looks like my test setup was wrong,
> > I added semaphore tests to
> GridCacheAbstractDataStructuresFailoverSelfTest
> > suite.
> > Now I have following problem:
> > when I run tests with TOP_CHANGE_THREAD_CNT = 3
> > tests fail when they reach stop() with the following exception:
> >
> > class org.apache.ignite.internal.IgniteInterruptedCheckedException: Node
> is
> > stopping: 09c5e8b8-8998-468e-960d-223220354fd3
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStop0(GridCachePartitionExchangeManager.java:382)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:113)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:946)
> > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1823)
> > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1769)
> > at
> >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2133)
> > at
> >
> >
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2096)
> > at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:314)
> > at org.apache.ignite.Ignition.stop(Ignition.java:223)
> > at
> >
> >
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:802)
> > at
> >
> >
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:784)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.access$500(GridCacheAbstractDataStructuresFailoverSelfTest.java:54)
> > at
> >
> >
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest$5.apply(GridCacheAbstractDataStructuresFailoverSelfTest.java:459)
> >
> > When I run tests with TOP_CHANGE_THEAD_CNT = 1
> > everything is running ok;
> >
> >
> > @Yakov
> > I made a new commit to my IGNITE-638 branch,
> > can you please take a look?
> >
> >
> >
> > Best regards,
> > Vladisav
> >
> >
> >
> >
> > > On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <dmagda@gridgain.com
> > <javascript:;>> wrote:
> > >
> > > > Hi Vladislav,
> > > >
> > > > Please see below..
> > > >
> > > >
> > > > On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> > > >
> > > >> Yakov,
> > > >>
> > > >> sorry for running a bit late.
> > > >>
> > > >> Vladislav, do you have any updates for
> > > >>> https://issues.apache.org/jira/browse/IGNITE-638? Or any
> questions?
> > > >>>
> > > >>> --Yakov
> > > >>>
> > > >> I have problems with some fail-over scenarios;
> > > >> It seems that if the two nodes are in the middle of acquiring or
> > > releasing
> > > >> the semaphore,
> > > >> and one of them fails, all nodes get:
> > > >>
> > > >> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> > > >> <ignite-atomics-sys-cache> Failed to compare and set:
> > > >>
> > o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> > > >> class
> > > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > >> Failed to acquire lock for keys (primary node left grid, retry
> > > transaction
> > > >> if possible) [keys=[UserKeyCacheObjectImpl
> > [val=GridCacheInternalKeyImpl
> > > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > >> ...
> > > >> Caused by: class
> > > >> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > > Failed
> > > >> to acquire lock for keys (primary node left grid, retry transaction
> if
> > > >> possible) [keys=[UserKeyCacheObjectImpl
> [val=GridCacheInternalKeyImpl
> > > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > > >> at
> > > >>
> > > >>
> > >
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> > > >> ... 10 more
> > > >>
> > > > You have to process this exception manually at your implementation
> > layer
> > > > since your data structure uses a transactional cache.
> > > > Below is a kind of template I used when it was required to process
> this
> > > > and some other exeptions. You can use it as-is.
> > > >
> > > > int retries = GridCacheAdapter.MAX_RETRIES;
> > > >
> > > > IgniteCheckedException err =null;
> > > >
> > > > for (int i =0; i < retries; i++) {
> > > > try {
> > > > //Your transactional code that may fail
> > > > }
> > > > catch (IgniteCheckedException e) {
> > > > if (i == retries)
> > > > throw e;
> > > >
> > > > if (X.hasCause(e, ClusterTopologyCheckedException.class)) {
> > > > ClusterTopologyCheckedException topErr =
> > > > e.getCause(ClusterTopologyCheckedException.class);
> > > >
> > > > topErr.retryReadyFuture().get();
> > > > }
> > > > else if (X.hasCause(e,
> IgniteTxRollbackCheckedException.class))
> > > > U.sleep(1);
> > > > else throw e;
> > > > }
> > > > }
> > > >
> > > >
> > > >
> > > >> I'm still trying to find out how to exactly reproduce this behavior,
> > > >> I'll send you more details once I try few more things.
> > > >>
> > > > There is the test suite called
> > > > GridCacheAbstractDataStructuresFailoverSelfTest that checks Ignite
> > > atomics
> > > > and data structures with fail-over scenario.
> > > > The suite will let you reproduce ClusterTopologyCheckedException
> > easily.
> > > > Just add your tests there referring to the tests of other data
> > > structures.
> > > >
> > > > Presently I'm improving this test suite under my work on IGNITE-801
> and
> > > > IGNITE-803. If you finish your task earlier then I'll adopt your
> tests
> > > to a
> > > > new test approach.
> > > >
> > > >
> > > >> I am still using partitioned cache, does it make sense to use
> > replicated
> > > >> cache instead?
> > > >>
> > > >> Yeah, you should support this as well. Cache mode for the data
> > > structures
> > > > is changed using CollectionConfigurations while for atomics using
> > > > AtomicsConfiguration.
> > > >
> > > > --
> > > > Denis
> > > >
> > > >
> > > > Other than that, I'm done with everything else.
> > > >>
> > > >> Thanks,
> > > >> Vladisav
> > > >>
> > > >>
> > > >>
> > > >> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <raulk@apache.org
> > <javascript:;>>
> > > wrote:
> > > >>
> > > >> Sorry I haven't made an appearance in this thread yet.
> > > >>>
> > > >>> 6. MQTT streamer
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > > >>>>
> > > >>> Yes, it was merged to master before the ignite-1.5 was created.
> > > >>>
> > > >>> I'd like to add:
> > > >>>
> > > >>> Camel Streamer =>
> https://issues.apache.org/jira/browse/IGNITE-1790
> > > >>> -- I'll merge this as soon as I finished with the OSGi tickets with
> > > >>> demand.
> > > >>>
> > > >>> OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI
> (or
> > > >>> whatever agreement we arrive to in mailing lists and Wiki)
> > > >>> -- https://issues.apache.org/jira/browse/IGNITE-1527
> > > >>> -- https://issues.apache.org/jira/browse/IGNITE-1877
> > > >>> -- I'm working actively on these two features.
> > > >>>
> > > >>> *Raúl Kripalani*
> > > >>> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> Data
> > > and
> > > >>> Messaging Engineer
> > > >>> http://about.me/raulkripalani |
> > > http://www.linkedin.com/in/raulkripalani
> > > >>> http://blog.raulkr.net | twitter: @raulvk
> > > >>>
> > > >>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yzhdanov@apache.org
> > <javascript:;>>
> > > >>> wrote:
> > > >>>
> > > >>> Guys,
> > > >>>>
> > > >>>> I think we can start preparation to Ignite-1.5 release which will
> > > >>>> include
> > > >>>> many interesting features:
> > > >>>>
> > > >>>> 1. Portable object API
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-1486
> > > >>>>
> > > >>>> 2. Ignite.NET and Ignite C++
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-1282
> > > >>>>
> > > >>>> 3. Optimistic serializable transactions
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-1607
> > > >>>>
> > > >>>> 4. Distributed SQL joins - we will be able to query non-collocated
> > > data
> > > >>>>
> > > >>> as
> > > >>>
> > > >>>> well
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-1232
> > > >>>>
> > > >>>> 5. Enhanced Oracle and IBM JDK interoperability
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-1526
> > > >>>>
> > > >>>> 6. MQTT streamer
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > > >>>>
> > > >>>> 7. Continuous query failover
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-426
> > > >>>>
> > > >>>> 8. Significant transactional cache performance optimizations - I
> > will
> > > >>>>
> > > >>> merge
> > > >>>
> > > >>>> these changes from 'ignite-1.4-slow-server-debug' today or
> tomorrow.
> > > >>>>
> > > >>>> 9. Many stability and fault-tolerance fixes.
> > > >>>>
> > > >>>> 10. I would also like to include distributed Semaphore. Vladislav,
> > any
> > > >>>> chance you can finish with it this week?
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-
> > > >>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > >>>>
> > > >>>> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > issues,
> > > >>>> please respond to this email and let us know when can we expect
> your
> > > >>>> changes being merged to master and release branch?
> > > >>>>
> > > >>>> Can someone create ignite-1.5 release branch?
> > > >>>>
> > > >>>> --Yakov
> > > >>>>
> > > >>>>
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Denis Magda <dm...@gridgain.com>.
Hi Vladislav,
Most likely there is a minor issue in your test.
I think Yakov would be able to run and check the test as a part of the
ongoing review.
Thanks,
Denis
On Friday, November 13, 2015, Vladisav Jelisavcic <vl...@gmail.com>
wrote:
> Hi Denis,
>
> Thanks a lot, it looks like my test setup was wrong,
> I added semaphore tests to GridCacheAbstractDataStructuresFailoverSelfTest
> suite.
> Now I have following problem:
> when I run tests with TOP_CHANGE_THREAD_CNT = 3
> tests fail when they reach stop() with the following exception:
>
> class org.apache.ignite.internal.IgniteInterruptedCheckedException: Node is
> stopping: 09c5e8b8-8998-468e-960d-223220354fd3
> at
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStop0(GridCachePartitionExchangeManager.java:382)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:113)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:946)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1823)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1769)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2133)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2096)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:314)
> at org.apache.ignite.Ignition.stop(Ignition.java:223)
> at
>
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:802)
> at
>
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:784)
> at
>
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.access$500(GridCacheAbstractDataStructuresFailoverSelfTest.java:54)
> at
>
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest$5.apply(GridCacheAbstractDataStructuresFailoverSelfTest.java:459)
>
> When I run tests with TOP_CHANGE_THEAD_CNT = 1
> everything is running ok;
>
>
> @Yakov
> I made a new commit to my IGNITE-638 branch,
> can you please take a look?
>
>
>
> Best regards,
> Vladisav
>
>
>
>
> > On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <dmagda@gridgain.com
> <javascript:;>> wrote:
> >
> > > Hi Vladislav,
> > >
> > > Please see below..
> > >
> > >
> > > On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> > >
> > >> Yakov,
> > >>
> > >> sorry for running a bit late.
> > >>
> > >> Vladislav, do you have any updates for
> > >>> https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
> > >>>
> > >>> --Yakov
> > >>>
> > >> I have problems with some fail-over scenarios;
> > >> It seems that if the two nodes are in the middle of acquiring or
> > releasing
> > >> the semaphore,
> > >> and one of them fails, all nodes get:
> > >>
> > >> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> > >> <ignite-atomics-sys-cache> Failed to compare and set:
> > >>
> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> > >> class
> > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > >> Failed to acquire lock for keys (primary node left grid, retry
> > transaction
> > >> if possible) [keys=[UserKeyCacheObjectImpl
> [val=GridCacheInternalKeyImpl
> > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > >> ...
> > >> Caused by: class
> > >> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > Failed
> > >> to acquire lock for keys (primary node left grid, retry transaction if
> > >> possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > >> at
> > >>
> > >>
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> > >> ... 10 more
> > >>
> > > You have to process this exception manually at your implementation
> layer
> > > since your data structure uses a transactional cache.
> > > Below is a kind of template I used when it was required to process this
> > > and some other exeptions. You can use it as-is.
> > >
> > > int retries = GridCacheAdapter.MAX_RETRIES;
> > >
> > > IgniteCheckedException err =null;
> > >
> > > for (int i =0; i < retries; i++) {
> > > try {
> > > //Your transactional code that may fail
> > > }
> > > catch (IgniteCheckedException e) {
> > > if (i == retries)
> > > throw e;
> > >
> > > if (X.hasCause(e, ClusterTopologyCheckedException.class)) {
> > > ClusterTopologyCheckedException topErr =
> > > e.getCause(ClusterTopologyCheckedException.class);
> > >
> > > topErr.retryReadyFuture().get();
> > > }
> > > else if (X.hasCause(e, IgniteTxRollbackCheckedException.class))
> > > U.sleep(1);
> > > else throw e;
> > > }
> > > }
> > >
> > >
> > >
> > >> I'm still trying to find out how to exactly reproduce this behavior,
> > >> I'll send you more details once I try few more things.
> > >>
> > > There is the test suite called
> > > GridCacheAbstractDataStructuresFailoverSelfTest that checks Ignite
> > atomics
> > > and data structures with fail-over scenario.
> > > The suite will let you reproduce ClusterTopologyCheckedException
> easily.
> > > Just add your tests there referring to the tests of other data
> > structures.
> > >
> > > Presently I'm improving this test suite under my work on IGNITE-801 and
> > > IGNITE-803. If you finish your task earlier then I'll adopt your tests
> > to a
> > > new test approach.
> > >
> > >
> > >> I am still using partitioned cache, does it make sense to use
> replicated
> > >> cache instead?
> > >>
> > >> Yeah, you should support this as well. Cache mode for the data
> > structures
> > > is changed using CollectionConfigurations while for atomics using
> > > AtomicsConfiguration.
> > >
> > > --
> > > Denis
> > >
> > >
> > > Other than that, I'm done with everything else.
> > >>
> > >> Thanks,
> > >> Vladisav
> > >>
> > >>
> > >>
> > >> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <raulk@apache.org
> <javascript:;>>
> > wrote:
> > >>
> > >> Sorry I haven't made an appearance in this thread yet.
> > >>>
> > >>> 6. MQTT streamer
> > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > >>>>
> > >>> Yes, it was merged to master before the ignite-1.5 was created.
> > >>>
> > >>> I'd like to add:
> > >>>
> > >>> Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
> > >>> -- I'll merge this as soon as I finished with the OSGi tickets with
> > >>> demand.
> > >>>
> > >>> OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI (or
> > >>> whatever agreement we arrive to in mailing lists and Wiki)
> > >>> -- https://issues.apache.org/jira/browse/IGNITE-1527
> > >>> -- https://issues.apache.org/jira/browse/IGNITE-1877
> > >>> -- I'm working actively on these two features.
> > >>>
> > >>> *Raúl Kripalani*
> > >>> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> > and
> > >>> Messaging Engineer
> > >>> http://about.me/raulkripalani |
> > http://www.linkedin.com/in/raulkripalani
> > >>> http://blog.raulkr.net | twitter: @raulvk
> > >>>
> > >>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yzhdanov@apache.org
> <javascript:;>>
> > >>> wrote:
> > >>>
> > >>> Guys,
> > >>>>
> > >>>> I think we can start preparation to Ignite-1.5 release which will
> > >>>> include
> > >>>> many interesting features:
> > >>>>
> > >>>> 1. Portable object API
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1486
> > >>>>
> > >>>> 2. Ignite.NET and Ignite C++
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1282
> > >>>>
> > >>>> 3. Optimistic serializable transactions
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1607
> > >>>>
> > >>>> 4. Distributed SQL joins - we will be able to query non-collocated
> > data
> > >>>>
> > >>> as
> > >>>
> > >>>> well
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1232
> > >>>>
> > >>>> 5. Enhanced Oracle and IBM JDK interoperability
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1526
> > >>>>
> > >>>> 6. MQTT streamer
> > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > >>>>
> > >>>> 7. Continuous query failover
> > >>>> https://issues.apache.org/jira/browse/IGNITE-426
> > >>>>
> > >>>> 8. Significant transactional cache performance optimizations - I
> will
> > >>>>
> > >>> merge
> > >>>
> > >>>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > >>>>
> > >>>> 9. Many stability and fault-tolerance fixes.
> > >>>>
> > >>>> 10. I would also like to include distributed Semaphore. Vladislav,
> any
> > >>>> chance you can finish with it this week?
> > >>>> https://issues.apache.org/jira/browse/IGNITE-
> > >>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > >>>>
> > >>>> Thanks to everyone involved! Guys, esp. assignees of mentioned
> issues,
> > >>>> please respond to this email and let us know when can we expect your
> > >>>> changes being merged to master and release branch?
> > >>>>
> > >>>> Can someone create ignite-1.5 release branch?
> > >>>>
> > >>>> --Yakov
> > >>>>
> > >>>>
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Folks,
I am working on portable marshalling performance at the moment. I took a
scenario which is good for OptimziedMarshaller and is very unfortunate for
PortableMarshaller: object with 40 int fields.
My idea here is that this scenario is so bad for Portable, so that in the
vast majority of sensible real-life scenarios it will show better relative
numbers.
*Marshalling*
Initially I got the following numbers:
Optimized: 1.9KK/sec
Portable: *0.7KK/sec*
Applied several optimizations:
- Removed reflection and boxing for primitive fields
- Removed some garbage (e.g. arrays instead of Collections)
- Decreased amount of thread-local lookups
Results after this:
Optimized: 1.9KK/sec
Portable: *1.2KK/sec*
Further profiling shows that now the most amount of time is spend in footer
preparation and write. I have some ideas how to improve it further, will
check them soon, what will hopefully bring us to ~1.5KK/sec. We will not be
faster than "optimized" here, though.
*Unmarshalling*
Initial measurements:
Optimized: 3KK/sec
Portable: *0.6KK/sec, 5 times slower*
Will start working on this on soon. There is a lot of optos here, some of
them already battle-tested in .Net, so I expect we will be able to get
~2KK/sec once they are applied.
On Fri, Nov 13, 2015 at 4:43 PM, Vladisav Jelisavcic <vl...@gmail.com>
wrote:
> Hi Denis,
>
> Thanks a lot, it looks like my test setup was wrong,
> I added semaphore tests to GridCacheAbstractDataStructuresFailoverSelfTest
> suite.
> Now I have following problem:
> when I run tests with TOP_CHANGE_THREAD_CNT = 3
> tests fail when they reach stop() with the following exception:
>
> class org.apache.ignite.internal.IgniteInterruptedCheckedException: Node is
> stopping: 09c5e8b8-8998-468e-960d-223220354fd3
> at
>
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStop0(GridCachePartitionExchangeManager.java:382)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:113)
> at
>
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:946)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1823)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1769)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2133)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2096)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:314)
> at org.apache.ignite.Ignition.stop(Ignition.java:223)
> at
>
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:802)
> at
>
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:784)
> at
>
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.access$500(GridCacheAbstractDataStructuresFailoverSelfTest.java:54)
> at
>
> org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest$5.apply(GridCacheAbstractDataStructuresFailoverSelfTest.java:459)
>
> When I run tests with TOP_CHANGE_THEAD_CNT = 1
> everything is running ok;
>
>
> @Yakov
> I made a new commit to my IGNITE-638 branch,
> can you please take a look?
>
>
>
> Best regards,
> Vladisav
>
>
>
>
> > On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <dm...@gridgain.com>
> wrote:
> >
> > > Hi Vladislav,
> > >
> > > Please see below..
> > >
> > >
> > > On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> > >
> > >> Yakov,
> > >>
> > >> sorry for running a bit late.
> > >>
> > >> Vladislav, do you have any updates for
> > >>> https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
> > >>>
> > >>> --Yakov
> > >>>
> > >> I have problems with some fail-over scenarios;
> > >> It seems that if the two nodes are in the middle of acquiring or
> > releasing
> > >> the semaphore,
> > >> and one of them fails, all nodes get:
> > >>
> > >> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> > >> <ignite-atomics-sys-cache> Failed to compare and set:
> > >>
> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> > >> class
> > org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > >> Failed to acquire lock for keys (primary node left grid, retry
> > transaction
> > >> if possible) [keys=[UserKeyCacheObjectImpl
> [val=GridCacheInternalKeyImpl
> > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > >> ...
> > >> Caused by: class
> > >> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> > Failed
> > >> to acquire lock for keys (primary node left grid, retry transaction if
> > >> possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> > >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> > >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> > >> at
> > >>
> > >>
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> > >> ... 10 more
> > >>
> > > You have to process this exception manually at your implementation
> layer
> > > since your data structure uses a transactional cache.
> > > Below is a kind of template I used when it was required to process this
> > > and some other exeptions. You can use it as-is.
> > >
> > > int retries = GridCacheAdapter.MAX_RETRIES;
> > >
> > > IgniteCheckedException err =null;
> > >
> > > for (int i =0; i < retries; i++) {
> > > try {
> > > //Your transactional code that may fail
> > > }
> > > catch (IgniteCheckedException e) {
> > > if (i == retries)
> > > throw e;
> > >
> > > if (X.hasCause(e, ClusterTopologyCheckedException.class)) {
> > > ClusterTopologyCheckedException topErr =
> > > e.getCause(ClusterTopologyCheckedException.class);
> > >
> > > topErr.retryReadyFuture().get();
> > > }
> > > else if (X.hasCause(e, IgniteTxRollbackCheckedException.class))
> > > U.sleep(1);
> > > else throw e;
> > > }
> > > }
> > >
> > >
> > >
> > >> I'm still trying to find out how to exactly reproduce this behavior,
> > >> I'll send you more details once I try few more things.
> > >>
> > > There is the test suite called
> > > GridCacheAbstractDataStructuresFailoverSelfTest that checks Ignite
> > atomics
> > > and data structures with fail-over scenario.
> > > The suite will let you reproduce ClusterTopologyCheckedException
> easily.
> > > Just add your tests there referring to the tests of other data
> > structures.
> > >
> > > Presently I'm improving this test suite under my work on IGNITE-801 and
> > > IGNITE-803. If you finish your task earlier then I'll adopt your tests
> > to a
> > > new test approach.
> > >
> > >
> > >> I am still using partitioned cache, does it make sense to use
> replicated
> > >> cache instead?
> > >>
> > >> Yeah, you should support this as well. Cache mode for the data
> > structures
> > > is changed using CollectionConfigurations while for atomics using
> > > AtomicsConfiguration.
> > >
> > > --
> > > Denis
> > >
> > >
> > > Other than that, I'm done with everything else.
> > >>
> > >> Thanks,
> > >> Vladisav
> > >>
> > >>
> > >>
> > >> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <ra...@apache.org>
> > wrote:
> > >>
> > >> Sorry I haven't made an appearance in this thread yet.
> > >>>
> > >>> 6. MQTT streamer
> > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > >>>>
> > >>> Yes, it was merged to master before the ignite-1.5 was created.
> > >>>
> > >>> I'd like to add:
> > >>>
> > >>> Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
> > >>> -- I'll merge this as soon as I finished with the OSGi tickets with
> > >>> demand.
> > >>>
> > >>> OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI (or
> > >>> whatever agreement we arrive to in mailing lists and Wiki)
> > >>> -- https://issues.apache.org/jira/browse/IGNITE-1527
> > >>> -- https://issues.apache.org/jira/browse/IGNITE-1877
> > >>> -- I'm working actively on these two features.
> > >>>
> > >>> *Raúl Kripalani*
> > >>> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> > and
> > >>> Messaging Engineer
> > >>> http://about.me/raulkripalani |
> > http://www.linkedin.com/in/raulkripalani
> > >>> http://blog.raulkr.net | twitter: @raulvk
> > >>>
> > >>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yz...@apache.org>
> > >>> wrote:
> > >>>
> > >>> Guys,
> > >>>>
> > >>>> I think we can start preparation to Ignite-1.5 release which will
> > >>>> include
> > >>>> many interesting features:
> > >>>>
> > >>>> 1. Portable object API
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1486
> > >>>>
> > >>>> 2. Ignite.NET and Ignite C++
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1282
> > >>>>
> > >>>> 3. Optimistic serializable transactions
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1607
> > >>>>
> > >>>> 4. Distributed SQL joins - we will be able to query non-collocated
> > data
> > >>>>
> > >>> as
> > >>>
> > >>>> well
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1232
> > >>>>
> > >>>> 5. Enhanced Oracle and IBM JDK interoperability
> > >>>> https://issues.apache.org/jira/browse/IGNITE-1526
> > >>>>
> > >>>> 6. MQTT streamer
> > >>>> https://issues.apache.org/jira/browse/IGNITE-535
> > >>>>
> > >>>> 7. Continuous query failover
> > >>>> https://issues.apache.org/jira/browse/IGNITE-426
> > >>>>
> > >>>> 8. Significant transactional cache performance optimizations - I
> will
> > >>>>
> > >>> merge
> > >>>
> > >>>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > >>>>
> > >>>> 9. Many stability and fault-tolerance fixes.
> > >>>>
> > >>>> 10. I would also like to include distributed Semaphore. Vladislav,
> any
> > >>>> chance you can finish with it this week?
> > >>>> https://issues.apache.org/jira/browse/IGNITE-
> > >>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > >>>>
> > >>>> Thanks to everyone involved! Guys, esp. assignees of mentioned
> issues,
> > >>>> please respond to this email and let us know when can we expect your
> > >>>> changes being merged to master and release branch?
> > >>>>
> > >>>> Can someone create ignite-1.5 release branch?
> > >>>>
> > >>>> --Yakov
> > >>>>
> > >>>>
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Vladisav Jelisavcic <vl...@gmail.com>.
Hi Denis,
Thanks a lot, it looks like my test setup was wrong,
I added semaphore tests to GridCacheAbstractDataStructuresFailoverSelfTest
suite.
Now I have following problem:
when I run tests with TOP_CHANGE_THREAD_CNT = 3
tests fail when they reach stop() with the following exception:
class org.apache.ignite.internal.IgniteInterruptedCheckedException: Node is
stopping: 09c5e8b8-8998-468e-960d-223220354fd3
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.onKernalStop0(GridCachePartitionExchangeManager.java:382)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.onKernalStop(GridCacheSharedManagerAdapter.java:113)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:946)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:1823)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:1769)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2133)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2096)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:314)
at org.apache.ignite.Ignition.stop(Ignition.java:223)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:802)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:784)
at
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.access$500(GridCacheAbstractDataStructuresFailoverSelfTest.java:54)
at
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest$5.apply(GridCacheAbstractDataStructuresFailoverSelfTest.java:459)
When I run tests with TOP_CHANGE_THEAD_CNT = 1
everything is running ok;
@Yakov
I made a new commit to my IGNITE-638 branch,
can you please take a look?
Best regards,
Vladisav
> On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <dm...@gridgain.com> wrote:
>
> > Hi Vladislav,
> >
> > Please see below..
> >
> >
> > On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> >
> >> Yakov,
> >>
> >> sorry for running a bit late.
> >>
> >> Vladislav, do you have any updates for
> >>> https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
> >>>
> >>> --Yakov
> >>>
> >> I have problems with some fail-over scenarios;
> >> It seems that if the two nodes are in the middle of acquiring or
> releasing
> >> the semaphore,
> >> and one of them fails, all nodes get:
> >>
> >> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> >> <ignite-atomics-sys-cache> Failed to compare and set:
> >> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> >> class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> >> Failed to acquire lock for keys (primary node left grid, retry
> transaction
> >> if possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> >> ...
> >> Caused by: class
> >> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> Failed
> >> to acquire lock for keys (primary node left grid, retry transaction if
> >> possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> >> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> >> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> >> at
> >>
> >>
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> >> ... 10 more
> >>
> > You have to process this exception manually at your implementation layer
> > since your data structure uses a transactional cache.
> > Below is a kind of template I used when it was required to process this
> > and some other exeptions. You can use it as-is.
> >
> > int retries = GridCacheAdapter.MAX_RETRIES;
> >
> > IgniteCheckedException err =null;
> >
> > for (int i =0; i < retries; i++) {
> > try {
> > //Your transactional code that may fail
> > }
> > catch (IgniteCheckedException e) {
> > if (i == retries)
> > throw e;
> >
> > if (X.hasCause(e, ClusterTopologyCheckedException.class)) {
> > ClusterTopologyCheckedException topErr =
> > e.getCause(ClusterTopologyCheckedException.class);
> >
> > topErr.retryReadyFuture().get();
> > }
> > else if (X.hasCause(e, IgniteTxRollbackCheckedException.class))
> > U.sleep(1);
> > else throw e;
> > }
> > }
> >
> >
> >
> >> I'm still trying to find out how to exactly reproduce this behavior,
> >> I'll send you more details once I try few more things.
> >>
> > There is the test suite called
> > GridCacheAbstractDataStructuresFailoverSelfTest that checks Ignite
> atomics
> > and data structures with fail-over scenario.
> > The suite will let you reproduce ClusterTopologyCheckedException easily.
> > Just add your tests there referring to the tests of other data
> structures.
> >
> > Presently I'm improving this test suite under my work on IGNITE-801 and
> > IGNITE-803. If you finish your task earlier then I'll adopt your tests
> to a
> > new test approach.
> >
> >
> >> I am still using partitioned cache, does it make sense to use replicated
> >> cache instead?
> >>
> >> Yeah, you should support this as well. Cache mode for the data
> structures
> > is changed using CollectionConfigurations while for atomics using
> > AtomicsConfiguration.
> >
> > --
> > Denis
> >
> >
> > Other than that, I'm done with everything else.
> >>
> >> Thanks,
> >> Vladisav
> >>
> >>
> >>
> >> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <ra...@apache.org>
> wrote:
> >>
> >> Sorry I haven't made an appearance in this thread yet.
> >>>
> >>> 6. MQTT streamer
> >>>> https://issues.apache.org/jira/browse/IGNITE-535
> >>>>
> >>> Yes, it was merged to master before the ignite-1.5 was created.
> >>>
> >>> I'd like to add:
> >>>
> >>> Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
> >>> -- I'll merge this as soon as I finished with the OSGi tickets with
> >>> demand.
> >>>
> >>> OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI (or
> >>> whatever agreement we arrive to in mailing lists and Wiki)
> >>> -- https://issues.apache.org/jira/browse/IGNITE-1527
> >>> -- https://issues.apache.org/jira/browse/IGNITE-1877
> >>> -- I'm working actively on these two features.
> >>>
> >>> *Raúl Kripalani*
> >>> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data
> and
> >>> Messaging Engineer
> >>> http://about.me/raulkripalani |
> http://www.linkedin.com/in/raulkripalani
> >>> http://blog.raulkr.net | twitter: @raulvk
> >>>
> >>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yz...@apache.org>
> >>> wrote:
> >>>
> >>> Guys,
> >>>>
> >>>> I think we can start preparation to Ignite-1.5 release which will
> >>>> include
> >>>> many interesting features:
> >>>>
> >>>> 1. Portable object API
> >>>> https://issues.apache.org/jira/browse/IGNITE-1486
> >>>>
> >>>> 2. Ignite.NET and Ignite C++
> >>>> https://issues.apache.org/jira/browse/IGNITE-1282
> >>>>
> >>>> 3. Optimistic serializable transactions
> >>>> https://issues.apache.org/jira/browse/IGNITE-1607
> >>>>
> >>>> 4. Distributed SQL joins - we will be able to query non-collocated
> data
> >>>>
> >>> as
> >>>
> >>>> well
> >>>> https://issues.apache.org/jira/browse/IGNITE-1232
> >>>>
> >>>> 5. Enhanced Oracle and IBM JDK interoperability
> >>>> https://issues.apache.org/jira/browse/IGNITE-1526
> >>>>
> >>>> 6. MQTT streamer
> >>>> https://issues.apache.org/jira/browse/IGNITE-535
> >>>>
> >>>> 7. Continuous query failover
> >>>> https://issues.apache.org/jira/browse/IGNITE-426
> >>>>
> >>>> 8. Significant transactional cache performance optimizations - I will
> >>>>
> >>> merge
> >>>
> >>>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> >>>>
> >>>> 9. Many stability and fault-tolerance fixes.
> >>>>
> >>>> 10. I would also like to include distributed Semaphore. Vladislav, any
> >>>> chance you can finish with it this week?
> >>>> https://issues.apache.org/jira/browse/IGNITE-
> >>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
> >>>>
> >>>> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> >>>> please respond to this email and let us know when can we expect your
> >>>> changes being merged to master and release branch?
> >>>>
> >>>> Can someone create ignite-1.5 release branch?
> >>>>
> >>>> --Yakov
> >>>>
> >>>>
> >
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
At the moment I am getting closer to finish with IGNITE-1816 - optional
compaction of portable object footers. In general feature works. In the
nearest time I am going to perform some microbenchmarks to understand
implications. Two things left:
- I have to rework lots of binary object unit tests because they were
designed to run with disabled metadata, and compact footers require
metadata.
- Need to add cross-node validation.
On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <dm...@gridgain.com> wrote:
> Hi Vladislav,
>
> Please see below..
>
>
> On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
>
>> Yakov,
>>
>> sorry for running a bit late.
>>
>> Vladislav, do you have any updates for
>>> https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
>>>
>>> --Yakov
>>>
>> I have problems with some fail-over scenarios;
>> It seems that if the two nodes are in the middle of acquiring or releasing
>> the semaphore,
>> and one of them fails, all nodes get:
>>
>> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
>> <ignite-atomics-sys-cache> Failed to compare and set:
>> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
>> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
>> Failed to acquire lock for keys (primary node left grid, retry transaction
>> if possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
>> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
>> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
>> ...
>> Caused by: class
>> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed
>> to acquire lock for keys (primary node left grid, retry transaction if
>> possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
>> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
>> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
>> at
>>
>> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
>> ... 10 more
>>
> You have to process this exception manually at your implementation layer
> since your data structure uses a transactional cache.
> Below is a kind of template I used when it was required to process this
> and some other exeptions. You can use it as-is.
>
> int retries = GridCacheAdapter.MAX_RETRIES;
>
> IgniteCheckedException err =null;
>
> for (int i =0; i < retries; i++) {
> try {
> //Your transactional code that may fail
> }
> catch (IgniteCheckedException e) {
> if (i == retries)
> throw e;
>
> if (X.hasCause(e, ClusterTopologyCheckedException.class)) {
> ClusterTopologyCheckedException topErr =
> e.getCause(ClusterTopologyCheckedException.class);
>
> topErr.retryReadyFuture().get();
> }
> else if (X.hasCause(e, IgniteTxRollbackCheckedException.class))
> U.sleep(1);
> else throw e;
> }
> }
>
>
>
>> I'm still trying to find out how to exactly reproduce this behavior,
>> I'll send you more details once I try few more things.
>>
> There is the test suite called
> GridCacheAbstractDataStructuresFailoverSelfTest that checks Ignite atomics
> and data structures with fail-over scenario.
> The suite will let you reproduce ClusterTopologyCheckedException easily.
> Just add your tests there referring to the tests of other data structures.
>
> Presently I'm improving this test suite under my work on IGNITE-801 and
> IGNITE-803. If you finish your task earlier then I'll adopt your tests to a
> new test approach.
>
>
>> I am still using partitioned cache, does it make sense to use replicated
>> cache instead?
>>
>> Yeah, you should support this as well. Cache mode for the data structures
> is changed using CollectionConfigurations while for atomics using
> AtomicsConfiguration.
>
> --
> Denis
>
>
> Other than that, I'm done with everything else.
>>
>> Thanks,
>> Vladisav
>>
>>
>>
>> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <ra...@apache.org> wrote:
>>
>> Sorry I haven't made an appearance in this thread yet.
>>>
>>> 6. MQTT streamer
>>>> https://issues.apache.org/jira/browse/IGNITE-535
>>>>
>>> Yes, it was merged to master before the ignite-1.5 was created.
>>>
>>> I'd like to add:
>>>
>>> Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
>>> -- I'll merge this as soon as I finished with the OSGi tickets with
>>> demand.
>>>
>>> OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI (or
>>> whatever agreement we arrive to in mailing lists and Wiki)
>>> -- https://issues.apache.org/jira/browse/IGNITE-1527
>>> -- https://issues.apache.org/jira/browse/IGNITE-1877
>>> -- I'm working actively on these two features.
>>>
>>> *Raúl Kripalani*
>>> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
>>> Messaging Engineer
>>> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
>>> http://blog.raulkr.net | twitter: @raulvk
>>>
>>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yz...@apache.org>
>>> wrote:
>>>
>>> Guys,
>>>>
>>>> I think we can start preparation to Ignite-1.5 release which will
>>>> include
>>>> many interesting features:
>>>>
>>>> 1. Portable object API
>>>> https://issues.apache.org/jira/browse/IGNITE-1486
>>>>
>>>> 2. Ignite.NET and Ignite C++
>>>> https://issues.apache.org/jira/browse/IGNITE-1282
>>>>
>>>> 3. Optimistic serializable transactions
>>>> https://issues.apache.org/jira/browse/IGNITE-1607
>>>>
>>>> 4. Distributed SQL joins - we will be able to query non-collocated data
>>>>
>>> as
>>>
>>>> well
>>>> https://issues.apache.org/jira/browse/IGNITE-1232
>>>>
>>>> 5. Enhanced Oracle and IBM JDK interoperability
>>>> https://issues.apache.org/jira/browse/IGNITE-1526
>>>>
>>>> 6. MQTT streamer
>>>> https://issues.apache.org/jira/browse/IGNITE-535
>>>>
>>>> 7. Continuous query failover
>>>> https://issues.apache.org/jira/browse/IGNITE-426
>>>>
>>>> 8. Significant transactional cache performance optimizations - I will
>>>>
>>> merge
>>>
>>>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>>>>
>>>> 9. Many stability and fault-tolerance fixes.
>>>>
>>>> 10. I would also like to include distributed Semaphore. Vladislav, any
>>>> chance you can finish with it this week?
>>>> https://issues.apache.org/jira/browse/IGNITE-
>>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
>>>>
>>>> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
>>>> please respond to this email and let us know when can we expect your
>>>> changes being merged to master and release branch?
>>>>
>>>> Can someone create ignite-1.5 release branch?
>>>>
>>>> --Yakov
>>>>
>>>>
>
Re: Ignite-1.5 Release
Posted by Denis Magda <dm...@gridgain.com>.
Hi Vladislav,
Please see below..
On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> Yakov,
>
> sorry for running a bit late.
>
>> Vladislav, do you have any updates for
>> https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
>>
>> --Yakov
> I have problems with some fail-over scenarios;
> It seems that if the two nodes are in the middle of acquiring or releasing
> the semaphore,
> and one of them fails, all nodes get:
>
> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> <ignite-atomics-sys-cache> Failed to compare and set:
> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> Failed to acquire lock for keys (primary node left grid, retry transaction
> if possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> ...
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed
> to acquire lock for keys (primary node left grid, retry transaction if
> possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> ... 10 more
You have to process this exception manually at your implementation layer
since your data structure uses a transactional cache.
Below is a kind of template I used when it was required to process this
and some other exeptions. You can use it as-is.
int retries = GridCacheAdapter.MAX_RETRIES;
IgniteCheckedException err =null;
for (int i =0; i < retries; i++) {
try {
//Your transactional code that may fail
}
catch (IgniteCheckedException e) {
if (i == retries)
throw e;
if (X.hasCause(e, ClusterTopologyCheckedException.class)) {
ClusterTopologyCheckedException topErr = e.getCause(ClusterTopologyCheckedException.class);
topErr.retryReadyFuture().get();
}
else if (X.hasCause(e, IgniteTxRollbackCheckedException.class))
U.sleep(1);
else throw e;
}
}
>
> I'm still trying to find out how to exactly reproduce this behavior,
> I'll send you more details once I try few more things.
There is the test suite called
GridCacheAbstractDataStructuresFailoverSelfTest that checks Ignite
atomics and data structures with fail-over scenario.
The suite will let you reproduce ClusterTopologyCheckedException easily.
Just add your tests there referring to the tests of other data structures.
Presently I'm improving this test suite under my work on IGNITE-801 and
IGNITE-803. If you finish your task earlier then I'll adopt your tests
to a new test approach.
>
> I am still using partitioned cache, does it make sense to use replicated
> cache instead?
>
Yeah, you should support this as well. Cache mode for the data
structures is changed using CollectionConfigurations while for atomics
using AtomicsConfiguration.
--
Denis
> Other than that, I'm done with everything else.
>
> Thanks,
> Vladisav
>
>
>
> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <ra...@apache.org> wrote:
>
>> Sorry I haven't made an appearance in this thread yet.
>>
>>> 6. MQTT streamer
>>> https://issues.apache.org/jira/browse/IGNITE-535
>> Yes, it was merged to master before the ignite-1.5 was created.
>>
>> I'd like to add:
>>
>> Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
>> -- I'll merge this as soon as I finished with the OSGi tickets with demand.
>>
>> OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI (or
>> whatever agreement we arrive to in mailing lists and Wiki)
>> -- https://issues.apache.org/jira/browse/IGNITE-1527
>> -- https://issues.apache.org/jira/browse/IGNITE-1877
>> -- I'm working actively on these two features.
>>
>> *Raúl Kripalani*
>> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
>> Messaging Engineer
>> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
>> http://blog.raulkr.net | twitter: @raulvk
>>
>> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yz...@apache.org> wrote:
>>
>>> Guys,
>>>
>>> I think we can start preparation to Ignite-1.5 release which will include
>>> many interesting features:
>>>
>>> 1. Portable object API
>>> https://issues.apache.org/jira/browse/IGNITE-1486
>>>
>>> 2. Ignite.NET and Ignite C++
>>> https://issues.apache.org/jira/browse/IGNITE-1282
>>>
>>> 3. Optimistic serializable transactions
>>> https://issues.apache.org/jira/browse/IGNITE-1607
>>>
>>> 4. Distributed SQL joins - we will be able to query non-collocated data
>> as
>>> well
>>> https://issues.apache.org/jira/browse/IGNITE-1232
>>>
>>> 5. Enhanced Oracle and IBM JDK interoperability
>>> https://issues.apache.org/jira/browse/IGNITE-1526
>>>
>>> 6. MQTT streamer
>>> https://issues.apache.org/jira/browse/IGNITE-535
>>>
>>> 7. Continuous query failover
>>> https://issues.apache.org/jira/browse/IGNITE-426
>>>
>>> 8. Significant transactional cache performance optimizations - I will
>> merge
>>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>>>
>>> 9. Many stability and fault-tolerance fixes.
>>>
>>> 10. I would also like to include distributed Semaphore. Vladislav, any
>>> chance you can finish with it this week?
>>> https://issues.apache.org/jira/browse/IGNITE-
>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
>>>
>>> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
>>> please respond to this email and let us know when can we expect your
>>> changes being merged to master and release branch?
>>>
>>> Can someone create ignite-1.5 release branch?
>>>
>>> --Yakov
>>>
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Vladislav, how can I take a look at the code and run your tests?
--Yakov
2015-11-11 12:33 GMT+03:00 Vladisav Jelisavcic <vl...@gmail.com>:
> Yakov,
>
> sorry for running a bit late.
>
> > Vladislav, do you have any updates for
> > https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
> >
> > --Yakov
>
> I have problems with some fail-over scenarios;
> It seems that if the two nodes are in the middle of acquiring or releasing
> the semaphore,
> and one of them fails, all nodes get:
>
> [09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
> <ignite-atomics-sys-cache> Failed to compare and set:
> o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> Failed to acquire lock for keys (primary node left grid, retry transaction
> if possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> ...
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed
> to acquire lock for keys (primary node left grid, retry transaction if
> possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
> [name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
> node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
> ... 10 more
>
>
> I'm still trying to find out how to exactly reproduce this behavior,
> I'll send you more details once I try few more things.
>
> I am still using partitioned cache, does it make sense to use replicated
> cache instead?
>
>
> Other than that, I'm done with everything else.
>
> Thanks,
> Vladisav
>
>
>
> On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <ra...@apache.org> wrote:
>
> > Sorry I haven't made an appearance in this thread yet.
> >
> > > 6. MQTT streamer
> > > https://issues.apache.org/jira/browse/IGNITE-535
> >
> > Yes, it was merged to master before the ignite-1.5 was created.
> >
> > I'd like to add:
> >
> > Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
> > -- I'll merge this as soon as I finished with the OSGi tickets with
> demand.
> >
> > OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI (or
> > whatever agreement we arrive to in mailing lists and Wiki)
> > -- https://issues.apache.org/jira/browse/IGNITE-1527
> > -- https://issues.apache.org/jira/browse/IGNITE-1877
> > -- I'm working actively on these two features.
> >
> > *Raúl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
> >
> > > Guys,
> > >
> > > I think we can start preparation to Ignite-1.5 release which will
> include
> > > many interesting features:
> > >
> > > 1. Portable object API
> > > https://issues.apache.org/jira/browse/IGNITE-1486
> > >
> > > 2. Ignite.NET and Ignite C++
> > > https://issues.apache.org/jira/browse/IGNITE-1282
> > >
> > > 3. Optimistic serializable transactions
> > > https://issues.apache.org/jira/browse/IGNITE-1607
> > >
> > > 4. Distributed SQL joins - we will be able to query non-collocated data
> > as
> > > well
> > > https://issues.apache.org/jira/browse/IGNITE-1232
> > >
> > > 5. Enhanced Oracle and IBM JDK interoperability
> > > https://issues.apache.org/jira/browse/IGNITE-1526
> > >
> > > 6. MQTT streamer
> > > https://issues.apache.org/jira/browse/IGNITE-535
> > >
> > > 7. Continuous query failover
> > > https://issues.apache.org/jira/browse/IGNITE-426
> > >
> > > 8. Significant transactional cache performance optimizations - I will
> > merge
> > > these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > >
> > > 9. Many stability and fault-tolerance fixes.
> > >
> > > 10. I would also like to include distributed Semaphore. Vladislav, any
> > > chance you can finish with it this week?
> > > https://issues.apache.org/jira/browse/IGNITE-
> > > <https://issues.apache.org/jira/browse/IGNITE-426>638
> > >
> > > Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> > > please respond to this email and let us know when can we expect your
> > > changes being merged to master and release branch?
> > >
> > > Can someone create ignite-1.5 release branch?
> > >
> > > --Yakov
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Vladisav Jelisavcic <vl...@gmail.com>.
Yakov,
sorry for running a bit late.
> Vladislav, do you have any updates for
> https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
>
> --Yakov
I have problems with some fail-over scenarios;
It seems that if the two nodes are in the middle of acquiring or releasing
the semaphore,
and one of them fails, all nodes get:
[09:36:38,509][ERROR][ignite-#13%pub-null%][GridCacheSemaphoreImpl]
<ignite-atomics-sys-cache> Failed to compare and set:
o.a.i.i.processors.datastructures.GridCacheSemaphoreImpl$Sync$1@5528b728
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
Failed to acquire lock for keys (primary node left grid, retry transaction
if possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
[name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
...
Caused by: class
org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Failed
to acquire lock for keys (primary node left grid, retry transaction if
possible) [keys=[UserKeyCacheObjectImpl [val=GridCacheInternalKeyImpl
[name=ac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=true]],
node=c321fcc4-5db5-4b03-9811-6a5587f2c253]
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.java:1199)
... 10 more
I'm still trying to find out how to exactly reproduce this behavior,
I'll send you more details once I try few more things.
I am still using partitioned cache, does it make sense to use replicated
cache instead?
Other than that, I'm done with everything else.
Thanks,
Vladisav
On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani <ra...@apache.org> wrote:
> Sorry I haven't made an appearance in this thread yet.
>
> > 6. MQTT streamer
> > https://issues.apache.org/jira/browse/IGNITE-535
>
> Yes, it was merged to master before the ignite-1.5 was created.
>
> I'd like to add:
>
> Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
> -- I'll merge this as soon as I finished with the OSGi tickets with demand.
>
> OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI (or
> whatever agreement we arrive to in mailing lists and Wiki)
> -- https://issues.apache.org/jira/browse/IGNITE-1527
> -- https://issues.apache.org/jira/browse/IGNITE-1877
> -- I'm working actively on these two features.
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yz...@apache.org> wrote:
>
> > Guys,
> >
> > I think we can start preparation to Ignite-1.5 release which will include
> > many interesting features:
> >
> > 1. Portable object API
> > https://issues.apache.org/jira/browse/IGNITE-1486
> >
> > 2. Ignite.NET and Ignite C++
> > https://issues.apache.org/jira/browse/IGNITE-1282
> >
> > 3. Optimistic serializable transactions
> > https://issues.apache.org/jira/browse/IGNITE-1607
> >
> > 4. Distributed SQL joins - we will be able to query non-collocated data
> as
> > well
> > https://issues.apache.org/jira/browse/IGNITE-1232
> >
> > 5. Enhanced Oracle and IBM JDK interoperability
> > https://issues.apache.org/jira/browse/IGNITE-1526
> >
> > 6. MQTT streamer
> > https://issues.apache.org/jira/browse/IGNITE-535
> >
> > 7. Continuous query failover
> > https://issues.apache.org/jira/browse/IGNITE-426
> >
> > 8. Significant transactional cache performance optimizations - I will
> merge
> > these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> >
> > 9. Many stability and fault-tolerance fixes.
> >
> > 10. I would also like to include distributed Semaphore. Vladislav, any
> > chance you can finish with it this week?
> > https://issues.apache.org/jira/browse/IGNITE-
> > <https://issues.apache.org/jira/browse/IGNITE-426>638
> >
> > Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> > please respond to this email and let us know when can we expect your
> > changes being merged to master and release branch?
> >
> > Can someone create ignite-1.5 release branch?
> >
> > --Yakov
> >
>
Re: Ignite-1.5 Release
Posted by Raul Kripalani <ra...@apache.org>.
Sorry I haven't made an appearance in this thread yet.
> 6. MQTT streamer
> https://issues.apache.org/jira/browse/IGNITE-535
Yes, it was merged to master before the ignite-1.5 was created.
I'd like to add:
Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
-- I'll merge this as soon as I finished with the OSGi tickets with demand.
OSGi Manifests, Karaf features and possible ClassLoaderCodec SPI (or
whatever agreement we arrive to in mailing lists and Wiki)
-- https://issues.apache.org/jira/browse/IGNITE-1527
-- https://issues.apache.org/jira/browse/IGNITE-1877
-- I'm working actively on these two features.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Mon, Nov 2, 2015 at 1:35 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Guys,
>
> I think we can start preparation to Ignite-1.5 release which will include
> many interesting features:
>
> 1. Portable object API
> https://issues.apache.org/jira/browse/IGNITE-1486
>
> 2. Ignite.NET and Ignite C++
> https://issues.apache.org/jira/browse/IGNITE-1282
>
> 3. Optimistic serializable transactions
> https://issues.apache.org/jira/browse/IGNITE-1607
>
> 4. Distributed SQL joins - we will be able to query non-collocated data as
> well
> https://issues.apache.org/jira/browse/IGNITE-1232
>
> 5. Enhanced Oracle and IBM JDK interoperability
> https://issues.apache.org/jira/browse/IGNITE-1526
>
> 6. MQTT streamer
> https://issues.apache.org/jira/browse/IGNITE-535
>
> 7. Continuous query failover
> https://issues.apache.org/jira/browse/IGNITE-426
>
> 8. Significant transactional cache performance optimizations - I will merge
> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>
> 9. Many stability and fault-tolerance fixes.
>
> 10. I would also like to include distributed Semaphore. Vladislav, any
> chance you can finish with it this week?
> https://issues.apache.org/jira/browse/IGNITE-
> <https://issues.apache.org/jira/browse/IGNITE-426>638
>
> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> please respond to this email and let us know when can we expect your
> changes being merged to master and release branch?
>
> Can someone create ignite-1.5 release branch?
>
> --Yakov
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
I would also try G1 collector. It will be the default collector in Java 9.
On Sun, Nov 8, 2015 at 10:14 PM, Semyon Boikov <sb...@gridgain.com> wrote:
> We run with -XX:+UseConcMarkSweepGC -XX:+UseParNewGC.
>
> On Thu, Nov 5, 2015 at 8:42 PM, Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
> > Semyon,
> >
> > Do you know what kind of Garbage Collector you have used for the
> > benchmarks? Was it G1?
> >
> > D.
> >
> > On Thu, Nov 5, 2015 at 5:55 AM, Semyon Boikov <sb...@gridgain.com>
> > wrote:
> >
> > > I merged into 1.5 performance optimizations implemented by Yakov. With
> > > these optimizations we got up to 20% throughput increase in
> transactional
> > > cache benchmarks.
> > >
> > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org>
> > wrote:
> > >
> > > > Guys,
> > > >
> > > > I think we can start preparation to Ignite-1.5 release which will
> > include
> > > > many interesting features:
> > > >
> > > > 1. Portable object API
> > > > https://issues.apache.org/jira/browse/IGNITE-1486
> > > >
> > > > 2. Ignite.NET and Ignite C++
> > > > https://issues.apache.org/jira/browse/IGNITE-1282
> > > >
> > > > 3. Optimistic serializable transactions
> > > > https://issues.apache.org/jira/browse/IGNITE-1607
> > > >
> > > > 4. Distributed SQL joins - we will be able to query non-collocated
> data
> > > as
> > > > well
> > > > https://issues.apache.org/jira/browse/IGNITE-1232
> > > >
> > > > 5. Enhanced Oracle and IBM JDK interoperability
> > > > https://issues.apache.org/jira/browse/IGNITE-1526
> > > >
> > > > 6. MQTT streamer
> > > > https://issues.apache.org/jira/browse/IGNITE-535
> > > >
> > > > 7. Continuous query failover
> > > > https://issues.apache.org/jira/browse/IGNITE-426
> > > >
> > > > 8. Significant transactional cache performance optimizations - I will
> > > merge
> > > > these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > > >
> > > > 9. Many stability and fault-tolerance fixes.
> > > >
> > > > 10. I would also like to include distributed Semaphore. Vladislav,
> any
> > > > chance you can finish with it this week?
> > > > https://issues.apache.org/jira/browse/IGNITE-
> > > > <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > >
> > > > Thanks to everyone involved! Guys, esp. assignees of mentioned
> issues,
> > > > please respond to this email and let us know when can we expect your
> > > > changes being merged to master and release branch?
> > > >
> > > > Can someone create ignite-1.5 release branch?
> > > >
> > > > --Yakov
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Semyon Boikov <sb...@gridgain.com>.
We run with -XX:+UseConcMarkSweepGC -XX:+UseParNewGC.
On Thu, Nov 5, 2015 at 8:42 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> Semyon,
>
> Do you know what kind of Garbage Collector you have used for the
> benchmarks? Was it G1?
>
> D.
>
> On Thu, Nov 5, 2015 at 5:55 AM, Semyon Boikov <sb...@gridgain.com>
> wrote:
>
> > I merged into 1.5 performance optimizations implemented by Yakov. With
> > these optimizations we got up to 20% throughput increase in transactional
> > cache benchmarks.
> >
> > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
> >
> > > Guys,
> > >
> > > I think we can start preparation to Ignite-1.5 release which will
> include
> > > many interesting features:
> > >
> > > 1. Portable object API
> > > https://issues.apache.org/jira/browse/IGNITE-1486
> > >
> > > 2. Ignite.NET and Ignite C++
> > > https://issues.apache.org/jira/browse/IGNITE-1282
> > >
> > > 3. Optimistic serializable transactions
> > > https://issues.apache.org/jira/browse/IGNITE-1607
> > >
> > > 4. Distributed SQL joins - we will be able to query non-collocated data
> > as
> > > well
> > > https://issues.apache.org/jira/browse/IGNITE-1232
> > >
> > > 5. Enhanced Oracle and IBM JDK interoperability
> > > https://issues.apache.org/jira/browse/IGNITE-1526
> > >
> > > 6. MQTT streamer
> > > https://issues.apache.org/jira/browse/IGNITE-535
> > >
> > > 7. Continuous query failover
> > > https://issues.apache.org/jira/browse/IGNITE-426
> > >
> > > 8. Significant transactional cache performance optimizations - I will
> > merge
> > > these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > >
> > > 9. Many stability and fault-tolerance fixes.
> > >
> > > 10. I would also like to include distributed Semaphore. Vladislav, any
> > > chance you can finish with it this week?
> > > https://issues.apache.org/jira/browse/IGNITE-
> > > <https://issues.apache.org/jira/browse/IGNITE-426>638
> > >
> > > Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> > > please respond to this email and let us know when can we expect your
> > > changes being merged to master and release branch?
> > >
> > > Can someone create ignite-1.5 release branch?
> > >
> > > --Yakov
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Semyon,
Do you know what kind of Garbage Collector you have used for the
benchmarks? Was it G1?
D.
On Thu, Nov 5, 2015 at 5:55 AM, Semyon Boikov <sb...@gridgain.com> wrote:
> I merged into 1.5 performance optimizations implemented by Yakov. With
> these optimizations we got up to 20% throughput increase in transactional
> cache benchmarks.
>
> On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org> wrote:
>
> > Guys,
> >
> > I think we can start preparation to Ignite-1.5 release which will include
> > many interesting features:
> >
> > 1. Portable object API
> > https://issues.apache.org/jira/browse/IGNITE-1486
> >
> > 2. Ignite.NET and Ignite C++
> > https://issues.apache.org/jira/browse/IGNITE-1282
> >
> > 3. Optimistic serializable transactions
> > https://issues.apache.org/jira/browse/IGNITE-1607
> >
> > 4. Distributed SQL joins - we will be able to query non-collocated data
> as
> > well
> > https://issues.apache.org/jira/browse/IGNITE-1232
> >
> > 5. Enhanced Oracle and IBM JDK interoperability
> > https://issues.apache.org/jira/browse/IGNITE-1526
> >
> > 6. MQTT streamer
> > https://issues.apache.org/jira/browse/IGNITE-535
> >
> > 7. Continuous query failover
> > https://issues.apache.org/jira/browse/IGNITE-426
> >
> > 8. Significant transactional cache performance optimizations - I will
> merge
> > these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> >
> > 9. Many stability and fault-tolerance fixes.
> >
> > 10. I would also like to include distributed Semaphore. Vladislav, any
> > chance you can finish with it this week?
> > https://issues.apache.org/jira/browse/IGNITE-
> > <https://issues.apache.org/jira/browse/IGNITE-426>638
> >
> > Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> > please respond to this email and let us know when can we expect your
> > changes being merged to master and release branch?
> >
> > Can someone create ignite-1.5 release branch?
> >
> > --Yakov
> >
>
Re: Ignite-1.5 Release
Posted by Semyon Boikov <sb...@gridgain.com>.
I merged into 1.5 performance optimizations implemented by Yakov. With
these optimizations we got up to 20% throughput increase in transactional
cache benchmarks.
On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Guys,
>
> I think we can start preparation to Ignite-1.5 release which will include
> many interesting features:
>
> 1. Portable object API
> https://issues.apache.org/jira/browse/IGNITE-1486
>
> 2. Ignite.NET and Ignite C++
> https://issues.apache.org/jira/browse/IGNITE-1282
>
> 3. Optimistic serializable transactions
> https://issues.apache.org/jira/browse/IGNITE-1607
>
> 4. Distributed SQL joins - we will be able to query non-collocated data as
> well
> https://issues.apache.org/jira/browse/IGNITE-1232
>
> 5. Enhanced Oracle and IBM JDK interoperability
> https://issues.apache.org/jira/browse/IGNITE-1526
>
> 6. MQTT streamer
> https://issues.apache.org/jira/browse/IGNITE-535
>
> 7. Continuous query failover
> https://issues.apache.org/jira/browse/IGNITE-426
>
> 8. Significant transactional cache performance optimizations - I will merge
> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>
> 9. Many stability and fault-tolerance fixes.
>
> 10. I would also like to include distributed Semaphore. Vladislav, any
> chance you can finish with it this week?
> https://issues.apache.org/jira/browse/IGNITE-
> <https://issues.apache.org/jira/browse/IGNITE-426>638
>
> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> please respond to this email and let us know when can we expect your
> changes being merged to master and release branch?
>
> Can someone create ignite-1.5 release branch?
>
> --Yakov
>
Re: Ignite-1.5 Release
Posted by Valentin Kulichenko <va...@gmail.com>.
Folks,
I'm currently working on finalizing optimizations in communication and
direct marshalling, as well as supporting backward compatibility. It turned
out that this requires some refactoring, so it will take one more day at
least. I hope to merge tomorrow.
On Tue, Nov 17, 2015 at 2:43 PM, Roman Shtykh <rs...@yahoo.com.invalid>
wrote:
> 11. Flume intergration
> https://issues.apache.org/jira/browse/IGNITE-529
>
>
> is done too. Thanks Anton for reviews!
>
> Roman
>
>
>
>
> On Monday, November 2, 2015 10:35 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
>
>
>
> Guys,
>
> I think we can start preparation to Ignite-1.5 release which will include
> many interesting features:
>
> 1. Portable object API
> https://issues.apache.org/jira/browse/IGNITE-1486
>
> 2. Ignite.NET and Ignite C++
> https://issues.apache.org/jira/browse/IGNITE-1282
>
> 3. Optimistic serializable transactions
> https://issues.apache.org/jira/browse/IGNITE-1607
>
> 4. Distributed SQL joins - we will be able to query non-collocated data as
> well
> https://issues.apache.org/jira/browse/IGNITE-1232
>
> 5. Enhanced Oracle and IBM JDK interoperability
> https://issues.apache.org/jira/browse/IGNITE-1526
>
> 6. MQTT streamer
> https://issues.apache.org/jira/browse/IGNITE-535
>
> 7. Continuous query failover
> https://issues.apache.org/jira/browse/IGNITE-426
>
> 8. Significant transactional cache performance optimizations - I will merge
> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>
> 9. Many stability and fault-tolerance fixes.
>
> 10. I would also like to include distributed Semaphore. Vladislav, any
> chance you can finish with it this week?
> https://issues.apache.org/jira/browse/IGNITE-
> <https://issues.apache.org/jira/browse/IGNITE-426>638
>
> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> please respond to this email and let us know when can we expect your
> changes being merged to master and release branch?
>
> Can someone create ignite-1.5 release branch?
>
> --Yakov
>
Re: Ignite-1.5 Release
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
11. Flume intergration
https://issues.apache.org/jira/browse/IGNITE-529
is done too. Thanks Anton for reviews!
Roman
On Monday, November 2, 2015 10:35 PM, Yakov Zhdanov <yz...@apache.org> wrote:
Guys,
I think we can start preparation to Ignite-1.5 release which will include
many interesting features:
1. Portable object API
https://issues.apache.org/jira/browse/IGNITE-1486
2. Ignite.NET and Ignite C++
https://issues.apache.org/jira/browse/IGNITE-1282
3. Optimistic serializable transactions
https://issues.apache.org/jira/browse/IGNITE-1607
4. Distributed SQL joins - we will be able to query non-collocated data as
well
https://issues.apache.org/jira/browse/IGNITE-1232
5. Enhanced Oracle and IBM JDK interoperability
https://issues.apache.org/jira/browse/IGNITE-1526
6. MQTT streamer
https://issues.apache.org/jira/browse/IGNITE-535
7. Continuous query failover
https://issues.apache.org/jira/browse/IGNITE-426
8. Significant transactional cache performance optimizations - I will merge
these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
9. Many stability and fault-tolerance fixes.
10. I would also like to include distributed Semaphore. Vladislav, any
chance you can finish with it this week?
https://issues.apache.org/jira/browse/IGNITE-
<https://issues.apache.org/jira/browse/IGNITE-426>638
Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
please respond to this email and let us know when can we expect your
changes being merged to master and release branch?
Can someone create ignite-1.5 release branch?
--Yakov
Re: Ignite-1.5 Release
Posted by Denis Magda <dm...@gridgain.com>.
On 11/2/2015 8:40 PM, Dmitriy Setrakyan wrote:
> On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
>
>> Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681 ?
>>
> I don’t see why not. Would be nice if one of the committers could pick up
> the review for this patch.
>
Dmitriy and other committers, who keep an eye on public API changes, are
you OK with the changes in CacheConfiguration API done in IGNITE-1681?
--
Denis
>> On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <avinogradov@gridgain.com
>> wrote:
>>
>>> Branch ignite-1.5 created.
>>>
>>> On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
>> avinogradov@gridgain.com
>>> wrote:
>>>
>>>> I assume that correct link at 10th feature is
>>>> https://issues.apache.org/jira/browse/IGNITE-638
>>>>
>>>> On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org>
>>> wrote:
>>>>> Guys,
>>>>>
>>>>> I think we can start preparation to Ignite-1.5 release which will
>>> include
>>>>> many interesting features:
>>>>>
>>>>> 1. Portable object API
>>>>> https://issues.apache.org/jira/browse/IGNITE-1486
>>>>>
>>>>> 2. Ignite.NET and Ignite C++
>>>>> https://issues.apache.org/jira/browse/IGNITE-1282
>>>>>
>>>>> 3. Optimistic serializable transactions
>>>>> https://issues.apache.org/jira/browse/IGNITE-1607
>>>>>
>>>>> 4. Distributed SQL joins - we will be able to query non-collocated
>> data
>>> as
>>>>> well
>>>>> https://issues.apache.org/jira/browse/IGNITE-1232
>>>>>
>>>>> 5. Enhanced Oracle and IBM JDK interoperability
>>>>> https://issues.apache.org/jira/browse/IGNITE-1526
>>>>>
>>>>> 6. MQTT streamer
>>>>> https://issues.apache.org/jira/browse/IGNITE-535
>>>>>
>>>>> 7. Continuous query failover
>>>>> https://issues.apache.org/jira/browse/IGNITE-426
>>>>>
>>>>> 8. Significant transactional cache performance optimizations - I will
>>>>> merge
>>>>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>>>>>
>>>>> 9. Many stability and fault-tolerance fixes.
>>>>>
>>>>> 10. I would also like to include distributed Semaphore. Vladislav, any
>>>>> chance you can finish with it this week?
>>>>> https://issues.apache.org/jira/browse/IGNITE-
>>>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
>>>>>
>>>>> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
>>>>> please respond to this email and let us know when can we expect your
>>>>> changes being merged to master and release branch?
>>>>>
>>>>> Can someone create ignite-1.5 release branch?
>>>>>
>>>>> --Yakov
>>>>>
>>>>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Folks,
It looks like Ignite-950 branch is ready to be merged to ignite-1282. Can
someone pull latest changes from 1.5 to ignite-1282 branch? I know some of
the critical issues have been fixed lately, so I would like to give CI
another run before my merge.
2015-11-04 1:50 GMT+03:00 Alexey Kuznetsov <ak...@gridgain.com>:
> I'm working on IGNITE-1753 Rework CacheJdbcPojoStore to new API (
> https://issues.apache.org/jira/browse/IGNITE-1753).
> Issue is implemented and waiting for IGNITE-950 to be merged into
> ignite-1282.
>
> On Wed, Nov 4, 2015 at 5:22 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com
> > wrote:
>
> > Good news for the IGNITE-950 ticket - CI looks good, changes will be
> merged
> > to ignite-1282 integration branch after benchmarks re-run.
> >
> > 2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <nt...@gridgain.com>:
> >
> > > I implemented changes related to IGNITE-426 task. Currently
> investigating
> > > performance degradation for atomic caches. I expect the ticket to be
> > merged
> > > in 2 days.
> > >
> > > On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> > > alexey.goncharuk@gmail.com
> > > > wrote:
> > >
> > > > IGNITE-950 is taking more time to be merged than I originally
> > estimated.
> > > We
> > > > had a couple of silly bugs, such as loosing cache operation context
> on
> > > > async cache operations, which led to hard-to debug failures in the
> > > platform
> > > > integration code.
> > > > I also added some sanity checks to indexing and found that I ran
> > > benchmarks
> > > > for new binary format on a model with externalizable classes, so the
> > > result
> > > > I've got were invalid, need more time to fix the model and re-run
> > > > benchmarks.
> > > >
> > > > I am currently waiting for another CI run, will give an update in
> > several
> > > > hours.
> > > >
> > > > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> > > >
> > > > > Here are my current status for all interop-related stuff (you can
> > view
> > > > > these tickets using query "project = IGNITE AND status in (Open,
> "In
> > > > > Progress", Reopened, Resolved, "Patch Available") AND component =
> > > interop
> > > > > AND fixVersion = 1.5"):
> > > > >
> > > > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > > > Trivial. Waiting for IGNITE-950 merge.
> > > > >
> > > > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > > > Trivial. Waiting for IGNITE-950 merge.
> > > > >
> > > > > *IGNITE-1803 - Optimized field lookup for queries*
> > > > > Ready. Waiting for IGNITE-950 to merge.
> > > > >
> > > > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > > > Not started yet. Waiting for IGNITE-950 to merge.
> > > > >
> > > > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > > > footer.*
> > > > > Not started yet.
> > > > >
> > > > > + Several minor tickets.
> > > > >
> > > > > All in all, I expect all these tickets to be ready in 2 days.
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > > > alexey.goncharuk@gmail.com
> > > > > > wrote:
> > > > >
> > > > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> > > *ticket*".
> > > > > The
> > > > > > changes are in ignite-950-new branch because it is a result of
> work
> > > on
> > > > > > multiple sub-tickets and it is currently used as an integration
> > > branch.
> > > > > >
> > > > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <
> dsetrakyan@apache.org
> > >:
> > > > > >
> > > > > > > Alexey,
> > > > > > >
> > > > > > > I am confused. Why do you have 2 branches?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > > > alexey.goncharuk@gmail.com
> > > > > > > > wrote:
> > > > > > >
> > > > > > > > I am finalizing changes related to IGNITE-1486 branch.
> > Currently
> > > > the
> > > > > > API
> > > > > > > > changes are finished and now I am mostly fixing the CI tests.
> > In
> > > > > fact,
> > > > > > I
> > > > > > > > just submitted the latest fix related to the new .NET
> platform
> > > > > > > > functionality and hope CI tests will pass, in this case it
> will
> > > be
> > > > > > ready
> > > > > > > to
> > > > > > > > be merged tomorrow morning.
> > > > > > > > It would be nice if other community members reviewed my
> changes
> > > in
> > > > > > > > ignite-950-new branch before it gets to master.
> > > > > > > >
> > > > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > > > dsetrakyan@apache.org
> > > > > >:
> > > > > > > >
> > > > > > > > > Thanks Vladislav!
> > > > > > > > >
> > > > > > > > > Would also be nice to get an update from other committers
> > > > involved
> > > > > in
> > > > > > > the
> > > > > > > > > outlined tickets. Specifically whether the ticket has been
> > > merged
> > > > > to
> > > > > > > > master
> > > > > > > > > or not, and if not, what should be the expectation.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > > > vladisavj@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > >10. I would also like to include distributed Semaphore.
> > > > > Vladislav,
> > > > > > > any
> > > > > > > > > > >chance you can finish with it this week?
> > > > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > > >
> > > > > > > > > > I will have it done by thursday.
> > > > > > > > > >
> > > > > > > > > > Best regards,
> > > > > > > > > > Vladisav
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > > > dsetrakyan@apache.org
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <
> endian675@gmail.com
> > >
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Can/will this include
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > > > ?
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I don’t see why not. Would be nice if one of the
> > committers
> > > > > could
> > > > > > > > pick
> > > > > > > > > up
> > > > > > > > > > > the review for this patch.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > > > yzhdanov@apache.org
> > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >> Guys,
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> > > release
> > > > > > which
> > > > > > > > > will
> > > > > > > > > > > > > include
> > > > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to
> > query
> > > > > > > > > non-collocated
> > > > > > > > > > > > data
> > > > > > > > > > > > > as
> > > > > > > > > > > > > >> well
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > > > optimizations
> > > > > > > > - I
> > > > > > > > > > > will
> > > > > > > > > > > > > >> merge
> > > > > > > > > > > > > >> these changes from
> 'ignite-1.4-slow-server-debug'
> > > > today
> > > > > or
> > > > > > > > > > tomorrow.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 10. I would also like to include distributed
> > > > Semaphore.
> > > > > > > > > Vladislav,
> > > > > > > > > > > any
> > > > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > > > >> <
> https://issues.apache.org/jira/browse/IGNITE-426
> > > >638
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Thanks to everyone involved! Guys, esp.
> assignees
> > of
> > > > > > > mentioned
> > > > > > > > > > > issues,
> > > > > > > > > > > > > >> please respond to this email and let us know
> when
> > > can
> > > > we
> > > > > > > > expect
> > > > > > > > > > your
> > > > > > > > > > > > > >> changes being merged to master and release
> branch?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> --Yakov
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Igniters,
IGNITE-950 branch with the latest API changes was merged to the ignite-1282
branch. There is still a couple of pending changes related to configuration
(these changes must be made after the merge) and performance, but I think
now it is a good moment for the community to review and leave feedback to
the proposed changes.
Looking forward for the comments :)
2015-11-05 16:11 GMT+03:00 Alexey Goncharuk <al...@gmail.com>:
> I think it's a critical issue; good thing is that the ticket already
> contains a proper description, so at least it is clear what to fix. I'll
> try to take a look at this over the weekend.
>
> 2015-11-05 15:45 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
>
>> Igniters,
>>
>> One more thing - I found a ticket *IGNITE-1377 *where portable metadata
>> update could cause hangs in cache. As we are planning to have
>> PortableMarshaller as default one, looks like this ticket is better to be
>> fixed before the release.
>>
>> On Thu, Nov 5, 2015 at 3:30 PM, Vladimir Ozerov <vo...@gridgain.com>
>> wrote:
>>
>> > When I look into profiler, I see that actual work with portables takes
>> > only relatively small fraction of time. The only significant hotspot I
>> saw
>> > was query parsing, but we already discussed this in another topic and
>> Sergi
>> > created a ticket.
>> >
>> > To improve performance even further, we need to start working on
>> > microoptimizations, because I see that query execution produces loooots
>> of
>> > garbage due to dozens of wrappers, primitives boxing, etc.. Something
>> comes
>> > form portables, something comes from indexing. I do not think that
>> working
>> > solely on portables can give us a breakthrough in performance.
>> >
>> > On Thu, Nov 5, 2015 at 12:50 AM, Dmitriy Setrakyan <
>> dsetrakyan@apache.org>
>> > wrote:
>> >
>> >> On Wed, Nov 4, 2015 at 10:25 AM, Vladimir Ozerov <vozerov@gridgain.com
>> >
>> >> wrote:
>> >>
>> >> >
>> >> > Also I measured query performance on some local benchmarks and got
>> >> > acceptable resutls - queries are about 5-7% slower with poratbles
>> than
>> >> with
>> >> > OptimizedMarshaller. Looks very promising to me provided that we work
>> >> with
>> >> > deserialized objects now.
>> >>
>> >>
>> >> Vladimir, I don’t think we can treat these results as acceptable. So
>> far,
>> >> Ignite has been doing very well on all competitive benchmarks, and we
>> >> cannot afford to start loosing any of them.
>> >>
>> >> Now, I remember seeing emails about many more performance
>> optimizations we
>> >> can add, like aligning String representation with binary
>> representation,
>> >> etc. Do you think after adding all the optimizations we will still be
>> >> slower or faster?
>> >>
>> >> D.
>> >>
>> >
>> >
>>
>
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
I think it's a critical issue; good thing is that the ticket already
contains a proper description, so at least it is clear what to fix. I'll
try to take a look at this over the weekend.
2015-11-05 15:45 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> Igniters,
>
> One more thing - I found a ticket *IGNITE-1377 *where portable metadata
> update could cause hangs in cache. As we are planning to have
> PortableMarshaller as default one, looks like this ticket is better to be
> fixed before the release.
>
> On Thu, Nov 5, 2015 at 3:30 PM, Vladimir Ozerov <vo...@gridgain.com>
> wrote:
>
> > When I look into profiler, I see that actual work with portables takes
> > only relatively small fraction of time. The only significant hotspot I
> saw
> > was query parsing, but we already discussed this in another topic and
> Sergi
> > created a ticket.
> >
> > To improve performance even further, we need to start working on
> > microoptimizations, because I see that query execution produces loooots
> of
> > garbage due to dozens of wrappers, primitives boxing, etc.. Something
> comes
> > form portables, something comes from indexing. I do not think that
> working
> > solely on portables can give us a breakthrough in performance.
> >
> > On Thu, Nov 5, 2015 at 12:50 AM, Dmitriy Setrakyan <
> dsetrakyan@apache.org>
> > wrote:
> >
> >> On Wed, Nov 4, 2015 at 10:25 AM, Vladimir Ozerov <vo...@gridgain.com>
> >> wrote:
> >>
> >> >
> >> > Also I measured query performance on some local benchmarks and got
> >> > acceptable resutls - queries are about 5-7% slower with poratbles than
> >> with
> >> > OptimizedMarshaller. Looks very promising to me provided that we work
> >> with
> >> > deserialized objects now.
> >>
> >>
> >> Vladimir, I don’t think we can treat these results as acceptable. So
> far,
> >> Ignite has been doing very well on all competitive benchmarks, and we
> >> cannot afford to start loosing any of them.
> >>
> >> Now, I remember seeing emails about many more performance optimizations
> we
> >> can add, like aligning String representation with binary representation,
> >> etc. Do you think after adding all the optimizations we will still be
> >> slower or faster?
> >>
> >> D.
> >>
> >
> >
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Igniters,
One more thing - I found a ticket *IGNITE-1377 *where portable metadata
update could cause hangs in cache. As we are planning to have
PortableMarshaller as default one, looks like this ticket is better to be
fixed before the release.
On Thu, Nov 5, 2015 at 3:30 PM, Vladimir Ozerov <vo...@gridgain.com>
wrote:
> When I look into profiler, I see that actual work with portables takes
> only relatively small fraction of time. The only significant hotspot I saw
> was query parsing, but we already discussed this in another topic and Sergi
> created a ticket.
>
> To improve performance even further, we need to start working on
> microoptimizations, because I see that query execution produces loooots of
> garbage due to dozens of wrappers, primitives boxing, etc.. Something comes
> form portables, something comes from indexing. I do not think that working
> solely on portables can give us a breakthrough in performance.
>
> On Thu, Nov 5, 2015 at 12:50 AM, Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
>> On Wed, Nov 4, 2015 at 10:25 AM, Vladimir Ozerov <vo...@gridgain.com>
>> wrote:
>>
>> >
>> > Also I measured query performance on some local benchmarks and got
>> > acceptable resutls - queries are about 5-7% slower with poratbles than
>> with
>> > OptimizedMarshaller. Looks very promising to me provided that we work
>> with
>> > deserialized objects now.
>>
>>
>> Vladimir, I don’t think we can treat these results as acceptable. So far,
>> Ignite has been doing very well on all competitive benchmarks, and we
>> cannot afford to start loosing any of them.
>>
>> Now, I remember seeing emails about many more performance optimizations we
>> can add, like aligning String representation with binary representation,
>> etc. Do you think after adding all the optimizations we will still be
>> slower or faster?
>>
>> D.
>>
>
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
When I look into profiler, I see that actual work with portables takes only
relatively small fraction of time. The only significant hotspot I saw was
query parsing, but we already discussed this in another topic and Sergi
created a ticket.
To improve performance even further, we need to start working on
microoptimizations, because I see that query execution produces loooots of
garbage due to dozens of wrappers, primitives boxing, etc.. Something comes
form portables, something comes from indexing. I do not think that working
solely on portables can give us a breakthrough in performance.
On Thu, Nov 5, 2015 at 12:50 AM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> On Wed, Nov 4, 2015 at 10:25 AM, Vladimir Ozerov <vo...@gridgain.com>
> wrote:
>
> >
> > Also I measured query performance on some local benchmarks and got
> > acceptable resutls - queries are about 5-7% slower with poratbles than
> with
> > OptimizedMarshaller. Looks very promising to me provided that we work
> with
> > deserialized objects now.
>
>
> Vladimir, I don’t think we can treat these results as acceptable. So far,
> Ignite has been doing very well on all competitive benchmarks, and we
> cannot afford to start loosing any of them.
>
> Now, I remember seeing emails about many more performance optimizations we
> can add, like aligning String representation with binary representation,
> etc. Do you think after adding all the optimizations we will still be
> slower or faster?
>
> D.
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Wed, Nov 4, 2015 at 10:25 AM, Vladimir Ozerov <vo...@gridgain.com>
wrote:
>
> Also I measured query performance on some local benchmarks and got
> acceptable resutls - queries are about 5-7% slower with poratbles than with
> OptimizedMarshaller. Looks very promising to me provided that we work with
> deserialized objects now.
Vladimir, I don’t think we can treat these results as acceptable. So far,
Ignite has been doing very well on all competitive benchmarks, and we
cannot afford to start loosing any of them.
Now, I remember seeing emails about many more performance optimizations we
can add, like aligning String representation with binary representation,
etc. Do you think after adding all the optimizations we will still be
slower or faster?
D.
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Igniters, here is curernt status of platform/portable tickets.
As I understand, IGNITE-950 is almost ready and will be merged very soon.
There are 5 more tickets which depends on it:
*IGNITE-1845*, *IGNITE-1846* - move portable API changes to .Net and C++.
This is a matter of refacotring, should not be a problem.
*IGNITE-1819* - remove "metadata enabled" flag. Also fairly simple ticket.
*IGNITE-1847* - move "field" method from PortableObject to
PortableMetadata. Also should be trivial.
*IGNITE-1816* - optionaly do not write field IDs to footer. Important
ticket, I'm working on it. About ~50% ready.
All in all, none of these tickets are showstoppers for merge of
IGNITE-950/IGNITE-1282 to release branch.
Also I measured query performance on some local benchmarks and got
acceptable resutls - queries are about 5-7% slower with poratbles than with
OptimizedMarshaller. Looks very promising to me provided that we work with
deserialized objects now.
On Wed, Nov 4, 2015 at 1:50 AM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> I'm working on IGNITE-1753 Rework CacheJdbcPojoStore to new API (
> https://issues.apache.org/jira/browse/IGNITE-1753).
> Issue is implemented and waiting for IGNITE-950 to be merged into
> ignite-1282.
>
> On Wed, Nov 4, 2015 at 5:22 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com
> > wrote:
>
> > Good news for the IGNITE-950 ticket - CI looks good, changes will be
> merged
> > to ignite-1282 integration branch after benchmarks re-run.
> >
> > 2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <nt...@gridgain.com>:
> >
> > > I implemented changes related to IGNITE-426 task. Currently
> investigating
> > > performance degradation for atomic caches. I expect the ticket to be
> > merged
> > > in 2 days.
> > >
> > > On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> > > alexey.goncharuk@gmail.com
> > > > wrote:
> > >
> > > > IGNITE-950 is taking more time to be merged than I originally
> > estimated.
> > > We
> > > > had a couple of silly bugs, such as loosing cache operation context
> on
> > > > async cache operations, which led to hard-to debug failures in the
> > > platform
> > > > integration code.
> > > > I also added some sanity checks to indexing and found that I ran
> > > benchmarks
> > > > for new binary format on a model with externalizable classes, so the
> > > result
> > > > I've got were invalid, need more time to fix the model and re-run
> > > > benchmarks.
> > > >
> > > > I am currently waiting for another CI run, will give an update in
> > several
> > > > hours.
> > > >
> > > > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> > > >
> > > > > Here are my current status for all interop-related stuff (you can
> > view
> > > > > these tickets using query "project = IGNITE AND status in (Open,
> "In
> > > > > Progress", Reopened, Resolved, "Patch Available") AND component =
> > > interop
> > > > > AND fixVersion = 1.5"):
> > > > >
> > > > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > > > Trivial. Waiting for IGNITE-950 merge.
> > > > >
> > > > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > > > Trivial. Waiting for IGNITE-950 merge.
> > > > >
> > > > > *IGNITE-1803 - Optimized field lookup for queries*
> > > > > Ready. Waiting for IGNITE-950 to merge.
> > > > >
> > > > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > > > Not started yet. Waiting for IGNITE-950 to merge.
> > > > >
> > > > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > > > footer.*
> > > > > Not started yet.
> > > > >
> > > > > + Several minor tickets.
> > > > >
> > > > > All in all, I expect all these tickets to be ready in 2 days.
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > > > alexey.goncharuk@gmail.com
> > > > > > wrote:
> > > > >
> > > > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> > > *ticket*".
> > > > > The
> > > > > > changes are in ignite-950-new branch because it is a result of
> work
> > > on
> > > > > > multiple sub-tickets and it is currently used as an integration
> > > branch.
> > > > > >
> > > > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <
> dsetrakyan@apache.org
> > >:
> > > > > >
> > > > > > > Alexey,
> > > > > > >
> > > > > > > I am confused. Why do you have 2 branches?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > > > alexey.goncharuk@gmail.com
> > > > > > > > wrote:
> > > > > > >
> > > > > > > > I am finalizing changes related to IGNITE-1486 branch.
> > Currently
> > > > the
> > > > > > API
> > > > > > > > changes are finished and now I am mostly fixing the CI tests.
> > In
> > > > > fact,
> > > > > > I
> > > > > > > > just submitted the latest fix related to the new .NET
> platform
> > > > > > > > functionality and hope CI tests will pass, in this case it
> will
> > > be
> > > > > > ready
> > > > > > > to
> > > > > > > > be merged tomorrow morning.
> > > > > > > > It would be nice if other community members reviewed my
> changes
> > > in
> > > > > > > > ignite-950-new branch before it gets to master.
> > > > > > > >
> > > > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > > > dsetrakyan@apache.org
> > > > > >:
> > > > > > > >
> > > > > > > > > Thanks Vladislav!
> > > > > > > > >
> > > > > > > > > Would also be nice to get an update from other committers
> > > > involved
> > > > > in
> > > > > > > the
> > > > > > > > > outlined tickets. Specifically whether the ticket has been
> > > merged
> > > > > to
> > > > > > > > master
> > > > > > > > > or not, and if not, what should be the expectation.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > > > vladisavj@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > >10. I would also like to include distributed Semaphore.
> > > > > Vladislav,
> > > > > > > any
> > > > > > > > > > >chance you can finish with it this week?
> > > > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > > >
> > > > > > > > > > I will have it done by thursday.
> > > > > > > > > >
> > > > > > > > > > Best regards,
> > > > > > > > > > Vladisav
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > > > dsetrakyan@apache.org
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <
> endian675@gmail.com
> > >
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Can/will this include
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > > > ?
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I don’t see why not. Would be nice if one of the
> > committers
> > > > > could
> > > > > > > > pick
> > > > > > > > > up
> > > > > > > > > > > the review for this patch.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > > > yzhdanov@apache.org
> > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >> Guys,
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> > > release
> > > > > > which
> > > > > > > > > will
> > > > > > > > > > > > > include
> > > > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to
> > query
> > > > > > > > > non-collocated
> > > > > > > > > > > > data
> > > > > > > > > > > > > as
> > > > > > > > > > > > > >> well
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > > > optimizations
> > > > > > > > - I
> > > > > > > > > > > will
> > > > > > > > > > > > > >> merge
> > > > > > > > > > > > > >> these changes from
> 'ignite-1.4-slow-server-debug'
> > > > today
> > > > > or
> > > > > > > > > > tomorrow.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 10. I would also like to include distributed
> > > > Semaphore.
> > > > > > > > > Vladislav,
> > > > > > > > > > > any
> > > > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > > > >> <
> https://issues.apache.org/jira/browse/IGNITE-426
> > > >638
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Thanks to everyone involved! Guys, esp.
> assignees
> > of
> > > > > > > mentioned
> > > > > > > > > > > issues,
> > > > > > > > > > > > > >> please respond to this email and let us know
> when
> > > can
> > > > we
> > > > > > > > expect
> > > > > > > > > > your
> > > > > > > > > > > > > >> changes being merged to master and release
> branch?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> --Yakov
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Ignite-1.5 Release
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
I'm working on IGNITE-1753 Rework CacheJdbcPojoStore to new API (
https://issues.apache.org/jira/browse/IGNITE-1753).
Issue is implemented and waiting for IGNITE-950 to be merged into
ignite-1282.
On Wed, Nov 4, 2015 at 5:22 AM, Alexey Goncharuk <alexey.goncharuk@gmail.com
> wrote:
> Good news for the IGNITE-950 ticket - CI looks good, changes will be merged
> to ignite-1282 integration branch after benchmarks re-run.
>
> 2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <nt...@gridgain.com>:
>
> > I implemented changes related to IGNITE-426 task. Currently investigating
> > performance degradation for atomic caches. I expect the ticket to be
> merged
> > in 2 days.
> >
> > On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> > alexey.goncharuk@gmail.com
> > > wrote:
> >
> > > IGNITE-950 is taking more time to be merged than I originally
> estimated.
> > We
> > > had a couple of silly bugs, such as loosing cache operation context on
> > > async cache operations, which led to hard-to debug failures in the
> > platform
> > > integration code.
> > > I also added some sanity checks to indexing and found that I ran
> > benchmarks
> > > for new binary format on a model with externalizable classes, so the
> > result
> > > I've got were invalid, need more time to fix the model and re-run
> > > benchmarks.
> > >
> > > I am currently waiting for another CI run, will give an update in
> several
> > > hours.
> > >
> > > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> > >
> > > > Here are my current status for all interop-related stuff (you can
> view
> > > > these tickets using query "project = IGNITE AND status in (Open, "In
> > > > Progress", Reopened, Resolved, "Patch Available") AND component =
> > interop
> > > > AND fixVersion = 1.5"):
> > > >
> > > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > > Trivial. Waiting for IGNITE-950 merge.
> > > >
> > > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > > Trivial. Waiting for IGNITE-950 merge.
> > > >
> > > > *IGNITE-1803 - Optimized field lookup for queries*
> > > > Ready. Waiting for IGNITE-950 to merge.
> > > >
> > > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > > Not started yet. Waiting for IGNITE-950 to merge.
> > > >
> > > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > > footer.*
> > > > Not started yet.
> > > >
> > > > + Several minor tickets.
> > > >
> > > > All in all, I expect all these tickets to be ready in 2 days.
> > > >
> > > >
> > > >
> > > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > > alexey.goncharuk@gmail.com
> > > > > wrote:
> > > >
> > > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> > *ticket*".
> > > > The
> > > > > changes are in ignite-950-new branch because it is a result of work
> > on
> > > > > multiple sub-tickets and it is currently used as an integration
> > branch.
> > > > >
> > > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org
> >:
> > > > >
> > > > > > Alexey,
> > > > > >
> > > > > > I am confused. Why do you have 2 branches?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > > alexey.goncharuk@gmail.com
> > > > > > > wrote:
> > > > > >
> > > > > > > I am finalizing changes related to IGNITE-1486 branch.
> Currently
> > > the
> > > > > API
> > > > > > > changes are finished and now I am mostly fixing the CI tests.
> In
> > > > fact,
> > > > > I
> > > > > > > just submitted the latest fix related to the new .NET platform
> > > > > > > functionality and hope CI tests will pass, in this case it will
> > be
> > > > > ready
> > > > > > to
> > > > > > > be merged tomorrow morning.
> > > > > > > It would be nice if other community members reviewed my changes
> > in
> > > > > > > ignite-950-new branch before it gets to master.
> > > > > > >
> > > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > > dsetrakyan@apache.org
> > > > >:
> > > > > > >
> > > > > > > > Thanks Vladislav!
> > > > > > > >
> > > > > > > > Would also be nice to get an update from other committers
> > > involved
> > > > in
> > > > > > the
> > > > > > > > outlined tickets. Specifically whether the ticket has been
> > merged
> > > > to
> > > > > > > master
> > > > > > > > or not, and if not, what should be the expectation.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > > vladisavj@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > >10. I would also like to include distributed Semaphore.
> > > > Vladislav,
> > > > > > any
> > > > > > > > > >chance you can finish with it this week?
> > > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > >
> > > > > > > > > I will have it done by thursday.
> > > > > > > > >
> > > > > > > > > Best regards,
> > > > > > > > > Vladisav
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > > dsetrakyan@apache.org
> > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <endian675@gmail.com
> >
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Can/will this include
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > > ?
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I don’t see why not. Would be nice if one of the
> committers
> > > > could
> > > > > > > pick
> > > > > > > > up
> > > > > > > > > > the review for this patch.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > > yzhdanov@apache.org
> > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >> Guys,
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> > release
> > > > > which
> > > > > > > > will
> > > > > > > > > > > > include
> > > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to
> query
> > > > > > > > non-collocated
> > > > > > > > > > > data
> > > > > > > > > > > > as
> > > > > > > > > > > > >> well
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > > optimizations
> > > > > > > - I
> > > > > > > > > > will
> > > > > > > > > > > > >> merge
> > > > > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug'
> > > today
> > > > or
> > > > > > > > > tomorrow.
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 10. I would also like to include distributed
> > > Semaphore.
> > > > > > > > Vladislav,
> > > > > > > > > > any
> > > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426
> > >638
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees
> of
> > > > > > mentioned
> > > > > > > > > > issues,
> > > > > > > > > > > > >> please respond to this email and let us know when
> > can
> > > we
> > > > > > > expect
> > > > > > > > > your
> > > > > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> --Yakov
> > > > > > > > > > > > >>
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Good news for the IGNITE-950 ticket - CI looks good, changes will be merged
to ignite-1282 integration branch after benchmarks re-run.
2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <nt...@gridgain.com>:
> I implemented changes related to IGNITE-426 task. Currently investigating
> performance degradation for atomic caches. I expect the ticket to be merged
> in 2 days.
>
> On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com
> > wrote:
>
> > IGNITE-950 is taking more time to be merged than I originally estimated.
> We
> > had a couple of silly bugs, such as loosing cache operation context on
> > async cache operations, which led to hard-to debug failures in the
> platform
> > integration code.
> > I also added some sanity checks to indexing and found that I ran
> benchmarks
> > for new binary format on a model with externalizable classes, so the
> result
> > I've got were invalid, need more time to fix the model and re-run
> > benchmarks.
> >
> > I am currently waiting for another CI run, will give an update in several
> > hours.
> >
> > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Here are my current status for all interop-related stuff (you can view
> > > these tickets using query "project = IGNITE AND status in (Open, "In
> > > Progress", Reopened, Resolved, "Patch Available") AND component =
> interop
> > > AND fixVersion = 1.5"):
> > >
> > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > Trivial. Waiting for IGNITE-950 merge.
> > >
> > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > Trivial. Waiting for IGNITE-950 merge.
> > >
> > > *IGNITE-1803 - Optimized field lookup for queries*
> > > Ready. Waiting for IGNITE-950 to merge.
> > >
> > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > Not started yet. Waiting for IGNITE-950 to merge.
> > >
> > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > footer.*
> > > Not started yet.
> > >
> > > + Several minor tickets.
> > >
> > > All in all, I expect all these tickets to be ready in 2 days.
> > >
> > >
> > >
> > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > alexey.goncharuk@gmail.com
> > > > wrote:
> > >
> > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> *ticket*".
> > > The
> > > > changes are in ignite-950-new branch because it is a result of work
> on
> > > > multiple sub-tickets and it is currently used as an integration
> branch.
> > > >
> > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> > > >
> > > > > Alexey,
> > > > >
> > > > > I am confused. Why do you have 2 branches?
> > > > >
> > > > > D.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > alexey.goncharuk@gmail.com
> > > > > > wrote:
> > > > >
> > > > > > I am finalizing changes related to IGNITE-1486 branch. Currently
> > the
> > > > API
> > > > > > changes are finished and now I am mostly fixing the CI tests. In
> > > fact,
> > > > I
> > > > > > just submitted the latest fix related to the new .NET platform
> > > > > > functionality and hope CI tests will pass, in this case it will
> be
> > > > ready
> > > > > to
> > > > > > be merged tomorrow morning.
> > > > > > It would be nice if other community members reviewed my changes
> in
> > > > > > ignite-950-new branch before it gets to master.
> > > > > >
> > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > dsetrakyan@apache.org
> > > >:
> > > > > >
> > > > > > > Thanks Vladislav!
> > > > > > >
> > > > > > > Would also be nice to get an update from other committers
> > involved
> > > in
> > > > > the
> > > > > > > outlined tickets. Specifically whether the ticket has been
> merged
> > > to
> > > > > > master
> > > > > > > or not, and if not, what should be the expectation.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > vladisavj@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > >10. I would also like to include distributed Semaphore.
> > > Vladislav,
> > > > > any
> > > > > > > > >chance you can finish with it this week?
> > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > >
> > > > > > > > I will have it done by thursday.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Vladisav
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > dsetrakyan@apache.org
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com>
> > > wrote:
> > > > > > > > >
> > > > > > > > > > Can/will this include
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > ?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > I don’t see why not. Would be nice if one of the committers
> > > could
> > > > > > pick
> > > > > > > up
> > > > > > > > > the review for this patch.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > yzhdanov@apache.org
> > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >> Guys,
> > > > > > > > > > > >>
> > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> release
> > > > which
> > > > > > > will
> > > > > > > > > > > include
> > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > >>
> > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > >>
> > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > >>
> > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > >>
> > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > > > > non-collocated
> > > > > > > > > > data
> > > > > > > > > > > as
> > > > > > > > > > > >> well
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > >>
> > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > >>
> > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > >>
> > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > >>
> > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > optimizations
> > > > > > - I
> > > > > > > > > will
> > > > > > > > > > > >> merge
> > > > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug'
> > today
> > > or
> > > > > > > > tomorrow.
> > > > > > > > > > > >>
> > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > >>
> > > > > > > > > > > >> 10. I would also like to include distributed
> > Semaphore.
> > > > > > > Vladislav,
> > > > > > > > > any
> > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426
> >638
> > > > > > > > > > > >>
> > > > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > > > > mentioned
> > > > > > > > > issues,
> > > > > > > > > > > >> please respond to this email and let us know when
> can
> > we
> > > > > > expect
> > > > > > > > your
> > > > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > > > >>
> > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > >>
> > > > > > > > > > > >> --Yakov
> > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Sergi Vladykin <se...@gmail.com>.
Guys,
I'm currently struggling with distributed SQL join feature. The main
problem comes from the query optimization side because
when we assume to have everything collocated it is a problem of user to
achieve that, but now we have to:
1. Get to optimal plan which will not use distributed joins if it is
possible to achieve correct result using some collocated plan.
2. Correctly execute that plan because now it not only a question of
performance but also a question of getting correct results.
This all gets quite tricky when we are handling subqueries. Hope to finish
this in a day or two.
Sergi
2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <nt...@gridgain.com>:
> I implemented changes related to IGNITE-426 task. Currently investigating
> performance degradation for atomic caches. I expect the ticket to be merged
> in 2 days.
>
> On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com
> > wrote:
>
> > IGNITE-950 is taking more time to be merged than I originally estimated.
> We
> > had a couple of silly bugs, such as loosing cache operation context on
> > async cache operations, which led to hard-to debug failures in the
> platform
> > integration code.
> > I also added some sanity checks to indexing and found that I ran
> benchmarks
> > for new binary format on a model with externalizable classes, so the
> result
> > I've got were invalid, need more time to fix the model and re-run
> > benchmarks.
> >
> > I am currently waiting for another CI run, will give an update in several
> > hours.
> >
> > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> >
> > > Here are my current status for all interop-related stuff (you can view
> > > these tickets using query "project = IGNITE AND status in (Open, "In
> > > Progress", Reopened, Resolved, "Patch Available") AND component =
> interop
> > > AND fixVersion = 1.5"):
> > >
> > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > Trivial. Waiting for IGNITE-950 merge.
> > >
> > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > Trivial. Waiting for IGNITE-950 merge.
> > >
> > > *IGNITE-1803 - Optimized field lookup for queries*
> > > Ready. Waiting for IGNITE-950 to merge.
> > >
> > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > Not started yet. Waiting for IGNITE-950 to merge.
> > >
> > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > footer.*
> > > Not started yet.
> > >
> > > + Several minor tickets.
> > >
> > > All in all, I expect all these tickets to be ready in 2 days.
> > >
> > >
> > >
> > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > alexey.goncharuk@gmail.com
> > > > wrote:
> > >
> > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> *ticket*".
> > > The
> > > > changes are in ignite-950-new branch because it is a result of work
> on
> > > > multiple sub-tickets and it is currently used as an integration
> branch.
> > > >
> > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> > > >
> > > > > Alexey,
> > > > >
> > > > > I am confused. Why do you have 2 branches?
> > > > >
> > > > > D.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > alexey.goncharuk@gmail.com
> > > > > > wrote:
> > > > >
> > > > > > I am finalizing changes related to IGNITE-1486 branch. Currently
> > the
> > > > API
> > > > > > changes are finished and now I am mostly fixing the CI tests. In
> > > fact,
> > > > I
> > > > > > just submitted the latest fix related to the new .NET platform
> > > > > > functionality and hope CI tests will pass, in this case it will
> be
> > > > ready
> > > > > to
> > > > > > be merged tomorrow morning.
> > > > > > It would be nice if other community members reviewed my changes
> in
> > > > > > ignite-950-new branch before it gets to master.
> > > > > >
> > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > dsetrakyan@apache.org
> > > >:
> > > > > >
> > > > > > > Thanks Vladislav!
> > > > > > >
> > > > > > > Would also be nice to get an update from other committers
> > involved
> > > in
> > > > > the
> > > > > > > outlined tickets. Specifically whether the ticket has been
> merged
> > > to
> > > > > > master
> > > > > > > or not, and if not, what should be the expectation.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > vladisavj@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > >10. I would also like to include distributed Semaphore.
> > > Vladislav,
> > > > > any
> > > > > > > > >chance you can finish with it this week?
> > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > >
> > > > > > > > I will have it done by thursday.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Vladisav
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > dsetrakyan@apache.org
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com>
> > > wrote:
> > > > > > > > >
> > > > > > > > > > Can/will this include
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > ?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > I don’t see why not. Would be nice if one of the committers
> > > could
> > > > > > pick
> > > > > > > up
> > > > > > > > > the review for this patch.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > yzhdanov@apache.org
> > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >> Guys,
> > > > > > > > > > > >>
> > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> release
> > > > which
> > > > > > > will
> > > > > > > > > > > include
> > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > >>
> > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > >>
> > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > >>
> > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > >>
> > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > > > > non-collocated
> > > > > > > > > > data
> > > > > > > > > > > as
> > > > > > > > > > > >> well
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > >>
> > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > >>
> > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > >>
> > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > >>
> > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > optimizations
> > > > > > - I
> > > > > > > > > will
> > > > > > > > > > > >> merge
> > > > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug'
> > today
> > > or
> > > > > > > > tomorrow.
> > > > > > > > > > > >>
> > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > >>
> > > > > > > > > > > >> 10. I would also like to include distributed
> > Semaphore.
> > > > > > > Vladislav,
> > > > > > > > > any
> > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426
> >638
> > > > > > > > > > > >>
> > > > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > > > > mentioned
> > > > > > > > > issues,
> > > > > > > > > > > >> please respond to this email and let us know when
> can
> > we
> > > > > > expect
> > > > > > > > your
> > > > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > > > >>
> > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > >>
> > > > > > > > > > > >> --Yakov
> > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Nikolay Tikhonov <nt...@gridgain.com>.
I implemented changes related to IGNITE-426 task. Currently investigating
performance degradation for atomic caches. I expect the ticket to be merged
in 2 days.
On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <alexey.goncharuk@gmail.com
> wrote:
> IGNITE-950 is taking more time to be merged than I originally estimated. We
> had a couple of silly bugs, such as loosing cache operation context on
> async cache operations, which led to hard-to debug failures in the platform
> integration code.
> I also added some sanity checks to indexing and found that I ran benchmarks
> for new binary format on a model with externalizable classes, so the result
> I've got were invalid, need more time to fix the model and re-run
> benchmarks.
>
> I am currently waiting for another CI run, will give an update in several
> hours.
>
> 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
>
> > Here are my current status for all interop-related stuff (you can view
> > these tickets using query "project = IGNITE AND status in (Open, "In
> > Progress", Reopened, Resolved, "Patch Available") AND component = interop
> > AND fixVersion = 1.5"):
> >
> > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > Trivial. Waiting for IGNITE-950 merge.
> >
> > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > Trivial. Waiting for IGNITE-950 merge.
> >
> > *IGNITE-1803 - Optimized field lookup for queries*
> > Ready. Waiting for IGNITE-950 to merge.
> >
> > *IGNITE-1847 - Add "field" method to portable metadata.*
> > Not started yet. Waiting for IGNITE-950 to merge.
> >
> > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > footer.*
> > Not started yet.
> >
> > + Several minor tickets.
> >
> > All in all, I expect all these tickets to be ready in 2 days.
> >
> >
> >
> > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > alexey.goncharuk@gmail.com
> > > wrote:
> >
> > > I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*".
> > The
> > > changes are in ignite-950-new branch because it is a result of work on
> > > multiple sub-tickets and it is currently used as an integration branch.
> > >
> > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> > >
> > > > Alexey,
> > > >
> > > > I am confused. Why do you have 2 branches?
> > > >
> > > > D.
> > > >
> > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > alexey.goncharuk@gmail.com
> > > > > wrote:
> > > >
> > > > > I am finalizing changes related to IGNITE-1486 branch. Currently
> the
> > > API
> > > > > changes are finished and now I am mostly fixing the CI tests. In
> > fact,
> > > I
> > > > > just submitted the latest fix related to the new .NET platform
> > > > > functionality and hope CI tests will pass, in this case it will be
> > > ready
> > > > to
> > > > > be merged tomorrow morning.
> > > > > It would be nice if other community members reviewed my changes in
> > > > > ignite-950-new branch before it gets to master.
> > > > >
> > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> dsetrakyan@apache.org
> > >:
> > > > >
> > > > > > Thanks Vladislav!
> > > > > >
> > > > > > Would also be nice to get an update from other committers
> involved
> > in
> > > > the
> > > > > > outlined tickets. Specifically whether the ticket has been merged
> > to
> > > > > master
> > > > > > or not, and if not, what should be the expectation.
> > > > > >
> > > > > > Thanks,
> > > > > > D.
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > vladisavj@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > >10. I would also like to include distributed Semaphore.
> > Vladislav,
> > > > any
> > > > > > > >chance you can finish with it this week?
> > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > >
> > > > > > > I will have it done by thursday.
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Vladisav
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > dsetrakyan@apache.org
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com>
> > wrote:
> > > > > > > >
> > > > > > > > > Can/will this include
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > ?
> > > > > > > > >
> > > > > > > >
> > > > > > > > I don’t see why not. Would be nice if one of the committers
> > could
> > > > > pick
> > > > > > up
> > > > > > > > the review for this patch.
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > avinogradov@gridgain.com
> > > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > avinogradov@gridgain.com
> > > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > yzhdanov@apache.org
> > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >> Guys,
> > > > > > > > > > >>
> > > > > > > > > > >> I think we can start preparation to Ignite-1.5 release
> > > which
> > > > > > will
> > > > > > > > > > include
> > > > > > > > > > >> many interesting features:
> > > > > > > > > > >>
> > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > >>
> > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > >>
> > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > >>
> > > > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > > > non-collocated
> > > > > > > > > data
> > > > > > > > > > as
> > > > > > > > > > >> well
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > >>
> > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > >>
> > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > >>
> > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > >>
> > > > > > > > > > >> 8. Significant transactional cache performance
> > > optimizations
> > > > > - I
> > > > > > > > will
> > > > > > > > > > >> merge
> > > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug'
> today
> > or
> > > > > > > tomorrow.
> > > > > > > > > > >>
> > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > >>
> > > > > > > > > > >> 10. I would also like to include distributed
> Semaphore.
> > > > > > Vladislav,
> > > > > > > > any
> > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > > > >>
> > > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > > > mentioned
> > > > > > > > issues,
> > > > > > > > > > >> please respond to this email and let us know when can
> we
> > > > > expect
> > > > > > > your
> > > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > > >>
> > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > >>
> > > > > > > > > > >> --Yakov
> > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
IGNITE-950 is taking more time to be merged than I originally estimated. We
had a couple of silly bugs, such as loosing cache operation context on
async cache operations, which led to hard-to debug failures in the platform
integration code.
I also added some sanity checks to indexing and found that I ran benchmarks
for new binary format on a model with externalizable classes, so the result
I've got were invalid, need more time to fix the model and re-run
benchmarks.
I am currently waiting for another CI run, will give an update in several
hours.
2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> Here are my current status for all interop-related stuff (you can view
> these tickets using query "project = IGNITE AND status in (Open, "In
> Progress", Reopened, Resolved, "Patch Available") AND component = interop
> AND fixVersion = 1.5"):
>
> *IGNITE-1819 - Remove metadataEnabled flag in Java*
> Trivial. Waiting for IGNITE-950 merge.
>
> *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> Trivial. Waiting for IGNITE-950 merge.
>
> *IGNITE-1803 - Optimized field lookup for queries*
> Ready. Waiting for IGNITE-950 to merge.
>
> *IGNITE-1847 - Add "field" method to portable metadata.*
> Not started yet. Waiting for IGNITE-950 to merge.
>
> *IGNITE-1816 - Optionally do not write field IDs to portable object
> footer.*
> Not started yet.
>
> + Several minor tickets.
>
> All in all, I expect all these tickets to be ready in 2 days.
>
>
>
> On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com
> > wrote:
>
> > I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*".
> The
> > changes are in ignite-950-new branch because it is a result of work on
> > multiple sub-tickets and it is currently used as an integration branch.
> >
> > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > Alexey,
> > >
> > > I am confused. Why do you have 2 branches?
> > >
> > > D.
> > >
> > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > alexey.goncharuk@gmail.com
> > > > wrote:
> > >
> > > > I am finalizing changes related to IGNITE-1486 branch. Currently the
> > API
> > > > changes are finished and now I am mostly fixing the CI tests. In
> fact,
> > I
> > > > just submitted the latest fix related to the new .NET platform
> > > > functionality and hope CI tests will pass, in this case it will be
> > ready
> > > to
> > > > be merged tomorrow morning.
> > > > It would be nice if other community members reviewed my changes in
> > > > ignite-950-new branch before it gets to master.
> > > >
> > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org
> >:
> > > >
> > > > > Thanks Vladislav!
> > > > >
> > > > > Would also be nice to get an update from other committers involved
> in
> > > the
> > > > > outlined tickets. Specifically whether the ticket has been merged
> to
> > > > master
> > > > > or not, and if not, what should be the expectation.
> > > > >
> > > > > Thanks,
> > > > > D.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > vladisavj@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > >10. I would also like to include distributed Semaphore.
> Vladislav,
> > > any
> > > > > > >chance you can finish with it this week?
> > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > >
> > > > > > I will have it done by thursday.
> > > > > >
> > > > > > Best regards,
> > > > > > Vladisav
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > dsetrakyan@apache.org
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com>
> wrote:
> > > > > > >
> > > > > > > > Can/will this include
> > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > ?
> > > > > > > >
> > > > > > >
> > > > > > > I don’t see why not. Would be nice if one of the committers
> could
> > > > pick
> > > > > up
> > > > > > > the review for this patch.
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > avinogradov@gridgain.com
> > > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > avinogradov@gridgain.com
> > > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > yzhdanov@apache.org
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >> Guys,
> > > > > > > > > >>
> > > > > > > > > >> I think we can start preparation to Ignite-1.5 release
> > which
> > > > > will
> > > > > > > > > include
> > > > > > > > > >> many interesting features:
> > > > > > > > > >>
> > > > > > > > > >> 1. Portable object API
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > >>
> > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > >>
> > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > >>
> > > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > > non-collocated
> > > > > > > > data
> > > > > > > > > as
> > > > > > > > > >> well
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > >>
> > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > >>
> > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > >>
> > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > >>
> > > > > > > > > >> 8. Significant transactional cache performance
> > optimizations
> > > > - I
> > > > > > > will
> > > > > > > > > >> merge
> > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug' today
> or
> > > > > > tomorrow.
> > > > > > > > > >>
> > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > >>
> > > > > > > > > >> 10. I would also like to include distributed Semaphore.
> > > > > Vladislav,
> > > > > > > any
> > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > > >>
> > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > > mentioned
> > > > > > > issues,
> > > > > > > > > >> please respond to this email and let us know when can we
> > > > expect
> > > > > > your
> > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > >>
> > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > >>
> > > > > > > > > >> --Yakov
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Here are my current status for all interop-related stuff (you can view
these tickets using query "project = IGNITE AND status in (Open, "In
Progress", Reopened, Resolved, "Patch Available") AND component = interop
AND fixVersion = 1.5"):
*IGNITE-1819 - Remove metadataEnabled flag in Java*
Trivial. Waiting for IGNITE-950 merge.
*IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
Trivial. Waiting for IGNITE-950 merge.
*IGNITE-1803 - Optimized field lookup for queries*
Ready. Waiting for IGNITE-950 to merge.
*IGNITE-1847 - Add "field" method to portable metadata.*
Not started yet. Waiting for IGNITE-950 to merge.
*IGNITE-1816 - Optionally do not write field IDs to portable object footer.*
Not started yet.
+ Several minor tickets.
All in all, I expect all these tickets to be ready in 2 days.
On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <alexey.goncharuk@gmail.com
> wrote:
> I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*". The
> changes are in ignite-950-new branch because it is a result of work on
> multiple sub-tickets and it is currently used as an integration branch.
>
> 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
>
> > Alexey,
> >
> > I am confused. Why do you have 2 branches?
> >
> > D.
> >
> > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > alexey.goncharuk@gmail.com
> > > wrote:
> >
> > > I am finalizing changes related to IGNITE-1486 branch. Currently the
> API
> > > changes are finished and now I am mostly fixing the CI tests. In fact,
> I
> > > just submitted the latest fix related to the new .NET platform
> > > functionality and hope CI tests will pass, in this case it will be
> ready
> > to
> > > be merged tomorrow morning.
> > > It would be nice if other community members reviewed my changes in
> > > ignite-950-new branch before it gets to master.
> > >
> > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> > >
> > > > Thanks Vladislav!
> > > >
> > > > Would also be nice to get an update from other committers involved in
> > the
> > > > outlined tickets. Specifically whether the ticket has been merged to
> > > master
> > > > or not, and if not, what should be the expectation.
> > > >
> > > > Thanks,
> > > > D.
> > > >
> > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > vladisavj@gmail.com>
> > > > wrote:
> > > >
> > > > > >10. I would also like to include distributed Semaphore. Vladislav,
> > any
> > > > > >chance you can finish with it this week?
> > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > >
> > > > > I will have it done by thursday.
> > > > >
> > > > > Best regards,
> > > > > Vladisav
> > > > >
> > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > dsetrakyan@apache.org
> > > > >
> > > > > wrote:
> > > > >
> > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
> > > > > >
> > > > > > > Can/will this include
> > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > ?
> > > > > > >
> > > > > >
> > > > > > I don’t see why not. Would be nice if one of the committers could
> > > pick
> > > > up
> > > > > > the review for this patch.
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > avinogradov@gridgain.com
> > > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Branch ignite-1.5 created.
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > avinogradov@gridgain.com
> > > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > yzhdanov@apache.org
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >> Guys,
> > > > > > > > >>
> > > > > > > > >> I think we can start preparation to Ignite-1.5 release
> which
> > > > will
> > > > > > > > include
> > > > > > > > >> many interesting features:
> > > > > > > > >>
> > > > > > > > >> 1. Portable object API
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > >>
> > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > >>
> > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > >>
> > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > non-collocated
> > > > > > > data
> > > > > > > > as
> > > > > > > > >> well
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > >>
> > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > >>
> > > > > > > > >> 6. MQTT streamer
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > >>
> > > > > > > > >> 7. Continuous query failover
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > >>
> > > > > > > > >> 8. Significant transactional cache performance
> optimizations
> > > - I
> > > > > > will
> > > > > > > > >> merge
> > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > > > > tomorrow.
> > > > > > > > >>
> > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > >>
> > > > > > > > >> 10. I would also like to include distributed Semaphore.
> > > > Vladislav,
> > > > > > any
> > > > > > > > >> chance you can finish with it this week?
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > >>
> > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > mentioned
> > > > > > issues,
> > > > > > > > >> please respond to this email and let us know when can we
> > > expect
> > > > > your
> > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > >>
> > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > >>
> > > > > > > > >> --Yakov
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*". The
changes are in ignite-950-new branch because it is a result of work on
multiple sub-tickets and it is currently used as an integration branch.
2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> Alexey,
>
> I am confused. Why do you have 2 branches?
>
> D.
>
> On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com
> > wrote:
>
> > I am finalizing changes related to IGNITE-1486 branch. Currently the API
> > changes are finished and now I am mostly fixing the CI tests. In fact, I
> > just submitted the latest fix related to the new .NET platform
> > functionality and hope CI tests will pass, in this case it will be ready
> to
> > be merged tomorrow morning.
> > It would be nice if other community members reviewed my changes in
> > ignite-950-new branch before it gets to master.
> >
> > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> >
> > > Thanks Vladislav!
> > >
> > > Would also be nice to get an update from other committers involved in
> the
> > > outlined tickets. Specifically whether the ticket has been merged to
> > master
> > > or not, and if not, what should be the expectation.
> > >
> > > Thanks,
> > > D.
> > >
> > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > vladisavj@gmail.com>
> > > wrote:
> > >
> > > > >10. I would also like to include distributed Semaphore. Vladislav,
> any
> > > > >chance you can finish with it this week?
> > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > >
> > > > I will have it done by thursday.
> > > >
> > > > Best regards,
> > > > Vladisav
> > > >
> > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > dsetrakyan@apache.org
> > > >
> > > > wrote:
> > > >
> > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
> > > > >
> > > > > > Can/will this include
> > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > ?
> > > > > >
> > > > >
> > > > > I don’t see why not. Would be nice if one of the committers could
> > pick
> > > up
> > > > > the review for this patch.
> > > > >
> > > > >
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > avinogradov@gridgain.com
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Branch ignite-1.5 created.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > avinogradov@gridgain.com
> > > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > yzhdanov@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Guys,
> > > > > > > >>
> > > > > > > >> I think we can start preparation to Ignite-1.5 release which
> > > will
> > > > > > > include
> > > > > > > >> many interesting features:
> > > > > > > >>
> > > > > > > >> 1. Portable object API
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > >>
> > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > >>
> > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > >>
> > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > non-collocated
> > > > > > data
> > > > > > > as
> > > > > > > >> well
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > >>
> > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > >>
> > > > > > > >> 6. MQTT streamer
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > >>
> > > > > > > >> 7. Continuous query failover
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > >>
> > > > > > > >> 8. Significant transactional cache performance optimizations
> > - I
> > > > > will
> > > > > > > >> merge
> > > > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > > > tomorrow.
> > > > > > > >>
> > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > >>
> > > > > > > >> 10. I would also like to include distributed Semaphore.
> > > Vladislav,
> > > > > any
> > > > > > > >> chance you can finish with it this week?
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > >>
> > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> mentioned
> > > > > issues,
> > > > > > > >> please respond to this email and let us know when can we
> > expect
> > > > your
> > > > > > > >> changes being merged to master and release branch?
> > > > > > > >>
> > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > >>
> > > > > > > >> --Yakov
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Alexey,
I am confused. Why do you have 2 branches?
D.
On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <alexey.goncharuk@gmail.com
> wrote:
> I am finalizing changes related to IGNITE-1486 branch. Currently the API
> changes are finished and now I am mostly fixing the CI tests. In fact, I
> just submitted the latest fix related to the new .NET platform
> functionality and hope CI tests will pass, in this case it will be ready to
> be merged tomorrow morning.
> It would be nice if other community members reviewed my changes in
> ignite-950-new branch before it gets to master.
>
> 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
>
> > Thanks Vladislav!
> >
> > Would also be nice to get an update from other committers involved in the
> > outlined tickets. Specifically whether the ticket has been merged to
> master
> > or not, and if not, what should be the expectation.
> >
> > Thanks,
> > D.
> >
> > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> vladisavj@gmail.com>
> > wrote:
> >
> > > >10. I would also like to include distributed Semaphore. Vladislav, any
> > > >chance you can finish with it this week?
> > > >https://issues.apache.org/jira/browse/IGNITE-
> > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > >
> > > I will have it done by thursday.
> > >
> > > Best regards,
> > > Vladisav
> > >
> > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org
> > >
> > > wrote:
> > >
> > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
> > > >
> > > > > Can/will this include
> > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > ?
> > > > >
> > > >
> > > > I don’t see why not. Would be nice if one of the committers could
> pick
> > up
> > > > the review for this patch.
> > > >
> > > >
> > > > >
> > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > avinogradov@gridgain.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > Branch ignite-1.5 created.
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > avinogradov@gridgain.com
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > I assume that correct link at 10th feature is
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > yzhdanov@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > >> Guys,
> > > > > > >>
> > > > > > >> I think we can start preparation to Ignite-1.5 release which
> > will
> > > > > > include
> > > > > > >> many interesting features:
> > > > > > >>
> > > > > > >> 1. Portable object API
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > >>
> > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > >>
> > > > > > >> 3. Optimistic serializable transactions
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > >>
> > > > > > >> 4. Distributed SQL joins - we will be able to query
> > non-collocated
> > > > > data
> > > > > > as
> > > > > > >> well
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > >>
> > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > >>
> > > > > > >> 6. MQTT streamer
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > >>
> > > > > > >> 7. Continuous query failover
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > >>
> > > > > > >> 8. Significant transactional cache performance optimizations
> - I
> > > > will
> > > > > > >> merge
> > > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > > tomorrow.
> > > > > > >>
> > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > >>
> > > > > > >> 10. I would also like to include distributed Semaphore.
> > Vladislav,
> > > > any
> > > > > > >> chance you can finish with it this week?
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > >>
> > > > > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > > > issues,
> > > > > > >> please respond to this email and let us know when can we
> expect
> > > your
> > > > > > >> changes being merged to master and release branch?
> > > > > > >>
> > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > >>
> > > > > > >> --Yakov
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
I am finalizing changes related to IGNITE-1486 branch. Currently the API
changes are finished and now I am mostly fixing the CI tests. In fact, I
just submitted the latest fix related to the new .NET platform
functionality and hope CI tests will pass, in this case it will be ready to
be merged tomorrow morning.
It would be nice if other community members reviewed my changes in
ignite-950-new branch before it gets to master.
2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <ds...@apache.org>:
> Thanks Vladislav!
>
> Would also be nice to get an update from other committers involved in the
> outlined tickets. Specifically whether the ticket has been merged to master
> or not, and if not, what should be the expectation.
>
> Thanks,
> D.
>
> On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <vl...@gmail.com>
> wrote:
>
> > >10. I would also like to include distributed Semaphore. Vladislav, any
> > >chance you can finish with it this week?
> > >https://issues.apache.org/jira/browse/IGNITE-
> > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> >
> > I will have it done by thursday.
> >
> > Best regards,
> > Vladisav
> >
> > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> > wrote:
> >
> > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
> > >
> > > > Can/will this include
> > https://issues.apache.org/jira/browse/IGNITE-1681
> > > ?
> > > >
> > >
> > > I don’t see why not. Would be nice if one of the committers could pick
> up
> > > the review for this patch.
> > >
> > >
> > > >
> > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > avinogradov@gridgain.com
> > > > >
> > > > wrote:
> > > >
> > > > > Branch ignite-1.5 created.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > avinogradov@gridgain.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > I assume that correct link at 10th feature is
> > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> yzhdanov@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > >> Guys,
> > > > > >>
> > > > > >> I think we can start preparation to Ignite-1.5 release which
> will
> > > > > include
> > > > > >> many interesting features:
> > > > > >>
> > > > > >> 1. Portable object API
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > >>
> > > > > >> 2. Ignite.NET and Ignite C++
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > >>
> > > > > >> 3. Optimistic serializable transactions
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > >>
> > > > > >> 4. Distributed SQL joins - we will be able to query
> non-collocated
> > > > data
> > > > > as
> > > > > >> well
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > >>
> > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > >>
> > > > > >> 6. MQTT streamer
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > >>
> > > > > >> 7. Continuous query failover
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > >>
> > > > > >> 8. Significant transactional cache performance optimizations - I
> > > will
> > > > > >> merge
> > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > tomorrow.
> > > > > >>
> > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > >>
> > > > > >> 10. I would also like to include distributed Semaphore.
> Vladislav,
> > > any
> > > > > >> chance you can finish with it this week?
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > >>
> > > > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > > issues,
> > > > > >> please respond to this email and let us know when can we expect
> > your
> > > > > >> changes being merged to master and release branch?
> > > > > >>
> > > > > >> Can someone create ignite-1.5 release branch?
> > > > > >>
> > > > > >> --Yakov
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Thanks Vladislav!
Would also be nice to get an update from other committers involved in the
outlined tickets. Specifically whether the ticket has been merged to master
or not, and if not, what should be the expectation.
Thanks,
D.
On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <vl...@gmail.com>
wrote:
> >10. I would also like to include distributed Semaphore. Vladislav, any
> >chance you can finish with it this week?
> >https://issues.apache.org/jira/browse/IGNITE-
> ><https://issues.apache.org/jira/browse/IGNITE-426>638
>
> I will have it done by thursday.
>
> Best regards,
> Vladisav
>
> On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
> > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
> >
> > > Can/will this include
> https://issues.apache.org/jira/browse/IGNITE-1681
> > ?
> > >
> >
> > I don’t see why not. Would be nice if one of the committers could pick up
> > the review for this patch.
> >
> >
> > >
> > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > avinogradov@gridgain.com
> > > >
> > > wrote:
> > >
> > > > Branch ignite-1.5 created.
> > > >
> > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > avinogradov@gridgain.com
> > > > >
> > > > wrote:
> > > >
> > > > > I assume that correct link at 10th feature is
> > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > >
> > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yzhdanov@apache.org
> >
> > > > wrote:
> > > > >
> > > > >> Guys,
> > > > >>
> > > > >> I think we can start preparation to Ignite-1.5 release which will
> > > > include
> > > > >> many interesting features:
> > > > >>
> > > > >> 1. Portable object API
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > >>
> > > > >> 2. Ignite.NET and Ignite C++
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > >>
> > > > >> 3. Optimistic serializable transactions
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > >>
> > > > >> 4. Distributed SQL joins - we will be able to query non-collocated
> > > data
> > > > as
> > > > >> well
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > >>
> > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > >>
> > > > >> 6. MQTT streamer
> > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > >>
> > > > >> 7. Continuous query failover
> > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > >>
> > > > >> 8. Significant transactional cache performance optimizations - I
> > will
> > > > >> merge
> > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> tomorrow.
> > > > >>
> > > > >> 9. Many stability and fault-tolerance fixes.
> > > > >>
> > > > >> 10. I would also like to include distributed Semaphore. Vladislav,
> > any
> > > > >> chance you can finish with it this week?
> > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > >>
> > > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > issues,
> > > > >> please respond to this email and let us know when can we expect
> your
> > > > >> changes being merged to master and release branch?
> > > > >>
> > > > >> Can someone create ignite-1.5 release branch?
> > > > >>
> > > > >> --Yakov
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Alexey Goncharuk <al...@gmail.com>.
Guys,
A quick update on the release status.
I have spotted several potential slowdowns that I would like to add to 1.5
release. I am currently working in a separate branch and preliminary
testing showed that we can get about 4-5% performance improvement in tx-put
benchmark. There are other potential improvements that I did not benchmark
yet, but I believe it may add another 4-5% for the same benchmark.
Also, as Vladimir noticed, there is IGNITE-1377 issue that is critical for
the release. I can take a closer look at it once I finish with the
performance improvements, however if there is anyone who can handle it now
- it would be great!
2015-11-10 16:36 GMT+03:00 Yakov Zhdanov <yz...@apache.org>:
> Vladislav, do you have any updates for
> https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
>
> --Yakov
>
> 2015-11-02 22:23 GMT+03:00 Vladisav Jelisavcic <vl...@gmail.com>:
>
> > >10. I would also like to include distributed Semaphore. Vladislav, any
> > >chance you can finish with it this week?
> > >https://issues.apache.org/jira/browse/IGNITE-
> > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> >
> > I will have it done by thursday.
> >
> > Best regards,
> > Vladisav
> >
> > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> > wrote:
> >
> > > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
> > >
> > > > Can/will this include
> > https://issues.apache.org/jira/browse/IGNITE-1681
> > > ?
> > > >
> > >
> > > I don’t see why not. Would be nice if one of the committers could pick
> up
> > > the review for this patch.
> > >
> > >
> > > >
> > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > avinogradov@gridgain.com
> > > > >
> > > > wrote:
> > > >
> > > > > Branch ignite-1.5 created.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > avinogradov@gridgain.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > I assume that correct link at 10th feature is
> > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> yzhdanov@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > >> Guys,
> > > > > >>
> > > > > >> I think we can start preparation to Ignite-1.5 release which
> will
> > > > > include
> > > > > >> many interesting features:
> > > > > >>
> > > > > >> 1. Portable object API
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > >>
> > > > > >> 2. Ignite.NET and Ignite C++
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > >>
> > > > > >> 3. Optimistic serializable transactions
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > >>
> > > > > >> 4. Distributed SQL joins - we will be able to query
> non-collocated
> > > > data
> > > > > as
> > > > > >> well
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > >>
> > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > >>
> > > > > >> 6. MQTT streamer
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > >>
> > > > > >> 7. Continuous query failover
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > >>
> > > > > >> 8. Significant transactional cache performance optimizations - I
> > > will
> > > > > >> merge
> > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > tomorrow.
> > > > > >>
> > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > >>
> > > > > >> 10. I would also like to include distributed Semaphore.
> Vladislav,
> > > any
> > > > > >> chance you can finish with it this week?
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > >>
> > > > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > > issues,
> > > > > >> please respond to this email and let us know when can we expect
> > your
> > > > > >> changes being merged to master and release branch?
> > > > > >>
> > > > > >> Can someone create ignite-1.5 release branch?
> > > > > >>
> > > > > >> --Yakov
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Yakov Zhdanov <yz...@apache.org>.
Vladislav, do you have any updates for
https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
--Yakov
2015-11-02 22:23 GMT+03:00 Vladisav Jelisavcic <vl...@gmail.com>:
> >10. I would also like to include distributed Semaphore. Vladislav, any
> >chance you can finish with it this week?
> >https://issues.apache.org/jira/browse/IGNITE-
> ><https://issues.apache.org/jira/browse/IGNITE-426>638
>
> I will have it done by thursday.
>
> Best regards,
> Vladisav
>
> On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
> > On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
> >
> > > Can/will this include
> https://issues.apache.org/jira/browse/IGNITE-1681
> > ?
> > >
> >
> > I don’t see why not. Would be nice if one of the committers could pick up
> > the review for this patch.
> >
> >
> > >
> > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > avinogradov@gridgain.com
> > > >
> > > wrote:
> > >
> > > > Branch ignite-1.5 created.
> > > >
> > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > avinogradov@gridgain.com
> > > > >
> > > > wrote:
> > > >
> > > > > I assume that correct link at 10th feature is
> > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > >
> > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yzhdanov@apache.org
> >
> > > > wrote:
> > > > >
> > > > >> Guys,
> > > > >>
> > > > >> I think we can start preparation to Ignite-1.5 release which will
> > > > include
> > > > >> many interesting features:
> > > > >>
> > > > >> 1. Portable object API
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > >>
> > > > >> 2. Ignite.NET and Ignite C++
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > >>
> > > > >> 3. Optimistic serializable transactions
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > >>
> > > > >> 4. Distributed SQL joins - we will be able to query non-collocated
> > > data
> > > > as
> > > > >> well
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > >>
> > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > >>
> > > > >> 6. MQTT streamer
> > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > >>
> > > > >> 7. Continuous query failover
> > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > >>
> > > > >> 8. Significant transactional cache performance optimizations - I
> > will
> > > > >> merge
> > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> tomorrow.
> > > > >>
> > > > >> 9. Many stability and fault-tolerance fixes.
> > > > >>
> > > > >> 10. I would also like to include distributed Semaphore. Vladislav,
> > any
> > > > >> chance you can finish with it this week?
> > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > >>
> > > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > issues,
> > > > >> please respond to this email and let us know when can we expect
> your
> > > > >> changes being merged to master and release branch?
> > > > >>
> > > > >> Can someone create ignite-1.5 release branch?
> > > > >>
> > > > >> --Yakov
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Vladisav Jelisavcic <vl...@gmail.com>.
>10. I would also like to include distributed Semaphore. Vladislav, any
>chance you can finish with it this week?
>https://issues.apache.org/jira/browse/IGNITE-
><https://issues.apache.org/jira/browse/IGNITE-426>638
I will have it done by thursday.
Best regards,
Vladisav
On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
>
> > Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681
> ?
> >
>
> I don’t see why not. Would be nice if one of the committers could pick up
> the review for this patch.
>
>
> >
> > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> avinogradov@gridgain.com
> > >
> > wrote:
> >
> > > Branch ignite-1.5 created.
> > >
> > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > avinogradov@gridgain.com
> > > >
> > > wrote:
> > >
> > > > I assume that correct link at 10th feature is
> > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > >
> > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org>
> > > wrote:
> > > >
> > > >> Guys,
> > > >>
> > > >> I think we can start preparation to Ignite-1.5 release which will
> > > include
> > > >> many interesting features:
> > > >>
> > > >> 1. Portable object API
> > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > >>
> > > >> 2. Ignite.NET and Ignite C++
> > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > >>
> > > >> 3. Optimistic serializable transactions
> > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > >>
> > > >> 4. Distributed SQL joins - we will be able to query non-collocated
> > data
> > > as
> > > >> well
> > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > >>
> > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > >>
> > > >> 6. MQTT streamer
> > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > >>
> > > >> 7. Continuous query failover
> > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > >>
> > > >> 8. Significant transactional cache performance optimizations - I
> will
> > > >> merge
> > > >> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > > >>
> > > >> 9. Many stability and fault-tolerance fixes.
> > > >>
> > > >> 10. I would also like to include distributed Semaphore. Vladislav,
> any
> > > >> chance you can finish with it this week?
> > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > >>
> > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> issues,
> > > >> please respond to this email and let us know when can we expect your
> > > >> changes being merged to master and release branch?
> > > >>
> > > >> Can someone create ignite-1.5 release branch?
> > > >>
> > > >> --Yakov
> > > >>
> > > >
> > > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by Dmitriy Setrakyan <ds...@apache.org>.
On Mon, Nov 2, 2015 at 6:58 AM, M G <en...@gmail.com> wrote:
> Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681 ?
>
I don’t see why not. Would be nice if one of the committers could pick up
the review for this patch.
>
> On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <avinogradov@gridgain.com
> >
> wrote:
>
> > Branch ignite-1.5 created.
> >
> > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> avinogradov@gridgain.com
> > >
> > wrote:
> >
> > > I assume that correct link at 10th feature is
> > > https://issues.apache.org/jira/browse/IGNITE-638
> > >
> > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org>
> > wrote:
> > >
> > >> Guys,
> > >>
> > >> I think we can start preparation to Ignite-1.5 release which will
> > include
> > >> many interesting features:
> > >>
> > >> 1. Portable object API
> > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > >>
> > >> 2. Ignite.NET and Ignite C++
> > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > >>
> > >> 3. Optimistic serializable transactions
> > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > >>
> > >> 4. Distributed SQL joins - we will be able to query non-collocated
> data
> > as
> > >> well
> > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > >>
> > >> 5. Enhanced Oracle and IBM JDK interoperability
> > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > >>
> > >> 6. MQTT streamer
> > >> https://issues.apache.org/jira/browse/IGNITE-535
> > >>
> > >> 7. Continuous query failover
> > >> https://issues.apache.org/jira/browse/IGNITE-426
> > >>
> > >> 8. Significant transactional cache performance optimizations - I will
> > >> merge
> > >> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > >>
> > >> 9. Many stability and fault-tolerance fixes.
> > >>
> > >> 10. I would also like to include distributed Semaphore. Vladislav, any
> > >> chance you can finish with it this week?
> > >> https://issues.apache.org/jira/browse/IGNITE-
> > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > >>
> > >> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> > >> please respond to this email and let us know when can we expect your
> > >> changes being merged to master and release branch?
> > >>
> > >> Can someone create ignite-1.5 release branch?
> > >>
> > >> --Yakov
> > >>
> > >
> > >
> >
>
Re: Ignite-1.5 Release
Posted by M G <en...@gmail.com>.
Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681 ?
On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <av...@gridgain.com>
wrote:
> Branch ignite-1.5 created.
>
> On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <avinogradov@gridgain.com
> >
> wrote:
>
> > I assume that correct link at 10th feature is
> > https://issues.apache.org/jira/browse/IGNITE-638
> >
> > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org>
> wrote:
> >
> >> Guys,
> >>
> >> I think we can start preparation to Ignite-1.5 release which will
> include
> >> many interesting features:
> >>
> >> 1. Portable object API
> >> https://issues.apache.org/jira/browse/IGNITE-1486
> >>
> >> 2. Ignite.NET and Ignite C++
> >> https://issues.apache.org/jira/browse/IGNITE-1282
> >>
> >> 3. Optimistic serializable transactions
> >> https://issues.apache.org/jira/browse/IGNITE-1607
> >>
> >> 4. Distributed SQL joins - we will be able to query non-collocated data
> as
> >> well
> >> https://issues.apache.org/jira/browse/IGNITE-1232
> >>
> >> 5. Enhanced Oracle and IBM JDK interoperability
> >> https://issues.apache.org/jira/browse/IGNITE-1526
> >>
> >> 6. MQTT streamer
> >> https://issues.apache.org/jira/browse/IGNITE-535
> >>
> >> 7. Continuous query failover
> >> https://issues.apache.org/jira/browse/IGNITE-426
> >>
> >> 8. Significant transactional cache performance optimizations - I will
> >> merge
> >> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> >>
> >> 9. Many stability and fault-tolerance fixes.
> >>
> >> 10. I would also like to include distributed Semaphore. Vladislav, any
> >> chance you can finish with it this week?
> >> https://issues.apache.org/jira/browse/IGNITE-
> >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> >>
> >> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> >> please respond to this email and let us know when can we expect your
> >> changes being merged to master and release branch?
> >>
> >> Can someone create ignite-1.5 release branch?
> >>
> >> --Yakov
> >>
> >
> >
>
Re: Ignite-1.5 Release
Posted by Anton Vinogradov <av...@gridgain.com>.
Branch ignite-1.5 created.
On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <av...@gridgain.com>
wrote:
> I assume that correct link at 10th feature is
> https://issues.apache.org/jira/browse/IGNITE-638
>
> On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org> wrote:
>
>> Guys,
>>
>> I think we can start preparation to Ignite-1.5 release which will include
>> many interesting features:
>>
>> 1. Portable object API
>> https://issues.apache.org/jira/browse/IGNITE-1486
>>
>> 2. Ignite.NET and Ignite C++
>> https://issues.apache.org/jira/browse/IGNITE-1282
>>
>> 3. Optimistic serializable transactions
>> https://issues.apache.org/jira/browse/IGNITE-1607
>>
>> 4. Distributed SQL joins - we will be able to query non-collocated data as
>> well
>> https://issues.apache.org/jira/browse/IGNITE-1232
>>
>> 5. Enhanced Oracle and IBM JDK interoperability
>> https://issues.apache.org/jira/browse/IGNITE-1526
>>
>> 6. MQTT streamer
>> https://issues.apache.org/jira/browse/IGNITE-535
>>
>> 7. Continuous query failover
>> https://issues.apache.org/jira/browse/IGNITE-426
>>
>> 8. Significant transactional cache performance optimizations - I will
>> merge
>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>>
>> 9. Many stability and fault-tolerance fixes.
>>
>> 10. I would also like to include distributed Semaphore. Vladislav, any
>> chance you can finish with it this week?
>> https://issues.apache.org/jira/browse/IGNITE-
>> <https://issues.apache.org/jira/browse/IGNITE-426>638
>>
>> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
>> please respond to this email and let us know when can we expect your
>> changes being merged to master and release branch?
>>
>> Can someone create ignite-1.5 release branch?
>>
>> --Yakov
>>
>
>
Re: Ignite-1.5 Release
Posted by Anton Vinogradov <av...@gridgain.com>.
I assume that correct link at 10th feature is
https://issues.apache.org/jira/browse/IGNITE-638
On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> Guys,
>
> I think we can start preparation to Ignite-1.5 release which will include
> many interesting features:
>
> 1. Portable object API
> https://issues.apache.org/jira/browse/IGNITE-1486
>
> 2. Ignite.NET and Ignite C++
> https://issues.apache.org/jira/browse/IGNITE-1282
>
> 3. Optimistic serializable transactions
> https://issues.apache.org/jira/browse/IGNITE-1607
>
> 4. Distributed SQL joins - we will be able to query non-collocated data as
> well
> https://issues.apache.org/jira/browse/IGNITE-1232
>
> 5. Enhanced Oracle and IBM JDK interoperability
> https://issues.apache.org/jira/browse/IGNITE-1526
>
> 6. MQTT streamer
> https://issues.apache.org/jira/browse/IGNITE-535
>
> 7. Continuous query failover
> https://issues.apache.org/jira/browse/IGNITE-426
>
> 8. Significant transactional cache performance optimizations - I will merge
> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>
> 9. Many stability and fault-tolerance fixes.
>
> 10. I would also like to include distributed Semaphore. Vladislav, any
> chance you can finish with it this week?
> https://issues.apache.org/jira/browse/IGNITE-
> <https://issues.apache.org/jira/browse/IGNITE-426>638
>
> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> please respond to this email and let us know when can we expect your
> changes being merged to master and release branch?
>
> Can someone create ignite-1.5 release branch?
>
> --Yakov
>