[jira] [Created] (IGNITE-5095) NULL strings in REST-HTTP should be serialized as null

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5095:


 Summary: NULL strings in REST-HTTP should be serialized as null
 Key: IGNITE-5095
 URL: https://issues.apache.org/jira/browse/IGNITE-5095
 Project: Ignite
  Issue Type: Task
  Components: cleints
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1874: IGNITE-5083: Add default cache for Redis.

[shroman]

Github user shroman closed the pull request at:

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


---
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: MemoryMetrics interface inconsistencies

[Denis Magda]

Sergey,

> There is no such thing as a "whole page memory", just look at the code.
> PageMemoryNoStoreImpl in AI manages single memory region (although
> expandable); and each MemoryPolicy has one and only one
> PageMemoryNoStoreImpl instance associated with it.


Under the “whole page memory” I meant all the regions defined by all the memory 
policies set up. I still think that it’s reasonable to have the metrics for the 
“whole page memory” so that people can see total memory consumption, etc. 
However, let’s put this off till 2.1. This should be an easy thing to add in 
the future.

> One more thing I cannot avoid mentioning is that the whole situation around
> interface inconsistency raised from huge lacks in documentation about
> metrics in AI in general. I haven't found any javadocs or wikis describing
> overall architecture of metrics gathering in Ignite, how they are exposed
> to users or what are use cases. And I still don't have a full picture of
> this.

Yes, there is a gap in here. We will start improving the situation with this 
ticket:
https://issues.apache.org/jira/browse/IGNITE-4963 


—
Denis

> On Apr 26, 2017, at 7:07 AM, Sergey Chugunov  
> wrote:
> 
> Denis,
> 
> There is no such thing as a "whole page memory", just look at the code.
> PageMemoryNoStoreImpl in AI manages single memory region (although
> expandable); and each MemoryPolicy has one and only one
> PageMemoryNoStoreImpl instance associated with it.
> 
> Each MemoryMetricsImpl is aimed to collect metrics from one MemoryPolicy
> (allocations, evictions, etc.) on local node. I'll reflect this in
> documentation for sure and ask you and other people to review it.
> 
> One more thing I cannot avoid mentioning is that the whole situation around
> interface inconsistency raised from huge lacks in documentation about
> metrics in AI in general. I haven't found any javadocs or wikis describing
> overall architecture of metrics gathering in Ignite, how they are exposed
> to users or what are use cases. And I still don't have a full picture of
> this.
> So if there are any experts who know more than me, I think it is a must for
> them to share their knowledge with community somewhere in javadoc or other
> easily accessible place.
> 
> Thanks,
> Sergey.
> 
> On Tue, Apr 25, 2017 at 8:46 PM, Denis Magda  wrote:
> 
>> Totally agree with all Pavel’s and Vovan's suggestions and concerns,
>> especially, with the following:
>> 
>>> 2) MemoryMetrics has methods that modify state, like enableMetrics
>>> and rateTimeInterval
>>> (IgniteCache.metrics() returns a read-only serializable snapshot)
>>> 
>>> 3) getSize method returns size in megabytes
>>> (IgniteCache.metrics() provides sizes in bytes)
>> 
>> In general, it’s unclear how to use it and the javadoc doesn’t explain
>> whether these are the metrics for a pool/region/block defined by memory
>> policy or the whole page memory available to a node will be monitored.
>> Please mention all that in the javadoc and don’t refer to internal classes
>> like PageMemory and FreeList the documentation.
>> 
>> —
>> Denis
>> 
>>> On Apr 25, 2017, at 12:23 AM, Pavel Tupitsyn 
>> wrote:
>>> 
>>> Can you give an example of such API usage?
>>> A piece of code to enable metrics and retrieve a snapshot?
>>> 
>>> On Mon, Apr 24, 2017 at 8:06 PM, Alexey Goncharuk <
>>> alexey.goncha...@gmail.com> wrote:
>>> 
 Agree, I overlooked this during the review. However, the changes to fix
 this is pretty simple - we just move all mutator methods to MBean, like
 Vladimir suggested and make MBean return the live data, while the public
 API will return a serializable snapshot.
 
 Agreed?
 
 2017-04-24 19:33 GMT+03:00 Vladimir Ozerov :
 
> It seems that all mutator methods should be simply moved to MBean
 interface
> and change MBytes to bytes. In this case metrics interface will be
> consistent.
> 
> On Mon, Apr 24, 2017 at 7:29 PM, Vladimir Ozerov >> 
> wrote:
> 
>> Sergey,
>> 
>> We need to keep API consistent. If we usually return bytes, then these
>> metrics should return bytes as well. What is more important, when I
 look
> at
>> API I understand that this thing is not metrics at all. Metrics in
 Ignte
>> terms is a set of read-only numeric properties. But this interface
> contains
>> strange things like "name", "swapPilePath". What even more strange, I
 do
>> not see how to get these metrics from public API.
>> 
>> All in all, looks like this entity is not "metrics", but "MBean" in
 usual
>> Ignite terms.
>> 
>> Vladimir.
>> 
>> On Mon, Apr 24, 2017 at 7:20 PM, Pavel Tupitsyn >> 
>> wrote:
>> 
>>> Sergey, I disagree.
>>> 
>>> 1) As a user, I would expect 

Re: Null cache names

[Denis Magda]

Thanks, Roman! As I see the changes have been already incorporated in 2.0.

Please document them on 2.0 specific Redis documentation:
https://apacheignite.readme.io/docs/redis-20 


—
Denis

> On Apr 25, 2017, at 10:58 PM, Roman Shtykh  wrote:
> 
> Denis,
> 
> PR is created. https://issues.apache.org/jira/browse/IGNITE-5083 
>  for review.
> 
> We will have to find a good solution to "externalize" the default cache name 
> in future, as Vladimir suggested. As Igor pointed out, probably for memcached 
> too.
> I'll create another JIRA issue for that.
> 
> Roman
> 
> 
> 
> On Wednesday, April 26, 2017 1:16 PM, Denis Magda  wrote:
> 
> 
> > So it is approach 1 ("redis_cache") I proposed initially. Any concerns? If 
> > it is ok, I set Redis to that cache and update the documentation.
> 
> Let’s handle the way Roman suggests. Don’t see any reason why we keep 
> discussing this if the whole story is about a “one line” fix.
> 
> Roman, could you implement your suggestion and do a pull-request?
> 
> —
> Denis
> 
> > On Apr 25, 2017, at 6:53 PM, Roman Shtykh  > > wrote:
> > 
> > Vladimir,
> > I agree. But, if I get it right, according to your concern for using 
> > memcached and Redis simultaneously, we'll need a separate default cache for 
> > each. So it is approach 1 ("redis_cache") I proposed initially. Any 
> > concerns? If it is ok, I set Redis to that cache and update the 
> > documentation.
> > Btw, I agree ConnectorConfiguration is not the proper place, but having 
> > 'jettyPath' in it made me think it could be done ;) Probably we will need 
> > refactoring to make it generic and more separate configuration classes as 
> > more protocols get implemented.
> > Roman 
> > 
> >On Wednesday, April 26, 2017 4:49 AM, Sergi Vladykin 
> > > wrote:
> > 
> > 
> > Agree, lets move forward with the simplest possible solution for now.
> > 
> > Sergi
> > 
> > 2017-04-25 13:07 GMT+03:00 Vladimir Ozerov  > >:
> > 
> >> Folks,
> >> 
> >> I do not think it is legal to add such property to ConnectorConfiguration.
> >> Connector is a generic gateway to cluster resources. It should not bother
> >> about caches anyhow. What if there are multiple caches in the cluster? What
> >> is I want to access "cache A" from Memcached and "cache B" from Redis
> >> simultaneously? Etc.. This kind of property should be defined on client
> >> level, not on the server.
> >> 
> >> For now, provided that 2.0 is about to be freezed, I propose to stick to
> >> Dmitriy's approach and use "default" cache name instead of null. This
> >> should work fine for AI 2.0. We will be able to improve it in further
> >> releases.
> >> 
> >> Thoughts?
> >> 
> >> Vladimir.
> >> 
> >> On Tue, Apr 25, 2017 at 7:22 AM, Roman Shtykh  >> >
> >> wrote:
> >> 
> >>> Igor, +1 from me.We can add a field to ConnectorConfiguration (not sure
> >> if
> >>> it's a proper place, but it's shared by REST, memcached and Redis). A
> >> user
> >>> will have to create a cache, configure as needed and specify the name in
> >>> ConnectorConfiguration.
> >>> Roman
> >>> 
> >>> 
> >>> 
> >>>On Monday, April 24, 2017 10:34 PM, Seliverstov Igor <
> >>> gvvinbl...@gmail.com > wrote:
> >>> 
> >>> 
> >>>  Dear Igniters,
> >>> 
> >>> Seems we have almost the same issue with Memcached protocol.
> >>> 
> >>> There is an ability to define a cache name via operation extras message
> >>> part (
> >>> https://github.com/memcached/memcached/wiki/ 
> >>> 
> >> BinaryProtocolRevamped#packet-
> >>> structure)
> >>> but it looks a bit complicated from my point of view...
> >>> 
> >>> Different client implementations might provide such functionality or not
> >> (I
> >>> mean an additional info in an operation extras), so, potential user might
> >>> have some difficultes using Ignite as a Memcached server because of this
> >>> ignite-specific message part becomes mandatory.
> >>> 
> >>> An alternative (an the best way, I think) is introducing a configuration
> >>> property to define which cache to use in case it hasn't be defined in a
> >>> message.
> >>> 
> >>> I'll appreciate any thoughts on that.
> >>> 
> >>> Regards,
> >>> Igor
> >>> 
> >>> 2017-04-24 12:43 GMT+03:00 Roman Shtykh  >>> >:
> >>> 
>  Vladimir,
>  Probably we may set the cache name via https://redis.io/commands/ 
>  
>  client-setname, save it and use until the user specifies another name.
>  #That will be the name for the default cache (mainly for STRING data).
> >>> For
>  

[jira] [Created] (IGNITE-5094) Eviction tracker does not evict data pages when near cache is enabled

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5094:


 Summary: Eviction tracker does not evict data pages when near 
cache is enabled
 Key: IGNITE-5094
 URL: https://issues.apache.org/jira/browse/IGNITE-5094
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.0
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Priority: Critical
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1878: changes with expandable memory policy and memory ...

[sergey-chugunov-1985]

Github user sergey-chugunov-1985 closed the pull request at:

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


---
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 #1878: changes with expandable memory policy and memory ...

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

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

changes with expandable memory policy and memory metrics improvements



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

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

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

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


commit 66a7eb3c6bd77d4af1a04f2224feac5c1a7e9fcb
Author: Sergi Vladykin 
Date:   2017-04-18T14:21:20Z

master - test adjusted

commit 5d8e31806ac8c013169c9892c0f88b79d6833358
Author: Anton Vinogradov 
Date:   2017-04-18T12:32:29Z

Special profiles to set versions and check compilation across all modules
(cherry picked from commit 3565e4e)

commit 0abf6601fc1ff1e6e659381666ae706e31b51de0
Author: Yury Babak 
Date:   2017-04-18T13:47:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation
(cherry picked from commit d78e071)

commit 364c38661a1864e0b823be737998ed66927d11ca
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:27Z

master - Mute test with a correct link

commit 0da51d4110ab13f42f0ee5a2fc3181fc50656cd4
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:55Z

master - Fix mvcc tests after CLOCK mode removal

commit 27fd74f1ebd0cb89a99be69c5c74829307e3
Author: Ignite Teamcity 
Date:   2017-04-18T16:43:28Z

2.1.0-SNAPSHOT

commit 9c954c93a9d93952354e784a75c45cecdf245a2d
Author: Andrey V. Mashenkov 
Date:   2017-04-19T03:30:30Z

Fixed service deployment tests.

commit 9ce62e64a7abfc59799f4edf8d057a12c7a0d11d
Author: Andrey V. Mashenkov 
Date:   2017-04-19T03:45:08Z

Fixed javadoc.

commit 83d913c804ab6ecd4fb650e3b09062dca92ccae1
Author: Sergey Chugunov 
Date:   2017-04-19T14:03:32Z

IGNITE-5024 default Memory Policy size was changed to 80% of available RAM

commit 67ba03bc2c2181f9d61caddd5981d24ef50cc10a
Author: Alexey Goncharuk 
Date:   2017-04-20T16:38:24Z

IGNITE-5024 - expandable memory space

commit 14c52e2fcac45bc51ca6e8588a7d250a0e285a1b
Author: Alexey Goncharuk 
Date:   2017-04-24T08:02:13Z

Merge branch ignite-5024 of https://github.com/gridgain/apache-ignite into 
ignite-5024

commit df7da50fb641bcde607bc3f3be591ea1704fb757
Author: Alexey Goncharuk 
Date:   2017-04-24T08:03:00Z

Merge branch 'ignite-2.0' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-5024

commit 777bd7763fe534ba88a9834c87f0c297832093c4
Author: Alexey Goncharuk 
Date:   2017-04-24T08:21:59Z

IGNITE-5024 - Fixing tests

commit 6746d82618343dcd1e57dadec337089476f451b0
Author: Alexey Goncharuk 
Date:   2017-04-24T17:14:01Z

IGNITE-5024 - Fixing tests

commit 21dce2708a50e2a87e876f2558c888f50d0d6df2
Author: Alexey Goncharuk 
Date:   2017-04-25T07:35:56Z

IGNITE-5024 - Fixing tests

commit afa1f96ccaa585b832e24bb07124b4eddfd524ca
Author: Alexey Goncharuk 
Date:   2017-04-25T07:44:41Z

IGNITE-5024 - Fixing tests

commit 5b35ebcda51f2e0041dd3ee249ddf8028c8f4b9b
Author: Alexey Goncharuk 
Date:   2017-04-25T07:52:12Z

IGNITE-5024 - Fixing tests

commit 9125b904a0fa253231374b0a9002de40e25f7ce3
Author: Alexey Goncharuk 
Date:   2017-04-25T09:21:42Z

IGNITE-5072 - Return memory metrics snapshot on public API

commit 00b7c51bc1f94d8a98709d61f48c19c7a4bc060f
Author: Sergey Chugunov 
Date:   2017-04-25T09:53:25Z

IGNITE-4536 one more obsolete cache metric was removed

commit 4ec1b65dda3e741abc09bfd342f958ce75b17a1a
Author: Sergey Chugunov 
Date:   2017-04-25T13:04:53Z

IGNITE-4536 MemoryMetricsImpl class was split, JMX part was extracted to a 
separate class

commit 26ec9ff589eaf36d7f149aec302281c28173718d
Author: Alexey Goncharuk 
Date:   2017-04-25T14:43:57Z

Merge into ignite-5072

commit 2fe80ef02e6ef0c15183142247f919a152dfbd29
Author: Alexey Goncharuk 
Date:   2017-04-25T14:44:26Z

Merge into ignite-5072

commit 30700df7a8796e2b9ad914f6dd2e8d113ecb3e20
Author: Pavel Tupitsyn 
Date:   2017-04-25T15:25:39Z

.NET: Update memory policy properties

commit ead52124b6fb2ecd279ab44070147bec5e513bcd
Author: Pavel Tupitsyn 

[GitHub] ignite pull request #1877: Ignite gg 12150 Provide safety way for run AWS/GC...

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

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

Ignite gg 12150 Provide safety way for run AWS/GCE ipfinder test



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

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

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

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


commit 8f9edebfe74e2de1368d42ba951fa074b116eb17
Author: Igor Seliverstov 
Date:   2017-04-26T14:51:43Z

IGNITE-3488: Prohibited null as cache name. This closes #1790.

commit 571c418a9792450b8d3a6a361c0684a34283a6c8
Author: Dmitriy Govorukhin 
Date:   2017-04-26T15:08:22Z

ignite-gg-12150 simple proxy server implementation




---
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-5093) Better heap usage during exchange on large topologies and cache numbers/partitions.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-5093:
-

 Summary: Better heap usage during exchange on large topologies and 
cache numbers/partitions.
 Key: IGNITE-5093
 URL: https://issues.apache.org/jira/browse/IGNITE-5093
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 1.6
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
 Fix For: 2.1


I observed huge heap occupation during exchange on large grid installation 
including 136 nodes/1k caches.

Example from machine with 64g heap:

{noformat}
 num #instances #bytes  class name
--
   1:   89728797743069822896  java.util.HashMap$Node
   2:   927316214866180592  [Ljava.util.HashMap$Node;
   3:   2012822924830775008java.lang.Integer
   4:   6247215 983811096  [Ljava.lang.Object;
   5:   3383402 767741664  [C
   6:   12188  669411952   [B
   7:   9923859 635126976   java.util.HashMap
...
{noformat}

Further investigation had showed the heap is polluted during exchange process, 
which involves creating many hashmaps occupying large amounts of memory.

Proposal: use other datastructures to help keep heap usage low.





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: MemoryMetrics interface inconsistencies

[Sergey Chugunov]

Denis,

There is no such thing as a "whole page memory", just look at the code.
PageMemoryNoStoreImpl in AI manages single memory region (although
expandable); and each MemoryPolicy has one and only one
PageMemoryNoStoreImpl instance associated with it.

Each MemoryMetricsImpl is aimed to collect metrics from one MemoryPolicy
(allocations, evictions, etc.) on local node. I'll reflect this in
documentation for sure and ask you and other people to review it.

One more thing I cannot avoid mentioning is that the whole situation around
interface inconsistency raised from huge lacks in documentation about
metrics in AI in general. I haven't found any javadocs or wikis describing
overall architecture of metrics gathering in Ignite, how they are exposed
to users or what are use cases. And I still don't have a full picture of
this.
So if there are any experts who know more than me, I think it is a must for
them to share their knowledge with community somewhere in javadoc or other
easily accessible place.

Thanks,
Sergey.

On Tue, Apr 25, 2017 at 8:46 PM, Denis Magda  wrote:

> Totally agree with all Pavel’s and Vovan's suggestions and concerns,
> especially, with the following:
>
> > 2) MemoryMetrics has methods that modify state, like enableMetrics
> > and rateTimeInterval
> > (IgniteCache.metrics() returns a read-only serializable snapshot)
> >
> > 3) getSize method returns size in megabytes
> > (IgniteCache.metrics() provides sizes in bytes)
>
> In general, it’s unclear how to use it and the javadoc doesn’t explain
> whether these are the metrics for a pool/region/block defined by memory
> policy or the whole page memory available to a node will be monitored.
> Please mention all that in the javadoc and don’t refer to internal classes
> like PageMemory and FreeList the documentation.
>
> —
> Denis
>
> > On Apr 25, 2017, at 12:23 AM, Pavel Tupitsyn 
> wrote:
> >
> > Can you give an example of such API usage?
> > A piece of code to enable metrics and retrieve a snapshot?
> >
> > On Mon, Apr 24, 2017 at 8:06 PM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> >> Agree, I overlooked this during the review. However, the changes to fix
> >> this is pretty simple - we just move all mutator methods to MBean, like
> >> Vladimir suggested and make MBean return the live data, while the public
> >> API will return a serializable snapshot.
> >>
> >> Agreed?
> >>
> >> 2017-04-24 19:33 GMT+03:00 Vladimir Ozerov :
> >>
> >>> It seems that all mutator methods should be simply moved to MBean
> >> interface
> >>> and change MBytes to bytes. In this case metrics interface will be
> >>> consistent.
> >>>
> >>> On Mon, Apr 24, 2017 at 7:29 PM, Vladimir Ozerov  >
> >>> wrote:
> >>>
>  Sergey,
> 
>  We need to keep API consistent. If we usually return bytes, then these
>  metrics should return bytes as well. What is more important, when I
> >> look
> >>> at
>  API I understand that this thing is not metrics at all. Metrics in
> >> Ignte
>  terms is a set of read-only numeric properties. But this interface
> >>> contains
>  strange things like "name", "swapPilePath". What even more strange, I
> >> do
>  not see how to get these metrics from public API.
> 
>  All in all, looks like this entity is not "metrics", but "MBean" in
> >> usual
>  Ignite terms.
> 
>  Vladimir.
> 
>  On Mon, Apr 24, 2017 at 7:20 PM, Pavel Tupitsyn  >
>  wrote:
> 
> > Sergey, I disagree.
> >
> > 1) As a user, I would expect MemoryMetrics instance to be
> > read-only and serializable, so I can send it somewhere, store,
> > put into a collection and draw a graph in UI, etc.
> >
> > Other metrics APIs allow this, MemoryMetrics does not.
> >
> > 2) Methods like enableMetrics and rateTimeInterval placed in
> >>> MemoryMetrics
> > break single responsibility principle and are confusing.
> > Why do I need to Get metrics to Enable them?
> >
> > These methods should be placed somewhere else.
> >
> > I would suggest some thing like this:
> > - introduce Memory class with getMetrics, enableMetrics,
> > setRateTimeInterval, etc
> > - add Ignite.getMemory method
> >
> >
> > On Mon, Apr 24, 2017 at 6:53 PM, Sergey Chugunov <
> > sergey.chugu...@gmail.com>
> > wrote:
> >
> >> I guess the main reason to have IgniteCache returning snapshot
> >> metrics
> > was
> >> to collect metrics about distributed cache across the cluster.
> >> At the same time MemoryMetrics were initially designed to be local
> >> on
> > each
> >> node, there were no requirements about collecting cluster-wide
> >> MemoryMetrics.
> >>
> >> Collecting MemoryMetrics is considered as an investigation action
> >> when
> >> something goes wrong, that's why it was decided to add
> >> 

[jira] [Created] (IGNITE-5092) TC should check Examples on each regression.

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-5092:


 Summary: TC should check Examples on each regression.
 Key: IGNITE-5092
 URL: https://issues.apache.org/jira/browse/IGNITE-5092
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov
Priority: Critical
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1876: IGNITE-4648

[SomeFire]

GitHub user SomeFire opened a pull request:

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

IGNITE-4648



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

$ git pull https://github.com/SomeFire/ignite ignite-4648

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

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


commit 400dca03c510730d867807a734195ff4a6bae77a
Author: Dmitrii Ryabov 
Date:   2017-04-26T13:28:18Z

tx.txState().awaitLastFut() inserted into prepareTx()




---
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-5091) Document RocketMQ streamer

[Roman Shtykh (JIRA)]

Roman Shtykh created IGNITE-5091:


 Summary: Document RocketMQ streamer
 Key: IGNITE-5091
 URL: https://issues.apache.org/jira/browse/IGNITE-5091
 Project: Ignite
  Issue Type: Sub-task
Reporter: Roman Shtykh
Assignee: Roman Shtykh
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1863: IGNITE-5036 Disallow @QuerySqlField and @QueryTex...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1803: Ignite-4949 Incorrect behavior CacheJdbcPojoStore...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1789: IGNITE-3524 IGFS: Do not allow nulls for FileSyst...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1832: index hints

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1718: IGNITE-4699 Introduce custom configurable executo...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1830: IGNITE-3549 IGFS: Switch "accessTime" and "modifi...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1824: ignite-5019 Deadlock in GridCacheVariableTopology...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1750: IGNITE-4925 Fix IgniteCacheEntryListenerEagerTtlD...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1854: IGNITE-3521 IGFS: Remove "max space" notion

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1858: IGNITE-4523

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1786: IGNITE-3523 IGFS: Remove "initialize default path...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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.
---

Contributions

[Dmitry Pavlov]

Hello, Ignite Community!

My name is Dmitriy. I would like to contribute to Apache Ignite and want to
start with this issue - IGNITE-5078.
JIRA ID: dpavlov. Any help on this will be appreciated.

Thanks!

Best Regards,
Dmitriy Pavlov

[jira] [Created] (IGNITE-5089) .NET: NuGet-based samples

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5089:
--

 Summary: .NET: NuGet-based samples
 Key: IGNITE-5089
 URL: https://issues.apache.org/jira/browse/IGNITE-5089
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


We have two ways to run samples:
* Download full (huge) binary package from ignite.apache.org, unzip and run 
from there. Cumbersome process.
* Run a limited set of samples in LINQPad. Very easy, but not everyone has 
LINQPad.

There is no quick and easy way to run samples in Visual Studio. We should fix 
that by providing sample NuGet packages. Works like this:
* User creates a new project
* Installs {{Apache.Ignite.Sample}} package (which depends on {{Apache.Ignite}} 
package, so it is installed too)
* Samples are added to the current project and can be run right away.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Apache Ignite 2.0 Release

[Alexey Goncharuk]

Roman,

Thanks for the contribution, I merged your changes to ignite-2.0 branch.

2017-04-26 7:12 GMT+03:00 Denis Magda :

> Alex G.,
>
> Would you complete the review of IGNITE-4539 and merge the changes?
>
> —
> Denis
>
> > On Apr 25, 2017, at 6:33 PM, Roman Shtykh 
> wrote:
> >
> > I would also like to include IGNITE-4539. Its implementation is finished.
> > Roman
> >
> >On Wednesday, April 26, 2017 1:59 AM, Vladimir Ozerov <
> voze...@gridgain.com> wrote:
> >
> >
> > Igniters,
> >
> > We are almost there. Outstanding issues which I hope we will be able to
> > resolve quickly:
> > 1) Hibernate 5 support [1]
> > 2) Two SQL tickets (2], [3]
> > 3) Two page memory tickets [4], [5]
> > 4) TcpDiscoverySpi.heartbeatsFrequency [6]
> > 5) Prohibit "null" as cache name [7]
> >
> > Most of them are in "Patch Available". Let's do our best to merge them in
> > the nearest day.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-1794
> > [2] https://issues.apache.org/jira/browse/IGNITE-3481
> > [3] https://issues.apache.org/jira/browse/IGNITE-3487
> > ]4] https://issues.apache.org/jira/browse/IGNITE-5024
> > [5] https://issues.apache.org/jira/browse/IGNITE-5072
> > [6] https://issues.apache.org/jira/browse/IGNITE-4799
> > [7] https://issues.apache.org/jira/browse/IGNITE-3488
> >
> >
> > On Sat, Apr 22, 2017 at 2:25 AM, Denis Magda  wrote:
> >
> >> Guys,
> >>
> >> How close are we for the voting? What exactly are we waiting for to
> >> initiate it (H2 release, TC tests, CREATE INDEX)?
> >>
> >> —
> >> Denis
> >>
> >>> On Apr 19, 2017, at 4:03 PM, Denis Magda  wrote:
> >>>
> >>> Roman,
> >>>
> >>> If we squeeze your contribution into 2.0 please add a documentation.
> You
> >> can handle the documentation separately as a subtask of this umbrella
> >> ticket:
> >>> https://issues.apache.org/jira/browse/IGNITE-4960
> >>>
> >>> —
> >>> Denis
> >>>
>  On Apr 19, 2017, at 7:03 AM, Roman Shtykh 
> >> wrote:
> 
>  Alexey,
>  Sorry, I forgot to update dependencies. Now it should be fine.
>  Roman
> 
> 
>    On Wednesday, April 19, 2017 9:56 PM, Alexey Goncharuk <
> >> alexey.goncha...@gmail.com> wrote:
> 
> 
>  Roman,
>  I see that you've changed the rocketmq version to 4.0.0-SNAPSHOT, but
> >> this does not work because it requires a local copy of rocketmq. If I
> >> revert it back to 4.0.0-incubating, then the test does not compile for
> me.
>  2017-04-19 11:55 GMT+03:00 Roman Shtykh :
> 
>  Hi Alexey,
>  Fixed now. Thanks for checking!
>  Roman
> 
> 
>  On Tuesday, April 18, 2017 10:17 PM, Alexey Goncharuk <
> >> alexey.goncha...@gmail.com> wrote:
> 
> 
>  Hi Roman,
> 
>  I tried to run tests for RocketMQ streamer, but they failed for me
> (I've
>  added a comment in the ticket). Can you please take a look?
> 
>  2017-04-18 15:13 GMT+03:00 Vladimir Ozerov :
> 
> > Folks,
> >
> > I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's
> >> continue
> > 2.0 finalization in this branch.
> >
> > On Wed, Apr 12, 2017 at 7:58 AM, Dmitriy Setrakyan <
> >> dsetrak...@apache.org>
> > wrote:
> >
> >> Awesome! Great addition to the project.
> >>
> >> On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda 
> >> wrote:
> >>
> >>> Spring Data integration caught up the train and will be released in
> > 2.0:
> >>> https://issues.apache.org/ jira/browse/IGNITE-1192 <
> >>> https://issues.apache.org/ jira/browse/IGNITE-1192>
> >>>
> >>> —
> >>> Denis
> >>>
>  On Apr 9, 2017, at 6:57 AM, Denis Magda 
> >> wrote:
> 
>  Val, yes, as far as I know we still need to merge to the master.
> The
> >>> branch should be ready later the next week.
> 
>  Denis
> 
>  On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
> >>> valentin.kuliche...@gmail.com  gmail.com
> 
> >>> wrote:
>  Guys,
> 
>  There is no branch for 2.0 right now, correct? If I want to add
> >> something
>  there, do I just merge to master?
> 
>  -Val
> 
>  On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
>  alexander.a.paschenko@gmail. com  >> gmail.com>>
> >>> wrote:
> 
> > I've fixed https://issues.apache.org/ jira/browse/IGNITE-4354 <
> >>> https://issues.apache.org/ jira/browse/IGNITE-4354>, PR is
> > https://github.com/apache/ ignite/pull/1759 <
> >> https://github.com/apache/
> >>> ignite/pull/1759>.
> > Pavel, thank you very much for bringing that to my attention.
> >
> > - Alex
> >
> 

[jira] [Created] (IGNITE-5088) problems with trying OSGi

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5088:
--

 Summary: problems with trying OSGi
 Key: IGNITE-5088
 URL: https://issues.apache.org/jira/browse/IGNITE-5088
 Project: Ignite
  Issue Type: Bug
  Components: osgi
Reporter: Pavel Konstantinov


I've tried to execute test suit from AI 2.0 source build but faced with error.
I went through apache-ignite-2.0.0-src/modules/osgi/README.txt and stuck on 
this step
{code}
You may then run the OSGi test suite:

   mvn test -Dtest=IgniteOsgiTestSuite
{code}
Actually I ran such command
{code}
mvn test -Dtest=IgniteOsgiTestSuite -DfailIfNoTests=false
{code}
and got the following result
{code}
Results :

Tests in error: 
  IgniteOsgiServiceTest.testServiceExposedAndCallbacksInvoked » MalformedURL 
unk...
  IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled 
» MalformedURL

Tests run: 2, Failures: 0, Errors: 2, Skipped: 0

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ignite-apache-license-gen .. SUCCESS [  1.054 s]
[INFO] ignite-tools ... SUCCESS [  2.244 s]
[INFO] ignite-core  SUCCESS [ 46.015 s]
[INFO] ignite-log4j ... SUCCESS [  0.530 s]
[INFO] ignite-indexing  SUCCESS [  1.589 s]
[INFO] ignite-urideploy ... SUCCESS [  0.933 s]
[INFO] ignite-spring .. SUCCESS [  0.959 s]
[INFO] ignite-hadoop .. SUCCESS [  2.595 s]
[INFO] ignite-extdata-p2p . SUCCESS [  0.384 s]
[INFO] ignite-extdata-uri-dep . SUCCESS [  0.126 s]
[INFO] ignite-extdata-uri . SUCCESS [  0.454 s]
[INFO] ignite-rest-http ... SUCCESS [  0.799 s]
[INFO] ignite-clients . SUCCESS [  0.284 s]
[INFO] ignite-spring-data . SUCCESS [  0.297 s]
[INFO] ignite-web . SUCCESS [  0.544 s]
[INFO] ignite-aop . SUCCESS [  0.616 s]
[INFO] ignite-ssh . SUCCESS [  0.395 s]
[INFO] ignite-jta . SUCCESS [  0.552 s]
[INFO] ignite-aws . SUCCESS [  0.904 s]
[INFO] ignite-log4j2 .. SUCCESS [  0.702 s]
[INFO] ignite-slf4j ... SUCCESS [  0.412 s]
[INFO] ignite-jcl . SUCCESS [  0.563 s]
[INFO] ignite-codegen . SUCCESS [  0.116 s]
[INFO] ignite-gce . SUCCESS [  0.334 s]
[INFO] ignite-cloud ... SUCCESS [  2.381 s]
[INFO] ignite-mesos ... SUCCESS [  0.223 s]
[INFO] ignite-kafka ... SUCCESS [  1.443 s]
[INFO] ignite-flume ... SUCCESS [  0.894 s]
[INFO] ignite-yarn  SUCCESS [  0.628 s]
[INFO] ignite-jms11 ... SUCCESS [  0.753 s]
[INFO] ignite-twitter . SUCCESS [  0.589 s]
[INFO] ignite-mqtt  SUCCESS [  1.343 s]
[INFO] ignite-zookeeper ... SUCCESS [  0.558 s]
[INFO] ignite-camel ... SUCCESS [  1.086 s]
[INFO] ignite-storm ... SUCCESS [  0.312 s]
[INFO] ignite-osgi-paxlogging . SUCCESS [  0.109 s]
[INFO] ignite-osgi-karaf .. SUCCESS [  0.049 s]
[INFO] ignite-osgi  FAILURE [  1.273 s]
[INFO] ignite-appserver-test .. SKIPPED
[INFO] ignite-websphere-test .. SKIPPED
[INFO] ignite-cassandra ... SKIPPED
[INFO] ignite-cassandra-store . SKIPPED
[INFO] ignite-cassandra-serializers ... SKIPPED
[INFO] ignite-flink ... SKIPPED
[INFO] ignite-kubernetes .. SKIPPED
[INFO] ignite-zeromq .. SKIPPED
[INFO] ignite-scalar .. SKIPPED
[INFO] ignite-spark ... SKIPPED
[INFO] ignite-visor-console ... SKIPPED
[INFO] ignite-visor-plugins ... SKIPPED
[INFO] 

Re: joining exchange

[Semyon Boikov]

To send message to coordinator we need establish new connection, it is
preferably to use existing connections. Actually we tested this approach,
and on large clusters (> 200 nodes) it did not give start time improvments.

Thanks

On Wed, Apr 26, 2017 at 1:06 PM, ALEKSEY KUZNETSOV  wrote:

> Hi, Igntrs!
> When new node joins topology, it sends join TcpDiscoveryJoinRequestMessage
> to arbitrary node N1.
> If N1 is not coordinator, then it will resend to all nodes.
>
> Why doesn't N1 send the message directly to coordinator ?
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

Re: joining exchange

[Dmitriy Setrakyan]

On Wed, Apr 26, 2017 at 1:06 PM, ALEKSEY KUZNETSOV  wrote:

> Hi, Igntrs!
> When new node joins topology, it sends join TcpDiscoveryJoinRequestMessage
> to arbitrary node N1.
> If N1 is not coordinator, then it will resend to all nodes.
>
> Why doesn't N1 send the message directly to coordinator ?
>

It think that the joining node sends its join-request message to the IP
address that was provided by the IP Finder, possibly in the configuration.

--
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

[GitHub] ignite pull request #1872: MemoryMetrics interface cleanup, MemoryMetricsImp...

[sergey-chugunov-1985]

Github user sergey-chugunov-1985 closed the pull request at:

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


---
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-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5087:


 Summary: Enum comparison fails after marshal-unmarshal with 
BinaryMarshaller.
 Key: IGNITE-5087
 URL: https://issues.apache.org/jira/browse/IGNITE-5087
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.9
Reporter: Andrew Mashenkov
 Fix For: 2.1
 Attachments: EnumBinaryMarshallerBug.java

PFA repro.
It fails on 1.9 and on 2.0-snapshot as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1875: Ignite gg 12084 2

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

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

Ignite gg 12084 2



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

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12084_2

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

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


commit d8480bdc22048ffadd3716f5d3a1f1c6a1797a0f
Author: devozerov 
Date:   2017-04-18T12:24:19Z

IGNITE-4990: Removed deprecated properties from FileSystemConfiguration. 
This closes #1816.

commit eaf7350c64aabd98084df4eca337923c0208d085
Author: devozerov 
Date:   2017-04-18T12:25:27Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 3565e4ee60e705e0bc34a73045a8b9b161df2e6e
Author: Anton Vinogradov 
Date:   2017-04-18T12:32:29Z

Special profiles to set versions and check compilation across all modules

commit 862d8af0a27974eec76665a8d336a4be4c08361a
Author: Dmitriy Govorukhin 
Date:   2017-04-18T12:42:54Z

master - fixed SPI test

commit c4d81808c3cc002f1c71afb275361b728a84440b
Author: Dmitriy Govorukhin 
Date:   2017-04-18T12:44:15Z

master - Fixed jetty REST processor testIncorrectPut

commit 22580e19b7ae5d11b8c299e2b3d92f5c8b9f0e8c
Author: Alexander Belyak 
Date:   2017-04-18T11:56:50Z

IGNITE-4927 Write behind - add an option to skip write coalescing

Signed-off-by: nikolay_tikhonov 

commit 58a8cb2579665c989ea9b08ebebf7b050f4d1405
Author: Pavel Tupitsyn 
Date:   2017-04-18T13:01:49Z

.NET: Fix MessagingTest flakiness

commit 7038af4a7d976e59a7875b32b3ee3dfc1758908d
Author: Yury Babak 
Date:   2017-04-18T13:46:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation

commit d78e071a7de1129838652e9f377ff73d3a84495d
Author: Yury Babak 
Date:   2017-04-18T13:47:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation

commit d60cf53bbfae162ac96ec1525bcd1772b8249a79
Author: Konstantin Dudkov 
Date:   2017-04-18T13:50:16Z

ignite-4982 Fixed GridIntList.

commit 43d6d7e7eb9eb146c48b843293849ac687ead216
Author: sboikov 
Date:   2017-04-18T13:50:45Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 8ea9f83ce7f21f6ba50c0c644f62319f25b56ebd
Author: Alexey Kuznetsov 
Date:   2017-04-18T13:39:58Z

master Fixed Visor tests.
(cherry picked from commit 36a6cd0)

commit 9e7421f261354b28119094b3b53b9490fd817b24
Author: devozerov 
Date:   2017-04-18T14:04:43Z

Merge branch 'master' into ignite-2.0

commit 2edb935cbf87198993c403724e26efc655710c25
Author: devozerov 
Date:   2017-04-18T14:11:34Z

IGNITE-4565: Implemented CREATE INDEX and DROP INDEX. This closes #1773. 
This closes #1804.

commit 9b21c85d6ec0cdbba8cbf2382559a8ef5a82e15c
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:27Z

master - Mute test with a correct link

commit f82ed01807c80b36b7e361a5800ea131c1431c14
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:55Z

master - Fix mvcc tests after CLOCK mode removal

commit 36e7e19830dc53c0ed02a0d83806b2cb5a7c7ce5
Author: Alexey Kuznetsov 
Date:   2017-04-19T04:34:16Z

IGNITE-4988 Cleanup code.

commit d38348432a2b8b66999c6410ec4f5c1ef050191d
Author: sboikov 
Date:   2017-04-19T09:46:31Z

Attempt to fix awaitPartitionMapExchange: wait for last exchange completion 
to avoid races with cache destroy.

commit 22d5e55bee69403c4f9f8da9c113751ce110aa2d
Author: tledkov-gridgain 
Date:   2017-04-19T09:54:14Z

IGNITE-3523 IGFS: Remove "initialize default path modes" feature. This 
closes #1786.

commit 2ded758ad1f1663aea05ca943ecf509b1574c0bf
Author: devozerov 
Date:   2017-04-19T09:54:34Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 800b8bd90033ab64f4299ba242cc89b1f4c98417
Author: Alexey Goncharuk 
Date:   2017-04-19T10:55:02Z

IGNITE-4993 - Fixing distributed joins on segmented index.

commit b47f29d83f25037c5bf3cfe489b7120a238c7120
Author: Evgenii Zhuravlev 
Date:   2017-04-19T11:01:21Z

IGNITE-4925 Fix IgniteCacheBinaryObjectsScanSelfTest.testScanNoClasses - 

joining exchange

[ALEKSEY KUZNETSOV]

Hi, Igntrs!
When new node joins topology, it sends join TcpDiscoveryJoinRequestMessage
to arbitrary node N1.
If N1 is not coordinator, then it will resend to all nodes.

Why doesn't N1 send the message directly to coordinator ?
-- 

*Best Regards,*

*Kuznetsov Aleksey*

[jira] [Created] (IGNITE-5086) Web Console: Redesign of Modal Windows

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-5086:
-

 Summary: Web Console: Redesign of Modal Windows
 Key: IGNITE-5086
 URL: https://issues.apache.org/jira/browse/IGNITE-5086
 Project: Ignite
  Issue Type: Task
  Components: UI, wizards
Reporter: Vica Abramova
Assignee: Dmitriy Shabalin






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5085) Re

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-5085:
-

 Summary: Re
 Key: IGNITE-5085
 URL: https://issues.apache.org/jira/browse/IGNITE-5085
 Project: Ignite
  Issue Type: Task
Reporter: Vica Abramova






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5084) PagesList.put() assertion: pageId != tailId

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-5084:
--

 Summary: PagesList.put() assertion: pageId != tailId
 Key: IGNITE-5084
 URL: https://issues.apache.org/jira/browse/IGNITE-5084
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.0
Reporter: Alexandr Kuramshin


Get an error upon rebalancing on topology update

{noformat}
Failed processing message [senderId=78a8f841-5d40-4ac7-b26b-f1b5e7f3faa0, 
msg=GridDhtPartitionSupplyMessageV2 [updateSeq=142, 
topVer=AffinityTopologyVersion [topVer=8, minorTopVer=0], missed=null, 
clean=[0, 1, 2, 3, 4, 5, 6, 7, 8, 11, 12, 13, 14, 17, 19, 21, 20, 23, 22, 24, 
26, 29, 28, 31, 35, 32, 33, 39, 36, 37, 42, 43, 40, 41, 44, 45, 51, 48, 55, 54, 
53, 52, 58, 56, 63, 62, 60, 68, 69, 65, 66, 76, 77, 78, 74, 85, 87, 86, 81, 80, 
82, 92, 91, 90, 98, 96, 97], msgSize=0, size=67, parts=[0, 1, 2, 3, 4, 5, 6, 7, 
8, 11, 12, 13, 14, 17, 19, 21, 20, 23, 22, 24, 26, 29, 28, 31, 35, 32, 33, 39, 
36, 37, 42, 43, 40, 41, 44, 45, 51, 48, 55, 54, 53, 52, 58, 56, 63, 62, 60, 68, 
69, 65, 66, 76, 77, 78, 74, 85, 87, 86, 81, 80, 82, 92, 91, 90, 98, 96, 97], 
super=GridCacheMessage [msgId=100460, depInfo=null, err=null, 
skipPrepare=false, cacheId=-2100569601, cacheId=-2100569601]]]
java.lang.AssertionError: pageId = 0, tailId = 281556581089286
at 
org.apache.ignite.internal.processors.cache.database.freelist.PagesList.put(PagesList.java:~)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)