Re: Cassandra cache store [IGNITE-1371]

[Denis Magda]

I think it makes sense to make this feature the one that drives the next 
release.


There is a discussion started by Yakov on this list named "Ignite 1.6 
release timelines".

https://mail-archives.apache.org/mod_mbox/ignite-dev/201602.mbox/%3CCAGcMBHiS-9SaqURK8pKQ98VKh-Ynoq_y723%2BotLDuNJJAjKgow%40mail.gmail.com%3E

Igor, could you ask to consider this ticket for the next release as well 
answering in that thread?


--
Denis

On 2/18/2016 10:37 AM, Dmitriy Setrakyan wrote:

Would be nice to get it into the next release.

On Wed, Feb 17, 2016 at 10:40 PM, irudyak  wrote:


Actually the idea of PersistenceCallback interface looks good. I'll try to
think how it's better to implement CassandraData class.



--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7436.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: NoopSwapSpaceSpi and dynamically started caches

[Konstantin Margorin]

Hi all.

Sorry for asking again, but after some experiments I want to discuss
several options for grid swap policy. Some of them have odd side effects.
It's better to explicitly write them down to select the best solution.

1. Strict policy.
- @IgniteSpiConsistencyChecked(optional = false) used in FileSwapSpaceSpi
and NoopSwapSpaceSpi. Nodes with different swap providers could not coexist
in the grid.
- Cache with swap space could be start, only if all nodes in the grid has
FileSwapSpaceSpi provider enabled.
In this case if part of nodes in the grid use FileSwapSpaceSpi and other
part use NoopSwapSpaceSpi, than only random part of them will start. If the
first started node has FileSwapSpaceSpi, then all nodes with
 NoopSwapSpaceSpi will fail to start, and vice versa.
Interesting thing is that client nodes ( with Ignition.setClientMode(true))
should also has the same swap space provider as others nodes in the grid.
I.e. If nodes in the grid use FileSwapSpaceSpi, client will fail to start
if it use  NoopSwapSpaceSpi. That is strange, because client node does not
store any data, so swap policy is irrelevant to them.
Another interesting thing with client nodes is that client node with
NoopSwapSpaceSpi will never be able to start cache with swap enabled:
- if all nodes in the grid use FileSwapSpaceSpi, than client node simply
will fail to start
- if all nodes in the grid use NoopSwapSpaceSpi, than cache with swap will
not start on such nodes
2. Soft policy
- @IgniteSpiConsistencyChecked(optional = true) used in FileSwapSpaceSpi
and NoopSwapSpaceSpi. Nodes with different swap providers could coexist,
warning is printed in case of different providers.
- Cache with swap space could be start, only if all nodes in the grid has
FileSwapSpaceSpi provider enabled.
In this case success of dynamic cache with swap creation depends on order
in which the nodes start. Suppose we have node with swap (nSwap), node
without swap (nNoSwap) and a client, who just after start creates dynamic
cache with swap (cSwap).
If nSwap and nNoSwap started before cSwap, than cSwap will fail to create
cache, because not all nodes in the grid support swap space.
If nSwap started first, than started cSwap. cSwap will create cache
succesfuly. After that nNoSwap will start. And we have configuration now,
when nodes with different swap policies are coexist in grid, but cache with
swap successfully started.
3. Another option, initially suggested by Artem, is always use
FileSwapSpaceSpi if user doesn't provide SwapSpaceSpi explicitly. Probably
will get higher resources usage in this case.
4. Leave it as now, but with logging:
- @IgniteSpiConsistencyChecked(optional = true)
- log when cache with swap enabled started and there some nodes without
swap in the grid
Which option should we choose?


On Tue, Feb 16, 2016 at 2:55 PM, Yakov Zhdanov  wrote:

> I think, yes
>
> --Yakov
>
> 2016-02-16 14:19 GMT+03:00 Konstantin Margorin :
>
> > Should we use optional=false in @IgniteSpiConsistencyChecked ?
> >
> > On Tue, Feb 16, 2016 at 1:15 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Sounds good to me.
> > >
> > > On Tue, Feb 16, 2016 at 2:13 AM, Yakov Zhdanov 
> > > wrote:
> > >
> > > > Let's require that all nodes should have same swap space SPI. I think
> > we
> > > > can put @GridSpiConsistencyChecked on file swap space SPI (any other
> > > > suggestions?).
> > > >
> > > > --Yakov
> > > >
> > > > 2016-02-15 23:31 GMT+03:00 Konstantin Margorin :
> > > >
> > > > > Probably I can handle this ticket, but I want to clarify one thing.
> > > > >
> > > > > Suppose dynamic cache with enabled swap should be partitioned
> between
> > > two
> > > > > nodes with backups=1. First node started with FileSwapSpaceSpi,
> > second
> > > > with
> > > > > NoopSwapSpaceSpi.
> > > > >
> > > > > How cache should start in this case?
> > > > >
> > > > >
> > > > > On Mon, Feb 15, 2016 at 3:45 PM, Artem Shutak <
> ashu...@gridgain.com>
> > > > > wrote:
> > > > >
> > > > > > I've created a newbie issue for that:
> > > > > > https://issues.apache.org/jira/browse/IGNITE-2650.
> > > > > >
> > > > > > -- Artem --
> > > > > >
> > > > > > On Wed, Feb 10, 2016 at 8:53 PM, Dmitriy Setrakyan <
> > > > > dsetrak...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Artem,
> > > > > > >
> > > > > > > I like the option with proper exception in case if a dynamic
> > cache
> > > is
> > > > > > > started with swap enabled while there was no swap configured in
> > > > Ignite.
> > > > > > >
> > > > > > > Starting FileSwapSpaceSpi all the time is not a good option as
> > user
> > > > > will
> > > > > > > face the same problem when trying to change to a different SPI.
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Wed, Feb 10, 2016 at 4:39 AM, Artem Shutak <
> > > ashu...@gridgain.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > > I've noticed an issue with NoopSwapSpaceSpi and dynamically
> > > started
> > > > >

Re: Ignite 1.6 release timelines

[Alexey Goncharuk]

Yakov,

Nothing major from my side is planned for 1.6. There is a ticket
IGNITE-2610 that I am currently working on (it is almost finished), but I
believe it does not make any restrictions for the schedule.

Re: Ignite 1.6 release timelines

[Pavel Tupitsyn]

There are some important .NET features on review, like LINQ and NuGet:
https://issues.apache.org/jira/browse/IGNITE-1630
https://issues.apache.org/jira/browse/IGNITE-1626

Vova can clarify which of them are going to be included in 1.6.

Thanks,


On Thu, Feb 18, 2016 at 12:42 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Yakov,
>
> Nothing major from my side is planned for 1.6. There is a ticket
> IGNITE-2610 that I am currently working on (it is almost finished), but I
> believe it does not make any restrictions for the schedule.
>



-- 
-- 
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

[Alexey Goncharuk]

Folks,

The current implementation of IgniteCache.lock(key).lock() has the same
semantics as the transactional locks - cache topology cannot be changed
while there exists an ongoing transaction or an explicit lock is held. The
restriction for transactions is quite fundamental, the lock() issue can be
fixed if we re-implement locking the same way IgniteSemaphore currently
works.

As for the "Failed to find semaphore with the given name" message, my first
guess is that DataStructures were configured with 1 backups which led to
the data loss when two nodes were stopped. Mario, can you please re-test
your semaphore scenario with 2 backups configured for data structures?
>From my side, I can also take a look at the semaphore issue when I'm done
with IGNITE-2610.

Re: Ignite 1.6 release timelines

[Vladimir Ozerov]

I would definitely want to include NuGet and ODBC into upcoming release.
Both issues are in review for now. I expect they will be in master in a
week or so.

LINQ is "nice to have" for me for this release. It changes .NET packaging
and moreover must be tested very thoroughly. So it would be cool to include
it as well, but I do not think it is a showstopper for 1.6.

On Thu, Feb 18, 2016 at 12:47 PM, Pavel Tupitsyn 
wrote:

> There are some important .NET features on review, like LINQ and NuGet:
> https://issues.apache.org/jira/browse/IGNITE-1630
> https://issues.apache.org/jira/browse/IGNITE-1626
>
> Vova can clarify which of them are going to be included in 1.6.
>
> Thanks,
>
>
> On Thu, Feb 18, 2016 at 12:42 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
> > Yakov,
> >
> > Nothing major from my side is planned for 1.6. There is a ticket
> > IGNITE-2610 that I am currently working on (it is almost finished), but I
> > believe it does not make any restrictions for the schedule.
> >
>
>
>
> --
> --
> Pavel Tupitsyn
> GridGain Systems, Inc.
> www.gridgain.com
>

Re: NoopSwapSpaceSpi and dynamically started caches

[Yakov Zhdanov]

Konstantin,

Here are my comments.

1. I would force same swap configuration on all servers. Therefore, I would
add "checkClient" attribute to annotation which is "true" by default
2. I think all users should properly configure swap along the cluster if
they want to handle possible memory overflow.

--Yakov

2016-02-18 12:35 GMT+03:00 Konstantin Margorin :

> Hi all.
>
> Sorry for asking again, but after some experiments I want to discuss
> several options for grid swap policy. Some of them have odd side effects.
> It's better to explicitly write them down to select the best solution.
>
> 1. Strict policy.
> - @IgniteSpiConsistencyChecked(optional = false) used in FileSwapSpaceSpi
> and NoopSwapSpaceSpi. Nodes with different swap providers could not coexist
> in the grid.
> - Cache with swap space could be start, only if all nodes in the grid has
> FileSwapSpaceSpi provider enabled.
> In this case if part of nodes in the grid use FileSwapSpaceSpi and other
> part use NoopSwapSpaceSpi, than only random part of them will start. If the
> first started node has FileSwapSpaceSpi, then all nodes with
>  NoopSwapSpaceSpi will fail to start, and vice versa.
> Interesting thing is that client nodes ( with Ignition.setClientMode(true))
> should also has the same swap space provider as others nodes in the grid.
> I.e. If nodes in the grid use FileSwapSpaceSpi, client will fail to start
> if it use  NoopSwapSpaceSpi. That is strange, because client node does not
> store any data, so swap policy is irrelevant to them.
> Another interesting thing with client nodes is that client node with
> NoopSwapSpaceSpi will never be able to start cache with swap enabled:
> - if all nodes in the grid use FileSwapSpaceSpi, than client node simply
> will fail to start
> - if all nodes in the grid use NoopSwapSpaceSpi, than cache with swap will
> not start on such nodes
> 2. Soft policy
> - @IgniteSpiConsistencyChecked(optional = true) used in FileSwapSpaceSpi
> and NoopSwapSpaceSpi. Nodes with different swap providers could coexist,
> warning is printed in case of different providers.
> - Cache with swap space could be start, only if all nodes in the grid has
> FileSwapSpaceSpi provider enabled.
> In this case success of dynamic cache with swap creation depends on order
> in which the nodes start. Suppose we have node with swap (nSwap), node
> without swap (nNoSwap) and a client, who just after start creates dynamic
> cache with swap (cSwap).
> If nSwap and nNoSwap started before cSwap, than cSwap will fail to create
> cache, because not all nodes in the grid support swap space.
> If nSwap started first, than started cSwap. cSwap will create cache
> succesfuly. After that nNoSwap will start. And we have configuration now,
> when nodes with different swap policies are coexist in grid, but cache with
> swap successfully started.
> 3. Another option, initially suggested by Artem, is always use
> FileSwapSpaceSpi if user doesn't provide SwapSpaceSpi explicitly. Probably
> will get higher resources usage in this case.
> 4. Leave it as now, but with logging:
> - @IgniteSpiConsistencyChecked(optional = true)
> - log when cache with swap enabled started and there some nodes without
> swap in the grid
> Which option should we choose?
>
>
> On Tue, Feb 16, 2016 at 2:55 PM, Yakov Zhdanov 
> wrote:
>
> > I think, yes
> >
> > --Yakov
> >
> > 2016-02-16 14:19 GMT+03:00 Konstantin Margorin :
> >
> > > Should we use optional=false in @IgniteSpiConsistencyChecked ?
> > >
> > > On Tue, Feb 16, 2016 at 1:15 PM, Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> > > wrote:
> > >
> > > > Sounds good to me.
> > > >
> > > > On Tue, Feb 16, 2016 at 2:13 AM, Yakov Zhdanov 
> > > > wrote:
> > > >
> > > > > Let's require that all nodes should have same swap space SPI. I
> think
> > > we
> > > > > can put @GridSpiConsistencyChecked on file swap space SPI (any
> other
> > > > > suggestions?).
> > > > >
> > > > > --Yakov
> > > > >
> > > > > 2016-02-15 23:31 GMT+03:00 Konstantin Margorin :
> > > > >
> > > > > > Probably I can handle this ticket, but I want to clarify one
> thing.
> > > > > >
> > > > > > Suppose dynamic cache with enabled swap should be partitioned
> > between
> > > > two
> > > > > > nodes with backups=1. First node started with FileSwapSpaceSpi,
> > > second
> > > > > with
> > > > > > NoopSwapSpaceSpi.
> > > > > >
> > > > > > How cache should start in this case?
> > > > > >
> > > > > >
> > > > > > On Mon, Feb 15, 2016 at 3:45 PM, Artem Shutak <
> > ashu...@gridgain.com>
> > > > > > wrote:
> > > > > >
> > > > > > > I've created a newbie issue for that:
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-2650.
> > > > > > >
> > > > > > > -- Artem --
> > > > > > >
> > > > > > > On Wed, Feb 10, 2016 at 8:53 PM, Dmitriy Setrakyan <
> > > > > > dsetrak...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Artem,
> > > > > > > >
> > > > > > > > I like the option with proper exception in case if a dynamic
> > > cache
> > > > is
> > > > > >

Re: Please review

[Semyon Boikov]

Hi Denis,

Yakov and me looked at changes at ignite-2666 and we do not understand how
ring message worker can be interrupted except case when node is stopped?
Should we care about this case?

On Wed, Feb 17, 2016 at 2:18 PM, Denis Magda  wrote:

> Igniters,
>
> Please review the critical minor fixes for the following tickets
>
> IGNITE-2647:Cache is undeployed even when BinaryMarshaller is used <
> https://issues.apache.org/jira/browse/IGNITE-2647>
>
> IGNITE-2666: Node is not stopped when RingMessageWorker is interrupted <
> https://issues.apache.org/jira/browse/IGNITE-2666>
>
> In my understanding the review should be done either by Alex G. or Yakov
> or Sam.
>
> --
> Denis
>

Re: NoopSwapSpaceSpi and dynamically started caches

[Konstantin Margorin]

Yakov, thank you. Sounds good. I'll do this way.

On Thu, Feb 18, 2016 at 1:43 PM, Yakov Zhdanov  wrote:

> Konstantin,
>
> Here are my comments.
>
> 1. I would force same swap configuration on all servers. Therefore, I would
> add "checkClient" attribute to annotation which is "true" by default
> 2. I think all users should properly configure swap along the cluster if
> they want to handle possible memory overflow.
>
> --Yakov
>
> 2016-02-18 12:35 GMT+03:00 Konstantin Margorin :
>
> > Hi all.
> >
> > Sorry for asking again, but after some experiments I want to discuss
> > several options for grid swap policy. Some of them have odd side effects.
> > It's better to explicitly write them down to select the best solution.
> >
> > 1. Strict policy.
> > - @IgniteSpiConsistencyChecked(optional = false) used in FileSwapSpaceSpi
> > and NoopSwapSpaceSpi. Nodes with different swap providers could not
> coexist
> > in the grid.
> > - Cache with swap space could be start, only if all nodes in the grid has
> > FileSwapSpaceSpi provider enabled.
> > In this case if part of nodes in the grid use FileSwapSpaceSpi and other
> > part use NoopSwapSpaceSpi, than only random part of them will start. If
> the
> > first started node has FileSwapSpaceSpi, then all nodes with
> >  NoopSwapSpaceSpi will fail to start, and vice versa.
> > Interesting thing is that client nodes ( with
> Ignition.setClientMode(true))
> > should also has the same swap space provider as others nodes in the grid.
> > I.e. If nodes in the grid use FileSwapSpaceSpi, client will fail to start
> > if it use  NoopSwapSpaceSpi. That is strange, because client node does
> not
> > store any data, so swap policy is irrelevant to them.
> > Another interesting thing with client nodes is that client node with
> > NoopSwapSpaceSpi will never be able to start cache with swap enabled:
> > - if all nodes in the grid use FileSwapSpaceSpi, than client node simply
> > will fail to start
> > - if all nodes in the grid use NoopSwapSpaceSpi, than cache with swap
> will
> > not start on such nodes
> > 2. Soft policy
> > - @IgniteSpiConsistencyChecked(optional = true) used in FileSwapSpaceSpi
> > and NoopSwapSpaceSpi. Nodes with different swap providers could coexist,
> > warning is printed in case of different providers.
> > - Cache with swap space could be start, only if all nodes in the grid has
> > FileSwapSpaceSpi provider enabled.
> > In this case success of dynamic cache with swap creation depends on order
> > in which the nodes start. Suppose we have node with swap (nSwap), node
> > without swap (nNoSwap) and a client, who just after start creates dynamic
> > cache with swap (cSwap).
> > If nSwap and nNoSwap started before cSwap, than cSwap will fail to create
> > cache, because not all nodes in the grid support swap space.
> > If nSwap started first, than started cSwap. cSwap will create cache
> > succesfuly. After that nNoSwap will start. And we have configuration now,
> > when nodes with different swap policies are coexist in grid, but cache
> with
> > swap successfully started.
> > 3. Another option, initially suggested by Artem, is always use
> > FileSwapSpaceSpi if user doesn't provide SwapSpaceSpi explicitly.
> Probably
> > will get higher resources usage in this case.
> > 4. Leave it as now, but with logging:
> > - @IgniteSpiConsistencyChecked(optional = true)
> > - log when cache with swap enabled started and there some nodes without
> > swap in the grid
> > Which option should we choose?
> >
> >
> > On Tue, Feb 16, 2016 at 2:55 PM, Yakov Zhdanov 
> > wrote:
> >
> > > I think, yes
> > >
> > > --Yakov
> > >
> > > 2016-02-16 14:19 GMT+03:00 Konstantin Margorin :
> > >
> > > > Should we use optional=false in @IgniteSpiConsistencyChecked ?
> > > >
> > > > On Tue, Feb 16, 2016 at 1:15 PM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org>
> > > > wrote:
> > > >
> > > > > Sounds good to me.
> > > > >
> > > > > On Tue, Feb 16, 2016 at 2:13 AM, Yakov Zhdanov <
> yzhda...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Let's require that all nodes should have same swap space SPI. I
> > think
> > > > we
> > > > > > can put @GridSpiConsistencyChecked on file swap space SPI (any
> > other
> > > > > > suggestions?).
> > > > > >
> > > > > > --Yakov
> > > > > >
> > > > > > 2016-02-15 23:31 GMT+03:00 Konstantin Margorin  >:
> > > > > >
> > > > > > > Probably I can handle this ticket, but I want to clarify one
> > thing.
> > > > > > >
> > > > > > > Suppose dynamic cache with enabled swap should be partitioned
> > > between
> > > > > two
> > > > > > > nodes with backups=1. First node started with FileSwapSpaceSpi,
> > > > second
> > > > > > with
> > > > > > > NoopSwapSpaceSpi.
> > > > > > >
> > > > > > > How cache should start in this case?
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Feb 15, 2016 at 3:45 PM, Artem Shutak <
> > > ashu...@gridgain.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > I've created a newbie issue for that:
> > > > > > > > https://issues.ap

Re: About issue 1661

[李玉珏]

Hi:

Thanks!

在 16/2/18 06:29, Dmitriy Setrakyan 写道:

I linked IGNITE-2610 and IGNITE-1661 in Jira. Let’s process them together.

On Wed, Feb 17, 2016 at 12:58 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:


Yes, from the description it looks related to IGNITE-2610. I will check the
test attached to the IGNITE-1661 once I finish the fix for IGNITE-2610.

Re: Ignite .NET & C++ links on the main website

[Pavel Tupitsyn]

Dmitry, nothing else in mind, besides the issue with 3 different pieces of
documentation
(main website, API docs, readme.io), but it is the same with Java.

Thanks,

On Thu, Feb 18, 2016 at 4:42 AM, Dmitriy Setrakyan 
wrote:

> Pavel, I think that the contributor(s) of the functionality have to add the
> documentation. Otherwise, it will be very hard to do for the people not
> deeply involved. Did you have something else in mind?
>
> D.
>
> On Wed, Feb 17, 2016 at 2:02 AM, Pavel Tupitsyn 
> wrote:
>
> > Igniters,
> >
> > We have released .NET & C++ support in 1.5, but there is not enough
> > information about these on the main website:
> >
> > * No mentions in Features
> > * Documentation submenu is inconsistent across different pages (Download
> > page does not have .NET links in Documentation submenu for some reason)
> > * "Ignite for .Net" should be "Ignite.NET"
> > * API docs and readme.io docs are in different places, which is
> confusing
> >
> > Any thoughts on how to improve the situation?
> >
> > Thanks,
> >
> > --
> > --
> > Pavel Tupitsyn
> > GridGain Systems, Inc.
> > www.gridgain.com
> >
>



-- 
-- 
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com

Binary mode for Data Structures

[Pavel Tupitsyn]

Igniters,

Currently we don't have binary mode (withKeepBinary) in Data Structures
(Queue, AtomicReference).
Are there any plans for implementing this, or may be a workaround?

Lack of binary mode prevents us from implementing IgniteQueue in .NET (.NET
types in most cases can't be deserialized in Java).

AtomicReference is already implemented, and it works because values are
wrapped in GridCacheAtomicReferenceValue. So there is inconsistent behavior
between data structures.

Thoughts?

-- 
-- 
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com

[GitHub] ignite pull request: IGNITE-426 Implemented sending partition coun...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/52


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-2600 .NET: Do not serialize object if ...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/496

IGNITE-2600 .NET: Do not serialize object if AtomicReference CAS succeeded.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-2600

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/496.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #496


commit 96123fd240c8d904e26748798743c3a49cfb079f
Author: Pavel Tupitsyn 
Date:   2016-02-18T12:44:57Z

IGNITE-2600 .NET: Do not serialize object if AtomicReference CAS succeeded.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-2684) DataStreamer doesn't stream BinaryObjects created with BinaryBuilder

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2684:
---

 Summary: DataStreamer doesn't stream BinaryObjects created with 
BinaryBuilder
 Key: IGNITE-2684
 URL: https://issues.apache.org/jira/browse/IGNITE-2684
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5.0.final
Reporter: Denis Magda
Assignee: Denis Magda
Priority: Blocker
 Fix For: 1.6


If to create a {{BinaryObject}} using a type name of non existed class and 
start streaming it then nothing will be streamed because the streamer will try 
to deserialize binary objects and fill fail.

In general it's not to have classes for {{BinaryObjects}} at all and work with 
them with {{BinaryBuilder}} always. Thus this bug has to be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: IGNITE-2679 .NET: Implement Ignition.TryGetIg...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/497

IGNITE-2679 .NET: Implement Ignition.TryGetIgnite, returning null instead 
of exception



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-2679

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/497.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #497


commit ff7b73b55fc429b3d26e347f5366bce2bf5da3c7
Author: Pavel Tupitsyn 
Date:   2016-02-18T13:36:04Z

IGNITE-2679 .NET: Implement Ignition.TryGetIgnite, returning null instead 
of exception




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: Ignite 2610 - Fixed excessive memory usage in...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/488


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: About issue 1661

[Alexey Goncharuk]

Hi,

I have merged the changes fixing IGNITE-2610 and verified the test in
IGNITE-1661. Please verify and close the ticket if all is ok.

Re: Please review

[Denis Magda]

Hi Sam,

I saw some users reporting the following error

[tcp-disco-msg-worker-#2%null%] o.a.i.s.d.tcp.TcpDiscoverySpi -  
TcpDiscoverSpi'smessage worker thread failed abnormally. Stopping the node in 
order to prevent cluster wide instability.
java.lang.InterruptedException: null
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2088)
at 
java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:522)
at 
java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:684)


This exception is shown only when a node is not being stopped explicitly 
by the user meaning that someone else interrupted this thread.
Probably it's a reasonable interruption. That's why in addition I 
decided that we need to store a stack trace of the thread that 
interrupted  the ring message worker.


--
Denis

On 2/18/2016 1:44 PM, Semyon Boikov wrote:

Hi Denis,

Yakov and me looked at changes at ignite-2666 and we do not understand 
how ring message worker can be interrupted except case when node is 
stopped? Should we care about this case?


On Wed, Feb 17, 2016 at 2:18 PM, Denis Magda > wrote:


Igniters,

Please review the critical minor fixes for the following tickets

IGNITE-2647:Cache is undeployed even when BinaryMarshaller is used


IGNITE-2666: Node is not stopped when RingMessageWorker is
interrupted 

In my understanding the review should be done either by Alex G. or
Yakov or Sam.

--
Denis

Transactional queues

[Valentin Kulichenko]

Folks,

There were several questions about transactional queues on user forum and
it looks like this is not supported right now.

My question is: why do we have atomicity mode in CollectionConfiguration
then? Does setting it to TRANSACTIONAL change anything?

-Val

Re: About issue 1661

[Dmitriy Setrakyan]

Alexey, can this be verified in master?

On Thu, Feb 18, 2016 at 7:47 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Hi,
>
> I have merged the changes fixing IGNITE-2610 and verified the test in
> IGNITE-1661. Please verify and close the ticket if all is ok.
>

Re: About issue 1661

[Alexey Goncharuk]

Yes, the fix has been merged to master.
On Feb 18, 2016 22:06, "Dmitriy Setrakyan"  wrote:

> Alexey, can this be verified in master?
>
> On Thu, Feb 18, 2016 at 7:47 AM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
> > Hi,
> >
> > I have merged the changes fixing IGNITE-2610 and verified the test in
> > IGNITE-1661. Please verify and close the ticket if all is ok.
> >
>

Re: Transactional queues

[Dmitriy Setrakyan]

If it’s not supported for data structures right now, we should check for it
and throw an exception, no? Also, do we have this documented?

D.

On Thu, Feb 18, 2016 at 10:58 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Folks,
>
> There were several questions about transactional queues on user forum and
> it looks like this is not supported right now.
>
> My question is: why do we have atomicity mode in CollectionConfiguration
> then? Does setting it to TRANSACTIONAL change anything?
>
> -Val
>

[GitHub] ignite pull request: IGNITE-2563: More descriptive exception on un...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/476


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-2685) Turn off REST on demo node

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2685:
--

 Summary: Turn off REST on demo node
 Key: IGNITE-2685
 URL: https://issues.apache.org/jira/browse/IGNITE-2685
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Andrey Novikov
Priority: Minor


This is need to make unavailable to establish external connect from Visor to 
address 127.0.0.1:11211



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Java proxy for .NET service

[Valentin Kulichenko]

Igniters,

One of our users is asking me if this is possible to have a proxy on Java
client for a service implemented in .NET (and vica versa). He tried to do
this, but without success. Is it not supported or he is doing something
wrong?

For me it sounds like a useful feature and I don't see any fundamental
reasons not to have it.

Thoughts?

-Val