Re: Apache Ignite 2.1 scope

[Konstantin Boudnik]

Fair enough, I will try to collect more and share with the team.

And +1 on the proposed release schedule: considering the complexity of the
changes we better have some time to play with the bits. In fact, I'd suggest
we give it 7 days for the [VOTE] so people have time to play with the bits.
Thoughts?

Cos

On Thu, Jul 06, 2017 at 11:06AM, Vladimir Ozerov wrote:
> Cos,
> 
> I am not aware of performance degradation in regards to Cassandra. AFAIK
> there were extensive benchmarking prior to 2.0 release. And in the end 2.0
> release had performance not worse than 1.9. If you have more information on
> the matter, let's discuss it in the separate thread.
> 
> On Thu, Jul 6, 2017 at 11:04 AM, Vladimir Ozerov 
> wrote:
> 
> > Vyacheslav, Denis,
> >
> > 7 July is too abrupt date. Scope of 2.1 is still too broad, and what is
> > more important - persistent store has been merged only several days ago. We
> > need some room for stabilization. I propose the following timeline:
> > 16 July - code freeze
> > 17-21 July - QA
> > 21-24 July - vote and release
> >
> > On Thu, Jul 6, 2017 at 4:30 AM, Konstantin Boudnik  wrote:
> >
> >> Thanks everyone for giving us enough time to take a look into the code
> >> and architecture of this new feature. The webinar was certainly quite
> >> helpful (thanks Denis!).
> >>
> >> It seems to be a good time to add the feature into the dot-release, so
> >> more users can have a taste of it "officially". I have a somewhat
> >> unrelated question though: it seems that 2.0 has significant
> >> performance degradation compared to 1.8 when it get to the working
> >> with external distributed storage (like Cassandra). Could it be caused
> >> by all the changes that were made between 1.8 and 2.0 in the
> >> preparation for the coming persistent store functionality? Are we
> >> publishing/collecting say yardstick reports for our own releases?
> >>
> >> Thanks!
> >>   Cos
> >> --
> >>   Take care,
> >> Konstantin (Cos) Boudnik
> >> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> >>
> >> Disclaimer: Opinions expressed in this email are those of the author,
> >> and do not necessarily represent the views of any company the author
> >> might be affiliated with at the moment of writing.
> >>
> >>
> >> On Tue, Jul 4, 2017 at 3:20 AM, Vladimir Ozerov 
> >> wrote:
> >> > Igniters,
> >> >
> >> > Persistent store has been merged to master branch! "master-bak" branch
> >> was
> >> > created to keep the state before merge for safety. As release date for
> >> 2.1
> >> > is mid July, I created "ignite-2.1" branch where we will stabilize the
> >> > release as usual. Please push features and fixes planned for 2.1
> >> release to
> >> > this branch. The rest commits should go to master.
> >> >
> >> > Vladimir.
> >> >
> >> > On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov 
> >> > wrote:
> >> >
> >> >> Hi Denis,
> >> >>
> >> >> Awesome news! I'll take care of necessary release procedures if nobody
> >> >> minds.
> >> >>
> >> >> Vladimir.
> >> >>
> >> >> On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda 
> >> wrote:
> >> >>
> >> >>> Igniters,
> >> >>>
> >> >>> It’s time to refresh this abandoned thread and finally rollout out all
> >> >>> the changes appeared in 2.1.
> >> >>>
> >> >>> In addition, recently donated Persistent Store got the green light
> >> [1] to
> >> >>> become a part of the master branch (no one asked for extra time to
> >> dive
> >> >>> into its details) and, personally, it’s absolutely fine to make it
> >> >>> available in the nearest release.
> >> >>>
> >> >>> My proposal is to do the release by mid of July (closer to July
> >> 15th). Is
> >> >>> there anyone who is ready to take over as a release manager creating
> >> the
> >> >>> page like this [2] and handling all release related activities?
> >> >>>
> >> >>>
> >> >>> [1] http://apache-ignite-developers.2346864.n4.nabble.com/
> >> >>> Ignite-Persistent-Store-Ready-for-merge-td19160.html
> >> >>> [2] https://cwiki.apache.org/confluence/display/IGNITE/Apache+
> >> Ignite+2.0
> >> >>>
> >> >>> —
> >> >>> Denis
> >> >>>
> >> >>> > On Jun 1, 2017, at 9:24 AM, Alexander Paschenko <
> >> >>> alexander.a.pasche...@gmail.com> wrote:
> >> >>> >
> >> >>> > IGNITE-5327 Create predefined cache templates for CREATE TABLE
> >> command
> >> >>> > - minor comments left, ETA is Friday.
> >> >>> >
> >> >>> > IGNITE-5380 Validate cache QueryEntities in discovery thread - in
> >> >>> > progress, the meat of code is written, but need to add lots of
> >> tests.
> >> >>> > ETA is Friday.
> >> >>> >
> >> >>> > IGNITE-5188 Support AFFINITY KEY keyword for CREATE TABLE command -
> >> in
> >> >>> > progress, made few first small steps, ETA is Friday.
> >> >>> >
> >> >>> > Rest is closed/patch available, ignite-4994 has been moved to 2.2.
> >> >>> >
> >> >>> > - Alex
> >> >>> >
> >> >>> > 2017-06-01 19:03 GMT+03:00 Sergey Chugunov <
> >> sergey.chugu...@gmail.com>:

Enabling memory and persistence metrics

[Denis Magda]

Sergey,

How do I enable MemoryMetrics and PersistenceMetrics metrics aggregation if a 
have only the default region set and don’t wanna use the JMX beans available?

Struggling to find any API method to do that. Hope we didn’t forget to support 
such an obvious thing.

—
Denis

Re: It seems WebSession's removeAttribute does not support HttpSessionBindingListener

[Valentin Kulichenko]

What is your Jira ID? I will add you as a contributor.

-Val

On Fri, Jul 7, 2017 at 2:44 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> This will not work. WebSessionV2 does not reinvent the wheel, it provides
> additional functionality. In particular, allows to use the same session in
> a clustered environment.
>
> Genuine session is local, so if you just rely on it, all session data will
> be lost when server that holds this session fails. Your listeners will not
> be invoked as well, BTW. That's exactly what we're trying to avoid by
> introducing this feature.
>
> However, I agree that there is an issue with expiration. It's currently
> handled based on ExpiryPolicy, i.e., if maxInactiveInterval is set, session
> will be removed from the cache. But looks like we do not invalidate the
> genuine session, which is wrong.
>
> I think we should add a CacheEntryListener that will listen to expirations
> and handle all required post actions - invalidation of genuine session and
> invoking the listeners.
>
> -Val
>
> On Fri, Jul 7, 2017 at 6:59 AM, yucigou  wrote:
>
>> Hi Val,
>>
>> The mechanism is similar to the implementation of invalidate() of the
>> WebSessionV2 class. The {@link #invalidate()} action is delegated to the
>> genuine session. Similarly, actions setAttribute(), removeAttribute(), and
>> setMaxInactiveInterval() should be delegated to the genuine session. This
>> way, the web container can do to the session whatever it promises to do,
>> such as calling the HttpSessionBindingListener's valueUnbound callback
>> function, etc.
>>
>> If you look at the HttpSession interface, this is the whole list of APIs
>> concerned:
>>
>> * setAttribute()
>> * removeAttribute()
>> * setMaxInactiveInterval()
>> * invalidate()
>> * putValue()
>>
>> And putValue() has been covered by setAttribute() in WebSessionV2
>>
>> There are two main reasons that WebSessionV2 should delegate to the
>> genuine
>> session:
>> 1. Avoid re-inventing the wheel. The web container has already implemented
>> the related APIs.
>> 2. WebSessionV2 is not visible to the web container. When the web
>> container
>> decides to expire the session, it will not reach the WebSessionV2
>> implementation. And this is exactly where I had the problem in the first
>> place.
>>
>> By the way, thanks for pointing out removing attributes, I've made another
>> pull request on GitHub:
>> https://github.com/apache/ignite/pull/2243
>>
>> Also I can't assign the ticket to myself because of lack of permission:
>> https://issues.apache.org/jira/browse/IGNITE-5607
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-developer
>> s.2346864.n4.nabble.com/It-seems-WebSession-s-removeAttri
>> bute-does-not-support-HttpSessionBindingListener-tp19184p19575.html
>> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>>
>
>

Re: It seems WebSession's removeAttribute does not support HttpSessionBindingListener

[Valentin Kulichenko]

This will not work. WebSessionV2 does not reinvent the wheel, it provides
additional functionality. In particular, allows to use the same session in
a clustered environment.

Genuine session is local, so if you just rely on it, all session data will
be lost when server that holds this session fails. Your listeners will not
be invoked as well, BTW. That's exactly what we're trying to avoid by
introducing this feature.

However, I agree that there is an issue with expiration. It's currently
handled based on ExpiryPolicy, i.e., if maxInactiveInterval is set, session
will be removed from the cache. But looks like we do not invalidate the
genuine session, which is wrong.

I think we should add a CacheEntryListener that will listen to expirations
and handle all required post actions - invalidation of genuine session and
invoking the listeners.

-Val

On Fri, Jul 7, 2017 at 6:59 AM, yucigou  wrote:

> Hi Val,
>
> The mechanism is similar to the implementation of invalidate() of the
> WebSessionV2 class. The {@link #invalidate()} action is delegated to the
> genuine session. Similarly, actions setAttribute(), removeAttribute(), and
> setMaxInactiveInterval() should be delegated to the genuine session. This
> way, the web container can do to the session whatever it promises to do,
> such as calling the HttpSessionBindingListener's valueUnbound callback
> function, etc.
>
> If you look at the HttpSession interface, this is the whole list of APIs
> concerned:
>
> * setAttribute()
> * removeAttribute()
> * setMaxInactiveInterval()
> * invalidate()
> * putValue()
>
> And putValue() has been covered by setAttribute() in WebSessionV2
>
> There are two main reasons that WebSessionV2 should delegate to the genuine
> session:
> 1. Avoid re-inventing the wheel. The web container has already implemented
> the related APIs.
> 2. WebSessionV2 is not visible to the web container. When the web container
> decides to expire the session, it will not reach the WebSessionV2
> implementation. And this is exactly where I had the problem in the first
> place.
>
> By the way, thanks for pointing out removing attributes, I've made another
> pull request on GitHub:
> https://github.com/apache/ignite/pull/2243
>
> Also I can't assign the ticket to myself because of lack of permission:
> https://issues.apache.org/jira/browse/IGNITE-5607
>
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/It-seems-WebSession-s-
> removeAttribute-does-not-support-HttpSessionBindingListener-
> tp19184p19575.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>

[jira] [Created] (IGNITE-5719) .NET: Exception in StreamReceiver is not propagated to caller

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5719:
--

 Summary: .NET: Exception in StreamReceiver is not propagated to 
caller
 Key: IGNITE-5719
 URL: https://issues.apache.org/jira/browse/IGNITE-5719
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
 Fix For: 2.2


When exception is thrown in user-defined StreamReceiver, .NET stack trace is 
lost, only Java traces are available.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2265: IGNITE-4831: Option to disable MBeans.

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-4831: Option to disable MBeans.



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

$ git pull https://github.com/gridgain/apache-ignite ignite-4831

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

https://github.com/apache/ignite/pull/2265.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 #2265


commit cfc3d0f1ea61eabc75bb4d13699958495edfdfd2
Author: Andrey V. Mashenkov 
Date:   2017-07-04T15:21:10Z

WIP.

commit a93c5fb8b6841c6f9cc5196b5cc6dd20390cb18b
Author: Andrey V. Mashenkov 
Date:   2017-07-04T15:21:10Z

WIP.

commit 18c5d5ead54cb5ca1db0cdd20cc64f85e58403b1
Author: Andrey V. Mashenkov 
Date:   2017-07-04T17:24:52Z

WIP.

commit 552c32e5387c94a403228931d5625ce1a53d871d
Author: Andrey V. Mashenkov 
Date:   2017-07-07T16:01:22Z

Tests added

commit 731dcdfef81fc1f24ad98cf9ee98475df920d820
Author: Andrey V. Mashenkov 
Date:   2017-07-07T16:03:22Z

Tests added




---
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 #2264: IGNITE-5711 Allowed to run queries on caches with...

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-5711 Allowed to run queries on caches without query entities.



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5711

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

https://github.com/apache/ignite/pull/2264.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 #2264


commit 817c102d46abea236199a7f161a6f18403014f99
Author: Alexander Paschenko 
Date:   2017-07-07T15:30:09Z

IGNITE-5711 Allowed to run queries on caches without query entities.




---
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 #2263: IGNITE-5467 Exception in communication SPI can st...

[ezhuravl]

GitHub user ezhuravl opened a pull request:

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

IGNITE-5467 Exception in communication SPI can stall the cluster



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5467

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

https://github.com/apache/ignite/pull/2263.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 #2263


commit 76060a8f6609948aa03910196710dc314a8abbb6
Author: Evgenii Zhuravlev 
Date:   2017-07-07T14:43:37Z

IGNITE-5467 Exception in communication SPI can stall the cluster




---
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: It seems WebSession's removeAttribute does not support HttpSessionBindingListener

[yucigou]

Hi Val,

The mechanism is similar to the implementation of invalidate() of the
WebSessionV2 class. The {@link #invalidate()} action is delegated to the
genuine session. Similarly, actions setAttribute(), removeAttribute(), and
setMaxInactiveInterval() should be delegated to the genuine session. This
way, the web container can do to the session whatever it promises to do,
such as calling the HttpSessionBindingListener's valueUnbound callback
function, etc.

If you look at the HttpSession interface, this is the whole list of APIs
concerned:

* setAttribute()
* removeAttribute()
* setMaxInactiveInterval()
* invalidate()
* putValue()

And putValue() has been covered by setAttribute() in WebSessionV2

There are two main reasons that WebSessionV2 should delegate to the genuine
session:
1. Avoid re-inventing the wheel. The web container has already implemented
the related APIs.
2. WebSessionV2 is not visible to the web container. When the web container
decides to expire the session, it will not reach the WebSessionV2
implementation. And this is exactly where I had the problem in the first
place.

By the way, thanks for pointing out removing attributes, I've made another
pull request on GitHub:
https://github.com/apache/ignite/pull/2243

Also I can't assign the ticket to myself because of lack of permission:
https://issues.apache.org/jira/browse/IGNITE-5607




--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/It-seems-WebSession-s-removeAttribute-does-not-support-HttpSessionBindingListener-tp19184p19575.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request #2218: IGNITE-5582: Implemented Compute::Broadcast for C...

[isapego]

Github user isapego closed the pull request at:

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


---
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 #2262: IGNITE-5473: Create ignite troubleshooting logger...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-5473: Create ignite troubleshooting logger.

Partial fix.

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

$ git pull https://github.com/gridgain/apache-ignite ignite-5473

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

https://github.com/apache/ignite/pull/2262.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 #2262


commit 6abe8ec92f016a18883332de2bc177fbab30a4c1
Author: Alexey Goncharuk 
Date:   2017-06-14T18:37:54Z

WIP.

commit 4ab6d52cfa2f0dda6170ad1dff80d4a42c2a0706
Author: Andrey V. Mashenkov 
Date:   2017-06-30T11:45:18Z

WIP.




---
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 #2261: ignite-5701

[ilantukh]

GitHub user ilantukh opened a pull request:

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

ignite-5701



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5701

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

https://github.com/apache/ignite/pull/2261.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 #2261


commit b218241cf585ca3ca48761ff1625edd89630be9b
Author: Ilya Lantukh 
Date:   2017-07-05T14:50:09Z

ignite-5701 : Extended tests to reproduce this issue.

commit f34ae8794f0e836f167441c03d293d5af4a22874
Author: Ilya Lantukh 
Date:   2017-07-06T15:00:45Z

ignite-5701 : Fixed partition update counter handling.

commit d17c992ff78d0fc4f27a0a99bd62542b5ef81e94
Author: Ilya Lantukh 
Date:   2017-07-06T16:49:33Z

ignite-5701 : Removed obsolete code for update counters, added test for 
consistency.

commit 473ad6ed47ea9371319013a7cd449815a0b515dc
Author: Ilya Lantukh 
Date:   2017-07-07T13:35:56Z

ignite-5701 : Minors.




---
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 #2260: IGNITE-5718: Forcible node drop makes cluster ins...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-5718: Forcible node drop makes cluster instable in some cases.



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5718

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

https://github.com/apache/ignite/pull/2260.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 #2260


commit 5574c14d166173b73f2892ca1228e3c2da194238
Author: Andrey V. Mashenkov 
Date:   2017-07-07T13:01:44Z

Forcible node drop makes cluster unstable in some cases. Disable forcible 
node drop by default.

commit 0729eb909db9ea4d253e32f79aba95597f6e1016
Author: Andrey V. Mashenkov 
Date:   2017-07-07T13:02:21Z

Fix tests.




---
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 #2259: Ignite 5562 Assertions in TCP discovery SPI when ...

[sk0x50]

GitHub user sk0x50 opened a pull request:

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

Ignite 5562 Assertions in TCP discovery SPI when NTP is moving time 
backwards

The `assert` statements were changed due to the fact 
`System.currentTimeMillis()` is not monotonic.

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

$ git pull https://github.com/sk0x50/ignite ignite-5562-2

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

https://github.com/apache/ignite/pull/2259.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 #2259


commit 7c89922e70257a0dd8ff718612d5f2710eea3d8b
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:33:55Z

WIP.

commit e7b297e27ae4b215ae228f619b58c239710c6055
Author: Slava Koptilin 
Date:   2017-07-07T12:35:33Z

ignite-5562: assert statements were changed to the 'if' blocks




---
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 #2258: IGNITE-5332 added toString() method where it was ...

[Desperus]

GitHub user Desperus opened a pull request:

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

IGNITE-5332 added toString() method where it was missing



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

$ git pull https://github.com/Desperus/ignite ignite-5332

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

https://github.com/apache/ignite/pull/2258.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 #2258


commit fd6e61b5eb9ba9084a093377b871e541220ac8b3
Author: Aleksandr_Meterko 
Date:   2017-07-07T11:29:25Z

ignite-5332 added toString() method where it was missing




---
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-5717) MemoryPolicy configuration and documentation improvements

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5717:
---

 Summary: MemoryPolicy configuration and documentation improvements
 Key: IGNITE-5717
 URL: https://issues.apache.org/jira/browse/IGNITE-5717
 Project: Ignite
  Issue Type: Improvement
Reporter: Sergey Chugunov


After introducing MemoryPolicy concept and related settings to Ignite there 
were several cases when users run into problems with default configuration.

It seems that approach with allocating 80% of available physical memory causes 
confusion among users sitting on 32bit systems including versions of JMV 
(example [1]) and also hurts stability of TeamCity.

We need to rethink these settings and make them easier to use.

Also it turned out that memory allocation process differs in cases of PDS on 
and off; it must be properly documented.

[1] 
http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2257: IGNITE-5712 Context switching between threads for...

[voipp]

GitHub user voipp opened a pull request:

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

IGNITE-5712 Context switching between threads for optimistic transact…

…ions

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

$ git pull https://github.com/voipp/ignite IGNITE-5712

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

https://github.com/apache/ignite/pull/2257.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 #2257


commit f8f9a2c16b81a9afa6cb5ccbf5f283a8af9103fc
Author: voipp 
Date:   2017-06-30T15:06:53Z

IGNITE-5712 Context switching between threads for optimistic transactions




---
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 #2200: IGNITE-5426 JDBC thin: support readOnly

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2239: ignite-5693 : Fixed flaky test.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2219: IGNITE-5187 Made test more reliable.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2167: IGNITE-5533 Proper DROP of dynamic tables.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2168: IGNITE-5424 Fix GridServiceProxy does not unwraps...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2182: IGNITE-5552: ServiceProcessor recalculates all se...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2183: IGNITE-5528 - IS_EVICT_DISABLED flag is not clear...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2206: IGNITE-5340 AssertionError in index name check

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2247: IGNITE-5441 .NET: Propagate CacheStore exception ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2244: IGNITE-5604 expand byteBuffer for wal iterator if...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2205: IGNITE-5401

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2235: two tests unmuted, one test removed as obsolete (...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2174: Ignite 5558: Add ability to read WAL outside of a...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2246: IGNITE-5702

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-5716) .NET: Negative field offset values can be observed on 2-byte offsets

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5716:
--

 Summary: .NET: Negative field offset values can be observed on 
2-byte offsets
 Key: IGNITE-5716
 URL: https://issues.apache.org/jira/browse/IGNITE-5716
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.9
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Priority: Blocker
 Fix For: 2.1


{{BinaryObjectSchemaSerializer.WriteSchema}} uses {{ushort.MaxValue}} as a 
boundary for 2-byte offsets. {{ReadSchema}} uses {{ReadShort}}, which returns 
negative offsets for anything above {{short.MaxValue}}.

* Ensure that all offsets are always non-negative (use uint in 
{{BinaryObjectSchemaField}} probably)
* Check how Java handles this
* Add tests for all edge cases



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2256: Ignite 2190

[nizhikov]

GitHub user nizhikov opened a pull request:

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

Ignite 2190

Skip EVT_CACHE_QUERY_OBJECT_READ if there is no listener to prevent 
ClassNotFoundException
Add test to check fix
Add suggestion for a case when someone catch ClassNotFoundException using 
BinaryMarshaller without keepBinary

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

$ git pull https://github.com/nizhikov/ignite ignite-2190

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

https://github.com/apache/ignite/pull/2256.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 #2256


commit 864f22e91a44712fa7d1ee3c9cc4ed2cc126121b
Author: Nikolay Izhikov 
Date:   2017-07-06T16:20:00Z

ignite-2190:
Skip EVT_CACHE_QUERY_OBJECT_READ if there is no listener to prevent 
ClassNotFoundException
Add test to check fix
Add suggestion for a case when someone catch ClassNotFoundException using 
BinaryMarshaller without keepBinary

commit 90df863e3cb76835611ed52ce3759ff3fa198948
Author: Nikolay Izhikov 
Date:   2017-07-06T16:23:57Z

ignite-2190: return private scope for a constants

commit b131206d219274d601e45863ebf1e62b76a26888
Author: Ижиков Николай Владимирович 

Date:   2017-07-07T06:12:37Z

ignite-2190 fix codestyle




---
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-5715) Thread safety for transaction operations

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5715:


 Summary: Thread safety for transaction operations
 Key: IGNITE-5715
 URL: https://issues.apache.org/jira/browse/IGNITE-5715
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov


Resume operation should succeed if transaction was suspended earlier. 
Other transaction operations must throw exception if it tries to operate 
thransaction, it doesn't own.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5714) Context switching for pessimistic transactions

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5714:


 Summary: Context switching for pessimistic transactions
 Key: IGNITE-5714
 URL: https://issues.apache.org/jira/browse/IGNITE-5714
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


Implement context switching for pessimistic transactions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5713) The ignite-spring module should not rely on the ignite-indexing module.

[Yujue Li (JIRA)]

Yujue Li created IGNITE-5713:


 Summary: The ignite-spring module should not rely on the 
ignite-indexing module.
 Key: IGNITE-5713
 URL: https://issues.apache.org/jira/browse/IGNITE-5713
 Project: Ignite
  Issue Type: Improvement
  Components: spring
Affects Versions: 2.0
Reporter: Yujue Li
 Fix For: 2.1


In version 2.0, the ignite-spring module has increased reliance on the 
ignite-indexing module, which is not appropriate.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5712) Context switching for optimistic transactions

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5712:


 Summary: Context switching for optimistic transactions
 Key: IGNITE-5712
 URL: https://issues.apache.org/jira/browse/IGNITE-5712
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov


Implement context switching between threads for optimistic transactions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5711) SQL: It should be possible to execute SQL queries over cache with no indexed types

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5711:
---

 Summary: SQL: It should be possible to execute SQL queries over 
cache with no indexed types
 Key: IGNITE-5711
 URL: https://issues.apache.org/jira/browse/IGNITE-5711
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)