Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CADdasW4L=uW-Q9YxeLxhhVRF=C3FWNGawg0=b0ZkgTdaLnF3uA@mail.gmail.com>
References: 
 <CAGcMBHjJ3zuVrKiOnRq7jfM5p24Ji8XP2zuKQnDpwaHTfg0Zgg@mail.gmail.com>
	<CAKoNANsHANEjHYeL7vsbkER=w5dMxFmNBQDQQHuZT-z5o2yPyQ@mail.gmail.com>
	<CADdasW4L=uW-Q9YxeLxhhVRF=C3FWNGawg0=b0ZkgTdaLnF3uA@mail.gmail.com>
Date: Wed, 11 Nov 2015 13:05:40 +0300
Message-ID: 
 <CAGcMBHj8ZE9A=D25=wS6qLt=yCx5g1D1WV82pxedv6Qd2eFV9w@mail.gmail.com>
Subject: Re: Ignite-1.5 Release
From: Yakov Zhdanov <yzhdanov@apache.org>
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=047d7b3a8290f742e0052440f78a

--047d7b3a8290f742e0052440f78a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 <vladisavj@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 releasin=
g
> 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 transactio=
n
> if possible) [keys=3D[UserKeyCacheObjectImpl [val=3DGridCacheInternalKeyI=
mpl
> [name=3Dac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=3Dtrue]],
> node=3Dc321fcc4-5db5-4b03-9811-6a5587f2c253]
> ...
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Faile=
d
> to acquire lock for keys (primary node left grid, retry transaction if
> possible) [keys=3D[UserKeyCacheObjectImpl [val=3DGridCacheInternalKeyImpl
> [name=3Dac83b8cb-3052-49a6-9301-81b20b0ecf3a], hasValBytes=3Dtrue]],
> node=3Dc321fcc4-5db5-4b03-9811-6a5587f2c253]
> at
>
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.Gri=
dDhtColocatedLockFuture.newTopologyException(GridDhtColocatedLockFuture.jav=
a: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 <raulk@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 =3D> 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=C3=BAl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data a=
nd
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalan=
i
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Mon, Nov 2, 2015 at 1: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 da=
ta
> > 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, an=
y
> > > 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
> > >
> >
>

--047d7b3a8290f742e0052440f78a--