date:20171201

RE: Does the Ignite C# client support distributed queues?

2017-12-01 Thread Raymond Wilson

Hi Alexey,



I think I need to be logged-in to vote for it. How do I get a credential to
do that?



Can you speak to my second question regards the plan for functional
equivalence between C# & Java clients?



Thanks,

Raymond.



*From:* Alexey Popov [mailto:tank2.a...@gmail.com]
*Sent:* Saturday, December 2, 2017 4:49 AM
*To:* u...@ignite.apache.org
*Cc:* dev@ignite.apache.org
*Subject:* RE: Does the Ignite C# client support distributed queues?



Hi Raymond,



You are right, distributed queues require changes at Ignite core.

https://issues.apache.org/jira/browse/IGNITE-2701

It was created almost 1 year ago. Please vote for this feature.

As far as I know there is no plan/schedule for it.



Thank you,
Alexey



*From: *Raymond Wilson 
*Sent: *Friday, December 1, 2017 5:58 AM
*To: *u...@ignite.apache.org
*Cc: *dev@ignite.apache.org
*Subject: *RE: Does the Ignite C# client support distributed queues?



Looking at it I see it's blocked by 2701 (which has additional

dependencies, all of which say they are blocked by 2701).



I understand there is an intention to bring the C# client up to par with

the Java client. Is there a ticket/schedule yet for this?



Raymond.



-Original Message-

From: vkulichenko [mailto:valentin.kuliche...@gmail.com
]

Sent: Friday, December 1, 2017 1:30 PM

To: u...@ignite.apache.org

Subject: RE: Does the Ignite C# client support distributed queues?



Oops, I read wrong! This is not supported. There is a ticket, but it

doesn't seem to be active at the moment:

https://issues.apache.org/jira/browse/IGNITE-1417



-Val







--

Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Request for Participation: The Right Metrics for the Right Project

2017-12-01 Thread Denis Magda

+ Ignite dev

Rafael,

That’s a really useful project. I would use it for Ignite metrics analysis.

How do you measure the pony-factor (contributors/committers breakdown per 
specific organization)?

Is there a way to see user/dev list specific metrics such as most active 
participants (senders and responders), number of signs-up, etc.?

Igniters, please log in and provide your feedback. The details are below.

—
Denis

> On Nov 30, 2017, at 4:30 PM, Rafael Weingärtner  
> wrote:
> 
> https://demo.kibble.apache.org/dashboard.html?page=repos=true=d58d1803c1337bc2762059eb4d6bd72cca53c4a3c981dcf48d1f7412
>  
> 
> 
> You need to log in as guest. The username and password are presented in the 
> login interface.
> 
> On Thu, Nov 30, 2017 at 9:53 PM, Denis Magda  > wrote:
> Rafael,
> 
> Where should I go to see Ignite metrics? Tried to look for data here but this 
> seems to be a wrong place:
> https://demo.kibble.apache.org/ 
> 
> —
> Denis
> 
>> On Nov 30, 2017, at 11:43 AM, Rafael Weingärtner 
>> > wrote:
>> 
>> sure.
>> You can already see Ignite status there ;)
>> 
>> On Thu, Nov 30, 2017 at 5:41 PM, Denis Magda > > wrote:
>> Hi Rafael,
>> 
>> Confirming that the information is correct. Please CC me in all the related 
>> discussions directly.
>> 
>> —
>> Denis
>> 
>>> On Nov 30, 2017, at 5:30 AM, Rafael Weingärtner 
>>> > wrote:
>>> 
>>> 
>>> -- Forwarded message --
>>> From: Rafael Weingärtner >> >
>>> Date: Thu, Nov 30, 2017 at 11:29 AM
>>> Subject: Re: Request for Participation: The Right Metrics for the Right 
>>> Project
>>> To: d...@kibble.apache.org 
>>> 
>>> 
>>> Hi Denis, 
>>> Can you confirm the Apache Ignite information? so I can add it
>>> 
>>> GitHub repo(s):
>>> https://github.com/apache/ignite.git 
>>> 
>>> Jira:
>>> https://issues.apache.org/jira/browse/IGNITE 
>>> 
>>> 
>>> Mailing lists:
>>> https://lists.apache.org/list.html?u...@ignite.apache.org 
>>> 
>>> https://lists.apache.org/list.html?dev@ignite.apache.org 
>>> 
>>> https://lists.apache.org/list.html?iss...@ignite.apache.org 
>>> 
>>> 
>>> On Mon, Nov 27, 2017 at 9:48 PM, Denis Magda >> > wrote:
>>> Hi Daniel,
>>> 
>>> Is there an easy way to hook Kibble with Ignite? We’re definitely 
>>> interested in such capabilities.
>>> 
>>> —
>>> Denis
>>> 
>>> > On Nov 27, 2017, at 10:26 AM, Daniel Gruno >> > > wrote:
>>> >
>>> > Hi there, fellow Apache projects!
>>> >
>>> > The Apache Kibble project serves as a practical implementation of
>>> > metrics deemed to be helpful for open source projects trying to
>>> > understand where their project is, was, and is headed.
>>> >
>>> > As such, we need help in determining which metrics projects either
>>> > already use and consider useful for measuring project health or which
>>> > metrics they would love to have and use.
>>> >
>>> > We are looking for projects interested in participating in the Kibble
>>> > demo instance ( https://demo.kibble.apache.org/ 
>>> >  ) and sending feedback
>>> > to the Kibble project on which parts they find useful, which elements
>>> > they find useless and which ideas they would love to see implemented to
>>> > better gauge the health and activity of their project.
>>> >
>>> > Initially we are looking for Apache projects to help out, but we will
>>> > later on expand this to other open source organizations and projects.
>>> >
>>> > Projects that participate will be added to the demo instance and scanned
>>> > on a regular basis so the data can be used for reports and analysis.
>>> > The Kibble PMC will ensure that the correct sources are added, but you
>>> > are of course welcome to help identify which parts need analyzing.
>>> >
>>> > How to participate:
>>> >
>>> > - Join the d...@kibble.apache.org  mailing 
>>> > list and let us know if your
>>> > project is interested in joining the demo (a few projects were added in
>>> > advance so you can actually test it). You can also join us on HipChat or
>>> > in #kibble on Freenode IRC (IRC and HipChat are bridged).
>>> >
>>> > - Try out the demo, and send us feedback to the mailing list on

RE: ci.ignite.apache: Run all for patch (jira number)

2017-12-01 Thread Cergey

The idea of doing so arose after I uploaded the changed patch second time and 
it didn't appear in teamcity to run against (changes). Should automatic build 
triggering work ? Anyway, I'll go for patch then.

-Original Message-
From: Dmitry Pavlov [mailto:dpavlov@gmail.com] 
Sent: Saturday, December 2, 2017 2:02 AM
To: dev@ignite.apache.org
Subject: Re: ci.ignite.apache: Run all for patch (jira number)

Hi Cergey,

for pull requests I use pull//head branch specification in changes field 
(e.g pull/2970/head) and 
https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAll run 
configuration.

Recently we've updated link on GitHub page so new contributors can see correct 
link.

Not sure if `run all for patch` works fine.

Sincerely,
Dmitriy Pavlov

пт, 1 дек. 2017 г. в 20:42, Denis Magda :

> It’s possible but requires you to create a branch and pass its name 
> into
> TeamCity:
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#H
> owtoContribute-2.CreateaPatch-file
> <
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#H
> owtoContribute-2.CreateaPatch-file
> >
>
> However, this approach works only for Ignite committers who have 
> enough permissions for branches creation.
>
> Plus, it’s easier for a reviewer to check the changes via 
> pull-requests and leave comments there.
>
> —
> Denis
>
> > On Nov 30, 2017, at 11:28 PM, Cergey  wrote:
> >
> > But I want to run the tests against the patch in jira (it is kinda
> easier to make changes in the patch). Is that feasible ?
> >
> > -Original Message-
> > From: Denis Magda [mailto:dma...@apache.org]
> > Sent: Friday, December 1, 2017 4:53 AM
> > To: dev@ignite.apache.org
> > Subject: Re: ci.ignite.apache: Run all for patch (jira number)
> >
> > Cergey,
> >
> > You need to run the tests agains the pull-request. In your case it
> should be this one - pull/2970/merge
> >
> > —
> > Denis
> >
> >> On Nov 30, 2017, at 12:36 PM, Cergey  wrote:
> >>
> >> Probably, I missed something in the patch (
> https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not 
> (and did not) start automatically. What may be wrong ?
> >>
> >> -Original Message-
> >> From: Cergey [mailto:cossa...@mail.ru.INVALID]
> >> Sent: Friday, December 1, 2017 12:31 AM
> >> To: dev@ignite.apache.org
> >> Subject: ci.ignite.apache: Run all for patch (jira number)
> >>
> >> Hi, igniters,
> >>
> >> When trying to run "Run all for patch" build with parameter "jira
> number" (existing, e.g. IGNITE-6745 or random), build fails (
> https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_R
> unAllTestBuilds) with exception: java.net.ConnectException: Connection 
> timed out. Is this functionality not supported or I incorrectly set 
> the jira number ?
> >>
> >>
> >
> >
>
>

Re: Documentation for GA Grid: GA library to Apache Ignite

2017-12-01 Thread techbysample

Denis,

Up on logging in, I do not see the Admin panel that you described.

I have attached a screen shot for you review.



 

There is only 'Suggest Edits' option.

Is there something I missed?

Please advise.

Best,
Turik



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: ci.ignite.apache: Run all for patch (jira number)

2017-12-01 Thread Dmitry Pavlov

Hi Cergey,

for pull requests I use pull//head branch specification in changes
field (e.g pull/2970/head)
and
https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAll run
configuration.

Recently we've updated link on GitHub page so new contributors can see
correct link.

Not sure if `run all for patch` works fine.

Sincerely,
Dmitriy Pavlov

пт, 1 дек. 2017 г. в 20:42, Denis Magda :

> It’s possible but requires you to create a branch and pass its name into
> TeamCity:
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-2.CreateaPatch-file
> <
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-2.CreateaPatch-file
> >
>
> However, this approach works only for Ignite committers who have enough
> permissions for branches creation.
>
> Plus, it’s easier for a reviewer to check the changes via pull-requests
> and leave comments there.
>
> —
> Denis
>
> > On Nov 30, 2017, at 11:28 PM, Cergey  wrote:
> >
> > But I want to run the tests against the patch in jira (it is kinda
> easier to make changes in the patch). Is that feasible ?
> >
> > -Original Message-
> > From: Denis Magda [mailto:dma...@apache.org]
> > Sent: Friday, December 1, 2017 4:53 AM
> > To: dev@ignite.apache.org
> > Subject: Re: ci.ignite.apache: Run all for patch (jira number)
> >
> > Cergey,
> >
> > You need to run the tests agains the pull-request. In your case it
> should be this one - pull/2970/merge
> >
> > —
> > Denis
> >
> >> On Nov 30, 2017, at 12:36 PM, Cergey  wrote:
> >>
> >> Probably, I missed something in the patch (
> https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not (and
> did not) start automatically. What may be wrong ?
> >>
> >> -Original Message-
> >> From: Cergey [mailto:cossa...@mail.ru.INVALID]
> >> Sent: Friday, December 1, 2017 12:31 AM
> >> To: dev@ignite.apache.org
> >> Subject: ci.ignite.apache: Run all for patch (jira number)
> >>
> >> Hi, igniters,
> >>
> >> When trying to run "Run all for patch" build with parameter "jira
> number" (existing, e.g. IGNITE-6745 or random), build fails (
> https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAllTestBuilds)
> with exception: java.net.ConnectException: Connection timed out. Is this
> functionality not supported or I incorrectly set the jira number ?
> >>
> >>
> >
> >
>
>

[jira] [Created] (IGNITE-7092) Deprecate embedded mode in IgniteRDD

2017-12-01 Thread Valentin Kulichenko (JIRA)

Valentin Kulichenko created IGNITE-7092:
---

 Summary: Deprecate embedded mode in IgniteRDD
 Key: IGNITE-7092
 URL: https://issues.apache.org/jira/browse/IGNITE-7092
 Project: Ignite
  Issue Type: Improvement
  Components: spark
Affects Versions: 2.3
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
 Fix For: 2.4


Currently we claim to support IgniteRDD in two modes: standalone and embedded. 
Standalone means there is a separately running Ignite cluster, and Spark start 
client node(s) to interact with it. In embedded node everything runs within 
Spark, including Ignite server nodes that are started embedded into Spark 
executors.

The latter case doesn't really work, mainly because the lifecycle of Spark 
executors is not very predictable - Spark can start and stop them while 
application is running. In case Ignite cluster is used to store data (which is 
usually the case), this causes unnecessary rebalancing or even unexpected data 
loss.

I propose to deprecate and eventually discontinue the embedded mode. Luckily, 
standalone mode is the default one, so we can simply print out a clear warning 
if one switches to embedded mode, and also mention this in the docs.



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

Re: Deprecate IgniteRDD in embedded mode

2017-12-01 Thread Valentin Kulichenko

Ticket created: https://issues.apache.org/jira/browse/IGNITE-7092

-Val

On Thu, Nov 30, 2017 at 5:01 PM, Denis Magda  wrote:

> Val,
>
> Sounds reasonable to me. The fewer useless and potentially harmful
> features or “switches” we have in Ignite the clear it will be for the user
> how to use us in a right way.
>
> +1 for the deprecation and further removal.
>
> —
> Denis
>
> > On Nov 30, 2017, at 3:07 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
> >
> > Igniters,
> >
> > Currently we claim to support IgniteRDD in two modes: standalone and
> > embedded. Standalone means there is a separately running Ignite cluster,
> > and Spark start client node(s) to interact with it. In embedded node
> > everything runs within Spark, including Ignite server nodes that are
> > started embedded into Spark executors.
> >
> > The latter case doesn't really work, mainly because the lifecycle of
> Spark
> > executors is not very predictable - Spark can start and stop them while
> > application is running. In case Ignite cluster is used to store data
> (which
> > is usually the case), this causes unnecessary rebalancing or even
> > unexpected data loss.
> >
> > I propose to deprecate and eventually discontinue the embedded mode.
> > Luckily, standalone mode is the default one, so we can simply print out a
> > clear warning if one switches to embedded mode, and also mention this in
> > the docs.
> >
> > Thoughts? If there are no objections, I will create a ticket and make the
> > change.
> >
> > -Val
>
>

[GitHub] ignite pull request #3130: IGNITE-6565: Use long type for size and keySize i...

2017-12-01 Thread SharplEr

GitHub user SharplEr opened a pull request:

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

IGNITE-6565: Use long type for size and keySize in cache metrics

https://issues.apache.org/jira/browse/IGNITE-6565

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

$ git pull https://github.com/SharplEr/ignite ignite-6565

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

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


commit 011a466d2d2c58f99482569ebcddf9d4d589e6f1
Author: Alexander Menshikov 
Date:   2017-11-13T16:11:02Z

Add long metrics

commit 2a567640205b092491720836f79ef4a0ee30c4df
Author: Alexander Menshikov 
Date:   2017-11-23T17:01:34Z

Add sizeLong to VisorCacheMetrics

commit 6516495d8507dd93b05322196a9d3fcba1b0d541
Author: Alexander Menshikov 
Date:   2017-11-24T14:16:33Z

Add testSize

commit 6117290bd1b25bed65cc7e06715f4ab412fc8a4d
Author: Alexander Menshikov 
Date:   2017-11-24T15:38:51Z

.net fix

commit 61bdcb4941a01fb34e169f39cfce081986335ad9
Author: Alexander Menshikov 
Date:   2017-11-29T16:18:11Z

Add sizeLong write in platform usege

commit b9c67295c4216d25f5f1ee91258364d2cafce19b
Author: SharplEr 
Date:   2017-11-30T12:58:14Z

Fix in donNet platform

commit 4340a2dd7d45db4a7ef21af3d582f0f9101f84c8
Author: Alexander Menshikov 
Date:   2017-11-30T13:08:05Z

In near cache size and sizeLong are not equals

commit e66229ccaeb5f4a805abc5a9ac68aa27f8d512b6
Author: Alexander Menshikov 
Date:   2017-12-01T19:20:08Z

fix line length

commit fea8b9d6997f486cec938b0045525ec44ae3acf1
Author: Alexander Menshikov 
Date:   2017-12-01T19:34:24Z

Fix tabs

commit 5f006286e6bc7fd691b74a38daa175f1fbd5a990
Author: Alexander Menshikov 
Date:   2017-12-01T19:45:42Z

Add newline!




---

[GitHub] ignite pull request #3129: Fixed DataStructures restore from snapshot

2017-12-01 Thread ilantukh

GitHub user ilantukh opened a pull request:

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

Fixed DataStructures restore from snapshot



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

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

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

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


commit 44a69a189d1ed638aa808393608eaa6de2b9b1a2
Author: Ilya Lantukh 
Date:   2017-10-31T12:31:59Z

gg-13029 : Forward-ported gg-13005 (fix for datastructures restore from 
snapshot)




---

Fwd: [jira] [Created] (IGNITE-7083) Reduce memory usage of CachePartitionFullCountersMap

2017-12-01 Thread Denis Magda

Ignite, especially Sam and Alex G., what’d you think about this?

—
Denis

> Begin forwarded message:
> 
> From: "Sunny Chan (JIRA)" 
> Subject: [jira] [Created] (IGNITE-7083) Reduce memory usage of 
> CachePartitionFullCountersMap
> Date: November 30, 2017 at 8:31:01 PM PST
> To: dev@ignite.apache.org
> Reply-To: dev@ignite.apache.org
> 
> Sunny Chan created IGNITE-7083:
> --
> 
> Summary: Reduce memory usage of CachePartitionFullCountersMap
> Key: IGNITE-7083
> URL: https://issues.apache.org/jira/browse/IGNITE-7083
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.3
> Environment: Any
>Reporter: Sunny Chan
> 
> 
> The Cache Partition Exchange Manager kept a copy of the already completed 
> exchange. However, we have found that it uses a significant amount of memory. 
> Upon further investigation using heap dump we have found that a large amount 
> of memory is used by the CachePartitionFullCountersMap. We have also observed 
> in most cases, these maps contains only 0s.
> 
> Therefore I propose an optimization for this: Initially the long arrays to 
> store initial update counter and update counter in the CPFCM will be null, 
> and when you get the value and see these tables are null then we will return 
> 0 for the counter. We only allocate the long arrays when there is any 
> non-zero updates to the the map.
> 
> In our tests, the amount of heap used by GridCachePartitionExchangeManager 
> was around 70MB (67 copies of these CPFCM), after we apply the optimization 
> it drops to around 9MB.
> 
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)

Re: Time to drop Java 7?

2017-12-01 Thread Dmitry Pavlov

Excellent, let's do it!

пт, 1 дек. 2017 г. в 20:43, Denis Magda :

> > Is my understanding correct, that the level of the VM for the source code
> > will be 8?
>
> Exactly!
>
> —
> Denis
>
> > On Dec 1, 2017, at 3:06 AM, Dmitry Pavlov  wrote:
> >
> > +1.
> >
> > I am sincerely glad that we are ready to do this!
> >
> > Is my understanding correct, that the level of the VM for the source code
> > will be 8?
> >
> > пт, 1 дек. 2017 г. в 13:32, Andrey Gura :
> >
> >> Good news for everyone )
> >>
> >> 30 нояб. 2017 г. 11:29 PM пользователь "Dmitriy Setrakyan" <
> >> dsetrak...@apache.org> написал:
> >>
> >>> +1
> >>>
> >>> On Thu, Nov 30, 2017 at 11:29 AM, Denis Magda 
> wrote:
> >>>
>  Igniters,
> 
>  Considering that we’re going to support Java 9 in the next release and
>  hitting several limitations caused by current Java 7 support (see
> spark
>  issue [2] and account difficulties of Java 8 based ML development) I
> >>> would
>  propose to discontinue Java 7.
> 
>  Let’s do both things in AI 2.4: Java 9 support and Java 7 removal.
> 
>  Share your thoughts on this?
> 
>  [1] http://apache-ignite-developers.2346864.n4.nabble.
>  com/Java-9-support-td23612.html
>  [2] http://apache-ignite-developers.2346864.n4.nabble.
>  com/TC-issues-IGNITE-3084-Spark-Data-Frame-API-td24639.html <
>  http://apache-ignite-developers.2346864.n4.nabble.
>  com/TC-issues-IGNITE-3084-Spark-Data-Frame-API-td24639.html>
> 
>  —
>  Denis
> >>>
> >>
>
>

[GitHub] ignite pull request #3084: IGNITE-7007: Code cleanups.

2017-12-01 Thread asfgit

Github user asfgit closed the pull request at:

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


---

Re: Are there any access control for ignite rest api

2017-12-01 Thread Denis Magda

Hi,

What’s Ignite Access Control? I’ve never heard about this tool/component.

—
Denis

> On Dec 1, 2017, at 8:00 AM, kcmvp  wrote:
> 
> Hi All,
> 
> Are there any access control fro Ignite Access Control? For my case I just
> want get related rest api can be accessed ?
> Of course it's better to have fine control
> 
> 
> 
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Ignite Logger & logging file config output

2017-12-01 Thread Denis Magda

Alexey,

Thanks, looks good to me too. Let’s merge the changes into the master.

—
Denis

> On Dec 1, 2017, at 6:35 AM, Alexey Popov  wrote:
> 
> Yes, it is implemented for all Ignite loggers. 
> However, some loggers (Slf4jLogger) does not have logging file configuration, 
> so they show less details.
> 
> Thank you,
> Alexey
> 
> From: Nikolai Tikhonov
> Sent: Friday, December 1, 2017 5:21 PM
> To: dev@ignite.apache.org
> Subject: Re: Ignite Logger & logging file config output
> 
> Alexey,
> 
> Looks cool and helpful! I understand correctly that improvement is
> implemented for all type of loggers which Ignite supports?
> 
> On Fri, Dec 1, 2017 at 5:18 PM, Alexey Popov  wrote:
> 
>> Hi Denis,
>> 
>> https://issues.apache.org/jira/browse/IGNITE-6971
>> 
>> Sample quite=true output:
>> 
>> [17:16:41]__  
>> [17:16:41]   /  _/ ___/ |/ /  _/_  __/ __/
>> [17:16:41]  _/ // (7 7// /  / / / _/
>> [17:16:41] /___/\___/_/|_/___/ /_/ /___/
>> [17:16:41]
>> [17:16:41] ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
>> [17:16:41] 2017 Copyright(C) Apache Software Foundation
>> [17:16:41]
>> [17:16:41] Ignite documentation: http://ignite.apache.org
>> [17:16:41]
>> [17:16:41] Quiet mode.
>> [17:16:41]   ^-- Logging to file 'C:\incubator-ignite\work\log\
>> ignite-7317b109.log'
>> [17:16:41]   ^-- Logging by 'Log4JLogger [quiet=true,
>> config=/C:/incubator-ignite/config/ignite-log4j.xml]'
>> [17:16:41]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
>> or "-v" to ignite.{sh|bat}
>> [17:16:41]
>> [17:16:41] OS: Windows 10 10.0 amd64
>> [17:16:41] VM information: Java(TM) SE Runtime Environment 1.8.0_141-b15
>> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
>> [17:16:41] Initial heap size is 254MB (should be no less than 512MB, use
>> -Xms512m -Xmx512m).
>> [17:16:41] Configured plugins:
>> [17:16:41]   ^-- None
>> [17:16:41]
>> 
>> Sample verbose output:
>> 
>   __  
>  /  _/ ___/ |/ /  _/_  __/ __/
> _/ // (7 7// /  / / / _/
> /___/\___/_/|_/___/ /_/ /___/
> 
> ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
> 2017 Copyright(C) Apache Software Foundation
> 
> Ignite documentation: http://ignite.apache.org
>> 
>> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Config
>> URL: n/a
>> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Daemon
>> mode: off
>> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] OS:
>> Windows 10 10.0 amd64
>> 2017-12-01T17:06:49,404][INFO ][main][IgniteKernal%verboseLogGrid] OS
>> user: gridgain
>> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] PID:
>> 5984
>> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid]
>> Language runtime: Java Platform API Specification ver. 1.8
>> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] VM
>> information: Java(TM) SE Runtime Environment 1.8.0_141-b15 Oracle
>> Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
>> 2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] VM
>> total memory: 3.5GB
>> 2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] Remote
>> Management [restart: off, REST: off, JMX (remote: off)]
>> 2017-12-01T17:06:49,416][INFO ][main][IgniteKernal%verboseLogGrid]
>> Logger: Log4J2Logger [quiet=false, config=C:\incubator-ignite\
>> modules\core\src\test\config\log4j2-verbose-test.xml]
>> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid]
>> IGNITE_HOME=C:\incubator-ignite
>> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] VM
>> arguments: [-ea, -Didea.test.cyclic.buffer.size=1048576,
>> -javaagent:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
>> 2017.2.5\lib\idea_rt.jar=64660:C:\Program Files\JetBrains\IntelliJ IDEA
>> Community Edition 2017.2.5\bin, -Dfile.encoding=UTF-8]
>> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] System
>> cache's DataRegion size is configured to 40 MB. Use
>> DataStorageConfiguration.systemCacheMemorySize property to change the
>> setting.
>> 2017-12-01T17:06:49,427][INFO ][main][IgniteKernal%verboseLogGrid]
>> Configured caches [in 'sysMemPlc' dataRegion: ['ignite-sys-cache']]
>> 2017-12-01T17:06:49,430][WARN ][pub-#19%verboseLogGrid%][GridDiagnostic]
>> This operating system has been tested less rigorously: Windows 10 10.0
>> amd64. Our team will appreciate the feedback if you experience any problems
>> running ignite in this environment.
>> 2017-12-01T17:06:49,436][INFO ][main][IgniteKernal%verboseLogGrid] 3-rd
>> party licenses can be found at: C:\incubator-ignite\libs\licenses
>> 
>> Thank you,
>> Alexey
>> 
>> From: Denis Magda
>> Sent: Tuesday, November 21, 2017 2:01 AM
>> To: dev@ignite.apache.org
>> Subject: Re: Ignite Logger & logging file config output
>> 
>> Good point. Could you create a ticket and probably contribute this
>> improvement?
>> 
>> —

Re: Documentation for GA Grid: GA library to Apache Ignite

2017-12-01 Thread Denis Magda

Akmal, yes, the updates need to be checked:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document 


An actual reiview though can take place before or after a doc goes online.


Turik,

You can edit the page directly. Once you log in under your account, click on 
your name to unveil a drop-down menu and select “Admin panel” from there. Then 
locate the GA page in the docs tree and edit it.

—
Denis

> On Dec 1, 2017, at 6:22 AM, Akmal Chaudhri  
> wrote:
> 
> Updates need to be checked and approved before going live?
> 
> On 1 December 2017 at 04:11, techbysample  wrote:
> 
>> Denis,
>> 
>> Thanks. In review, I noticed that  when I edit page:
>> 
>> "https://apacheignite.readme.io/v2.3/docs/genetic-algorithms;, my updates
>> do
>> not appear instantly.
>> 
>> Is this the correct behavior of ReadMe?
>> 
>> I assumed that updates were 'instant' akin to blogging..
>> 
>> Please advise.
>> 
>> Regards,
>> Turik
>> 
>> 
>> 
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>

Re: ci.ignite.apache: Run all for patch (jira number)

2017-12-01 Thread Denis Magda

It’s possible but requires you to create a branch and pass its name into 
TeamCity:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-2.CreateaPatch-file
 


However, this approach works only for Ignite committers who have enough 
permissions for branches creation.

Plus, it’s easier for a reviewer to check the changes via pull-requests and 
leave comments there. 

—
Denis

> On Nov 30, 2017, at 11:28 PM, Cergey  wrote:
> 
> But I want to run the tests against the patch in jira (it is kinda easier to 
> make changes in the patch). Is that feasible ?
> 
> -Original Message-
> From: Denis Magda [mailto:dma...@apache.org] 
> Sent: Friday, December 1, 2017 4:53 AM
> To: dev@ignite.apache.org
> Subject: Re: ci.ignite.apache: Run all for patch (jira number)
> 
> Cergey,
> 
> You need to run the tests agains the pull-request. In your case it should be 
> this one - pull/2970/merge
> 
> —
> Denis
> 
>> On Nov 30, 2017, at 12:36 PM, Cergey  wrote:
>> 
>> Probably, I missed something in the patch 
>> (https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not (and 
>> did not) start automatically. What may be wrong ? 
>> 
>> -Original Message-
>> From: Cergey [mailto:cossa...@mail.ru.INVALID] 
>> Sent: Friday, December 1, 2017 12:31 AM
>> To: dev@ignite.apache.org
>> Subject: ci.ignite.apache: Run all for patch (jira number)
>> 
>> Hi, igniters,
>> 
>> When trying to run "Run all for patch" build with parameter "jira number" 
>> (existing, e.g. IGNITE-6745 or random), build fails 
>> (https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAllTestBuilds)
>>   with exception: java.net.ConnectException: Connection timed out. Is this 
>> functionality not supported or I incorrectly set the jira number ?
>> 
>> 
> 
>

[GitHub] ignite pull request #3128: IGNITE-7091: PDS Compatibilty: Assertion error in...

2017-12-01 Thread dspavlov

GitHub user dspavlov opened a pull request:

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

IGNITE-7091: PDS Compatibilty: Assertion error in case serializer V1

Flaky failure fix

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

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

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

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


commit bd9e4c8893e0b1f9452b7cd222f6aeed3a9aec6c
Author: dpavlov 
Date:   2017-12-01T14:42:12Z

GG-13117: PDS compatibility test flaky failure: debug code added

commit b6d4753ce4ab5866f888c183b89a8708abcbe52a
Author: dpavlov 
Date:   2017-12-01T15:59:19Z

GG-13117: PDS compatibility test flaky failure: debug code added

commit a6454caa288dcc603a6b55774a257ef130c24491
Author: dpavlov 
Date:   2017-12-01T16:47:45Z

GG-13117: PDS compatibility test flaky failure: debug code added

commit f728b33967d9829719d9aa2b964cb3bf1dfe65bd
Author: dpavlov 
Date:   2017-12-01T17:09:08Z

GG-13117: PDS compatibility test flaky failure: fix

commit 17d967fded2e54164d8e9f753c61fa1ada97edc0
Author: dpavlov 
Date:   2017-12-01T17:13:52Z

GG-13117: PDS compatibility test flaky failure: fix

commit 11c9b6e3f55b769ec86b2c810120401a419d7e81
Author: dpavlov 
Date:   2017-12-01T17:35:23Z

GG-13117: PDS compatibility test flaky failure: debug code return




---

[jira] [Created] (IGNITE-7091) PDS Compatibilty: Assertion error in case serializer V1 is found and there is no next segment to read in WAL iterator

2017-12-01 Thread Dmitriy Pavlov (JIRA)

Dmitriy Pavlov created IGNITE-7091:
--

 Summary: PDS Compatibilty: Assertion error in case serializer V1 
is found and there is no next segment to read in WAL iterator
 Key: IGNITE-7091
 URL: https://issues.apache.org/jira/browse/IGNITE-7091
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Affects Versions: 2.4
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
Priority: Critical
 Fix For: 2.4


In case of absence of next segment for WAL iterator and current segment having 
V1 version there is flaky failure of PDS compatibilty tests
{noformat}
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.releaseWorkSegment(FileWriteAheadLogManager.java:1424)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.access$8400(FileWriteAheadLogManager.java:1173)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.releaseWorkSegment(FileWriteAheadLogManager.java:3104)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.advanceSegment(FileWriteAheadLogManager.java:3084)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:168)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.(FileWriteAheadLogManager.java:2949)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.(FileWriteAheadLogManager.java:2883)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.replay(FileWriteAheadLogManager.java:646)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:1980)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1344)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1139)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1054)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:658)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2284)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
{noformat}



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

[GitHub] ignite pull request #3127: Ignite-6339-mmap

2017-12-01 Thread agura

GitHub user agura opened a pull request:

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

Ignite-6339-mmap



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

$ git pull https://github.com/agura/incubator-ignite ignite-6339-mmap

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

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


commit 6bf7a6071806c32e0c4d182ce07a4f49898ace8b
Author: Andrey Gura 
Date:   2017-09-13T12:36:26Z

ignite-6339 Segmented ring buffer implemented instead of WAL records chain

commit 6f1d79f05e83ba7f81b5344c61e13b90fade7f1f
Author: Andrey Gura 
Date:   2017-12-01T17:30:24Z

ignite-6339 mmap WIP




---

[jira] [Created] (IGNITE-7090) Semaphore Stuck when no acquirers to assign permit

2017-12-01 Thread Tim Onyschak (JIRA)

Tim Onyschak created IGNITE-7090:


 Summary: Semaphore Stuck when no acquirers to assign permit
 Key: IGNITE-7090
 URL: https://issues.apache.org/jira/browse/IGNITE-7090
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.1, 2.4
Reporter: Tim Onyschak


If no acquirers are available to take permit of semaphore, the permit never 
gets release and any further acquirerers will wait forever. 





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

[GitHub] ignite pull request #3126: Ignite-2.1.8.b2

2017-12-01 Thread AMashenkov

GitHub user AMashenkov opened a pull request:

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

Ignite-2.1.8.b2



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

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

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

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


commit 96cdf426bf53f777a1214a6b618f8304d86d031a
Author: Ilya Kasnacheev 
Date:   2017-09-04T10:56:25Z

IGNITE-6139: JDBC thick driver: fixed driver versions. This closes #2552.

commit 6e608b881f05ab3503304ab73506163c840dc55d
Author: Igor Sapego 
Date:   2017-09-04T12:34:59Z

IGNITE-6188: ODBC: Fix for SQLFreeStmt(SQL_CLOSE).

(cherry picked from commit dc6b73b)

commit 7d0a7cc89c6e2920d3cc8f4e219aa980e59b071f
Author: Igor Sapego 
Date:   2017-09-04T13:20:20Z

IGNITE-3987: ODBC: Improved error output when query parsing failed.

(cherry picked from commit 29ce1fa)

commit a5f5a9932f598062e45f903c2f170301157ac00a
Author: Alexey Kukushkin 
Date:   2017-08-31T14:44:11Z

ignite-5966 IgniteCache#get() fails with "Requesting mapping from grid 
failed" when deserialising binary object loaded from CacheJdbcPojoStoreFactory

commit 5bb79244a3049efa2a455f8e0eb8b76fb916ce02
Author: Igor Seliverstov 
Date:   2017-09-01T09:56:56Z

IGNITE-6182 Change default max memory size from 80% to 20%

commit 1f6102f75f759fed525e62bb9781f85404a68c9b
Author: devozerov 
Date:   2017-09-04T14:41:30Z

IGNITE-6182: Improved message.

commit 78a7cdb0196ecfe6c11943f5150630897ccc4d6c
Author: devozerov 
Date:   2017-09-04T14:59:44Z

Merge remote-tracking branch 'upstream/ignite-2.1.5' into ignite-2.1.5

commit dd3c7198861d3f7079a00fcb011bbe5e587eb972
Author: Ilya Lantukh 
Date:   2017-09-01T11:25:34Z

ignite-5999 : Fixed calculation of moving partitions count.

commit 790512da417bfcc01457d380be47c36bd4852c97
Author: Denis Mekhanikov 
Date:   2017-08-31T07:32:25Z

ignite-6214 resolve problem with concurrent metadata updates

commit 9112c9bdba233de5e350e06ac9df8b270870c47d
Author: Pavel Tupitsyn 
Date:   2017-09-05T07:39:32Z

IGNITE-6255 .NET: Fix TestAffinityCall to take late affinity assignment 
into account

This closes #2589

commit 21220f245464a73e2311d79e25f1dedce5ad2dce
Author: Igor Sapego 
Date:   2017-09-05T14:20:51Z

IGNITE-6119: Added 'lazy' flag to ODBC driver.

(cherry picked from commit d6cbc50)

commit 2e8a7f492685ebba6e66c98bb4d3b6cd1a4b9c36
Author: tledkov-gridgain 
Date:   2017-09-05T15:12:53Z

IGNITE-5344: JDBC thin driver: support Statement.closeOnCompletion. This 
closes #2131.

commit 2e053d85e20b338e259e60367e4f21786df29b84
Author: vk 
Date:   2017-09-06T07:41:16Z

IGNITE-6179: Improved reliability of 
DynamicIndexAbstractConcurrentSelfTest.testClientReconnectWithCacheRestart. 
This closes #2596.

commit f3707d0db44965f453d2d5668f8a956e9ed89de1
Author: Igor Sapego 
Date:   2017-09-06T10:42:04Z

IGNITE-6119: Fixes for style and DSN.

(cherry picked from commit 6c9bb89)

commit 9eabbe915b8c465033f047152fdcacd2ff41f400
Author: Ilya Lantukh 
Date:   2017-09-04T10:21:06Z

ignite-6254 : Fixed assertions for req.txState().

commit f34b5547e536d84133a1a242aaf6a369e61a4b59
Author: Alexander Belyak 
Date:   2017-09-06T14:07:33Z

ignite-5061: move rebalance enabled methods to 
GridCacheSharedContext

commit b5897d4dca6cca69f841321004550f4e43ecb66a
Author: devozerov 
Date:   2017-09-06T14:34:11Z

IGNITE-5339: JDBC thin driver: improved compliance. This closes #2112.

commit 9b5c9af084fa05dc1a5d5ab6db60eb7870647b15
Author: Alexander Paschenko 
Date:   2017-09-06T15:18:23Z

IGNITE-5572: SQL: ALTER TABLE ADD COLUMN support. This closes #2344.

commit 19e204250b05f76116c59981003bd1740a8efacd
Author: tledkov-gridgain 
Date:   2017-09-06T15:42:22Z

IGNITE-6130 JDBC thin driver: implemented type conversions. This closes 
#2510.

commit 25898aa06e161940a5b8267cc43e78e89dd1d8ef
Author: Evgenii Zhuravlev 
Date:   2017-09-07T07:17:27Z

Merge remote-tracking branch 'remotes/origin/ignite-2.1.4-p1' into 
ignite-2.1.5

commit d6fb2bf5e5f6bd978ec376c03de0346eaaff1212
Author: Vasiliy Sisko 
Date:   2017-08-22T10:51:55Z

IGNITE-6120 Lazy query execution from Web console.
(cherry picked from commit fea96f7)

[GitHub] ignite pull request #3125: IGNITE-6338 .NET: Thin client: LINQ

2017-12-01 Thread ptupitsyn

GitHub user ptupitsyn opened a pull request:

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

IGNITE-6338 .NET: Thin client: LINQ



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

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

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

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


commit 5b842cbdf8727af44cc155f6e4de962b04b4d92e
Author: Pavel Tupitsyn 
Date:   2017-12-01T11:59:54Z

IGNITE-6338 .NET: Thin client: LINQ

commit fb52a56e019cd2df8b5a81e0d7917b5402d280ef
Author: Pavel Tupitsyn 
Date:   2017-12-01T12:06:44Z

wip extension methods

commit 4e12092ae59f9e1a673b4ae047a711dd5b309c6e
Author: Pavel Tupitsyn 
Date:   2017-12-01T12:47:17Z

Deprecate ICacheQueryable

commit 0823f584ee5e9768ea47fa8e23586e34103d3d4c
Author: Pavel Tupitsyn 
Date:   2017-12-01T12:54:15Z

Refactor ICacheInternal usage

commit 823164f79422c0c0a1535fa86c925b3f27358d79
Author: Pavel Tupitsyn 
Date:   2017-12-01T13:00:33Z

Fix warnings

commit 682d945d0e1c480b5cbd02a940c2f95fd0117324
Author: Pavel Tupitsyn 
Date:   2017-12-01T13:04:07Z

wip tests

commit 9ee02bea17c8c44eaa9d8a3872d1ebadae92c03a
Author: Pavel Tupitsyn 
Date:   2017-12-01T13:07:08Z

adding thin client linq tests

commit 36ae8655f164d5616caded5f9043a7ec7376b605
Author: Pavel Tupitsyn 
Date:   2017-12-01T13:08:50Z

SqlQueryTestBase

commit cf01a86e0e2eb9dab0389afaff9c8958ade823cd
Author: Pavel Tupitsyn 
Date:   2017-12-01T13:17:19Z

Adding tests

commit 210be35fe23470c0ac36412495dbce7de4e01b75
Author: Pavel Tupitsyn 
Date:   2017-12-01T13:19:03Z

Add tests to core project

commit 707e8145d7b5ffacf18718f048816bc93902f221
Author: Pavel Tupitsyn 
Date:   2017-12-01T14:05:25Z

Generic fields qury implemented

commit e0d6e85612637b696137bdd0957d958d1cd14dd4
Author: Pavel Tupitsyn 
Date:   2017-12-01T14:11:38Z

Simple test passed

commit b85be17a17ffa8d011c508265d3cdf88667019d2
Author: Pavel Tupitsyn 
Date:   2017-12-01T14:22:58Z

wip

commit f088ccebc03f0ebed2025bd0b08e71bf098fd71e
Author: Pavel Tupitsyn 
Date:   2017-12-01T14:31:26Z

Add join test

commit 0664285392a1fad5e520248c499709859a532454
Author: Pavel Tupitsyn 
Date:   2017-12-01T14:32:45Z

Cleanup

commit 9b561432221f45d495236411c7d246832a6aaa54
Author: Pavel Tupitsyn 
Date:   2017-12-01T14:37:54Z

wip tests

commit 9674ec1fd1ea807b893863685eb03c0acde913af
Author: Pavel Tupitsyn 
Date:   2017-12-01T14:41:50Z

fix linux tests build




---

[GitHub] ignite pull request #3124: IGNITE-6425: Races during transaction finalizatio...

2017-12-01 Thread AMashenkov

GitHub user AMashenkov opened a pull request:

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

IGNITE-6425: Races during transaction finalization.



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

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

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

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


commit bd2607a6a4d12ae5912e2fb1a8a9473197975ea6
Author: Eduard Shangareev 
Date:   2017-09-11T15:07:13Z

IGNITE-6425 Test added.

commit c646ddec07c04e5f55d2340f328061e6e5678cd5
Author: Eduard Shangareev 
Date:   2017-09-11T15:07:13Z

IGNITE-6342 Exchange is hanging on eviction
-race in transaction failing

(cherry picked from commit f548fb7)




---

Are there any access control for ignite rest api

2017-12-01 Thread kcmvp

Hi All,

Are there any access control fro Ignite Access Control? For my case I just
want get related rest api can be accessed ?
Of course it's better to have fine control



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

RE: Does the Ignite C# client support distributed queues?

2017-12-01 Thread Alexey Popov

Hi Raymond,

You are right, distributed queues require changes at Ignite core. 
https://issues.apache.org/jira/browse/IGNITE-2701
It was created almost 1 year ago. Please vote for this feature.
As far as I know there is no plan/schedule for it. 

Thank you,
Alexey

From: Raymond Wilson
Sent: Friday, December 1, 2017 5:58 AM
To: u...@ignite.apache.org
Cc: dev@ignite.apache.org
Subject: RE: Does the Ignite C# client support distributed queues?

Looking at it I see it's blocked by 2701 (which has additional
dependencies, all of which say they are blocked by 2701).

I understand there is an intention to bring the C# client up to par with
the Java client. Is there a ticket/schedule yet for this?

Raymond.

-Original Message-
From: vkulichenko [mailto:valentin.kuliche...@gmail.com]
Sent: Friday, December 1, 2017 1:30 PM
To: u...@ignite.apache.org
Subject: RE: Does the Ignite C# client support distributed queues?

Oops, I read wrong! This is not supported. There is a ticket, but it
doesn't seem to be active at the moment:
https://issues.apache.org/jira/browse/IGNITE-1417

-Val



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Internal problems requiring graceful node shutdown, reboot, etc.

2017-12-01 Thread Anton Vinogradov

Dmitry,

Seems, we found that it's impossible to specify one action for all cases,
but it's a good idea to allow user to decide what to do.
We should make something like

interface IgniteFailureHandler {
   IgniteFailureAction onFailure(IgniteFailureCause cause);
}

public enum IgniteFailureAction {
RESTART_JVM,
STOP,
NOOP;
}

and ability to set it to IgniteConfiguration.
Also, we should provide default implementation of IgniteFailureHandler which
should be enabled by default and can be replaced by user's code.

On Fri, Dec 1, 2017 at 4:27 PM, Vladimir Ozerov 
wrote:

> HI Dmitry,
>
> I do not think it is good idea to mix failures of different threads into a
> single event type.
> - Practice shows that the most common source of problem is exchange thread
> - if disco worker has died, not will be excluded from topology safely
> - "nio-acceptor" can be spawn from multiple places where GridNioServer is
> started, not all of them are ciritical
> - "grid-nio-worker-tcp-comm" is internal thread which doesn't do any
> complex processing, so risk of it's crash is minimal
>
> We could track most of them, but death of different threads may result in
> different actions from user side. So I propose to start with exchange
> thread only for now.
>
> Another important point, is that FailureProcessingPolicy should get enough
> information on what happened in order to decide how to react. E.g., as I
> explained earlier, IgniteOutOfMemoryException *is not critical error*.
> Nasty, but not deadly. And node should not be stopped blindly in response
> to this event.
>
> Vladimir.
>
>
> On Fri, Dec 1, 2017 at 3:50 AM, Denis Magda  wrote:
>
> > Hi Dmitriy,
> >
> > I’m totally for the FailureProcessingPolicy addition to
> > IgniteConfiguration.
> >
> > Apart of this, may I ask you to create corresponding documentation
> tickets
> > for 2.4 release and “documentation” component? Only for the improvements
> > that are getting into the next release. Basically you can aggregate them
> if
> > it helps. Feel free to assign the ticket on me right away.
> >
> > —
> > Denis
> >
> > > On Nov 30, 2017, at 10:31 AM, Дмитрий Сорокин <
> sbt.sorokin@gmail.com>
> > wrote:
> > >
> > > Hi, Igniters!
> > >
> > > We have a set of internal problems, which required graceful node
> > shutdown,
> > > or other reaction configured (See discussion thread
> > > http://apache-ignite-developers.2346864.n4.nabble.
> > com/Ignite-Enhancement-Proposal-7-Internal-problems-
> detection-td24460.html
> > > ):
> > > - IgniteOutOfMemoryException -
> > > https://issues.apache.org/jira/browse/IGNITE-6892
> > > - Persistence errors - https://issues.apache.org/
> jira/browse/IGNITE-6891
> > > - ExchangeWorker exits with error -
> > > https://issues.apache.org/jira/browse/IGNITE-6890
> > >
> > > First, I propose reconsider 3rd problem as "System worker exit while
> node
> > > still running (node stopping process has not been started)", because we
> > > have at least 5 worker classes, which running is critical for node
> > working.
> > >
> > > These workers are:
> > > - partition-exchanger (ExchangeWorker)
> > > - disco-event-worker
> > > - nio-acceptor
> > > - grid-nio-worker-tcp-comm-*
> > > - grid-timeout-worker
> > >
> > > Second, I propose to use FailureProcessingPolicy (already implemented
> in
> > > scope of task IGNITE-6890) for reaction definition on 1st and 2nd
> > detected
> > > problems too. This policy can be configured similar to
> SegmentationPolicy
> > > in IgniteConfiguration.
> > >
> > > Opinions?
> >
> >
>

[jira] [Created] (IGNITE-7089) .NET: Thin client: LINQPad example

2017-12-01 Thread Pavel Tupitsyn (JIRA)

Pavel Tupitsyn created IGNITE-7089:
--

 Summary: .NET: Thin client: LINQPad example
 Key: IGNITE-7089
 URL: https://issues.apache.org/jira/browse/IGNITE-7089
 Project: Ignite
  Issue Type: Improvement
  Components: platforms, thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Add thin client example to LINQPad: "cache explorer".

Connect to a local node with thin client, show all caches and data in them.
Use binary mode so that any data can be displayed.



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

RE: Ignite Logger & logging file config output

2017-12-01 Thread Alexey Popov

Yes, it is implemented for all Ignite loggers. 
However, some loggers (Slf4jLogger) does not have logging file configuration, 
so they show less details.

Thank you,
Alexey

From: Nikolai Tikhonov
Sent: Friday, December 1, 2017 5:21 PM
To: dev@ignite.apache.org
Subject: Re: Ignite Logger & logging file config output

Alexey,

Looks cool and helpful! I understand correctly that improvement is
implemented for all type of loggers which Ignite supports?

On Fri, Dec 1, 2017 at 5:18 PM, Alexey Popov  wrote:

> Hi Denis,
>
> https://issues.apache.org/jira/browse/IGNITE-6971
>
> Sample quite=true output:
>
> [17:16:41]__  
> [17:16:41]   /  _/ ___/ |/ /  _/_  __/ __/
> [17:16:41]  _/ // (7 7// /  / / / _/
> [17:16:41] /___/\___/_/|_/___/ /_/ /___/
> [17:16:41]
> [17:16:41] ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
> [17:16:41] 2017 Copyright(C) Apache Software Foundation
> [17:16:41]
> [17:16:41] Ignite documentation: http://ignite.apache.org
> [17:16:41]
> [17:16:41] Quiet mode.
> [17:16:41]   ^-- Logging to file 'C:\incubator-ignite\work\log\
> ignite-7317b109.log'
> [17:16:41]   ^-- Logging by 'Log4JLogger [quiet=true,
> config=/C:/incubator-ignite/config/ignite-log4j.xml]'
> [17:16:41]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
> or "-v" to ignite.{sh|bat}
> [17:16:41]
> [17:16:41] OS: Windows 10 10.0 amd64
> [17:16:41] VM information: Java(TM) SE Runtime Environment 1.8.0_141-b15
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
> [17:16:41] Initial heap size is 254MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [17:16:41] Configured plugins:
> [17:16:41]   ^-- None
> [17:16:41]
>
> Sample verbose output:
>
> >>>__  
> >>>   /  _/ ___/ |/ /  _/_  __/ __/
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2017 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
>
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Config
> URL: n/a
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Daemon
> mode: off
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] OS:
> Windows 10 10.0 amd64
> 2017-12-01T17:06:49,404][INFO ][main][IgniteKernal%verboseLogGrid] OS
> user: gridgain
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] PID:
> 5984
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid]
> Language runtime: Java Platform API Specification ver. 1.8
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] VM
> information: Java(TM) SE Runtime Environment 1.8.0_141-b15 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
> 2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] VM
> total memory: 3.5GB
> 2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] Remote
> Management [restart: off, REST: off, JMX (remote: off)]
> 2017-12-01T17:06:49,416][INFO ][main][IgniteKernal%verboseLogGrid]
> Logger: Log4J2Logger [quiet=false, config=C:\incubator-ignite\
> modules\core\src\test\config\log4j2-verbose-test.xml]
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid]
> IGNITE_HOME=C:\incubator-ignite
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] VM
> arguments: [-ea, -Didea.test.cyclic.buffer.size=1048576,
> -javaagent:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
> 2017.2.5\lib\idea_rt.jar=64660:C:\Program Files\JetBrains\IntelliJ IDEA
> Community Edition 2017.2.5\bin, -Dfile.encoding=UTF-8]
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] System
> cache's DataRegion size is configured to 40 MB. Use
> DataStorageConfiguration.systemCacheMemorySize property to change the
> setting.
> 2017-12-01T17:06:49,427][INFO ][main][IgniteKernal%verboseLogGrid]
> Configured caches [in 'sysMemPlc' dataRegion: ['ignite-sys-cache']]
> 2017-12-01T17:06:49,430][WARN ][pub-#19%verboseLogGrid%][GridDiagnostic]
> This operating system has been tested less rigorously: Windows 10 10.0
> amd64. Our team will appreciate the feedback if you experience any problems
> running ignite in this environment.
> 2017-12-01T17:06:49,436][INFO ][main][IgniteKernal%verboseLogGrid] 3-rd
> party licenses can be found at: C:\incubator-ignite\libs\licenses
>
> Thank you,
> Alexey
>
> From: Denis Magda
> Sent: Tuesday, November 21, 2017 2:01 AM
> To: dev@ignite.apache.org
> Subject: Re: Ignite Logger & logging file config output
>
> Good point. Could you create a ticket and probably contribute this
> improvement?
>
> —
> Denis
>
> > On Nov 20, 2017, at 3:12 AM, Alexey Popov  wrote:
> >
> > Hi Igniters,
> >
> > Could you please advise why Ignite does not indicate
> > 1) the logger type it uses
> > 2) the logger configuration file (name) it applies
> > during startup?
> >
> > Can we add such

[GitHub] ignite pull request #3123: IGNITE-6868 nodeId type fixed, unused methods rem...

2017-12-01 Thread alex-plekhanov

GitHub user alex-plekhanov opened a pull request:

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

IGNITE-6868 nodeId type fixed, unused methods removed



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

$ git pull https://github.com/alex-plekhanov/ignite ignite-6868-fix

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

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


commit 94237fe576dcc4ab502f98c6690caafebda9ab5d
Author: Aleksey Plekhanov 
Date:   2017-12-01T14:22:01Z

IGNITE-6868 nodeId type fixed, unused methods removed




---

Re: Documentation for GA Grid: GA library to Apache Ignite

2017-12-01 Thread Akmal Chaudhri

Updates need to be checked and approved before going live?

On 1 December 2017 at 04:11, techbysample  wrote:

> Denis,
>
> Thanks. In review, I noticed that  when I edit page:
>
> "https://apacheignite.readme.io/v2.3/docs/genetic-algorithms;, my updates
> do
> not appear instantly.
>
> Is this the correct behavior of ReadMe?
>
> I assumed that updates were 'instant' akin to blogging..
>
> Please advise.
>
> Regards,
> Turik
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: Ignite Logger & logging file config output

2017-12-01 Thread Nikolai Tikhonov

Alexey,

Looks cool and helpful! I understand correctly that improvement is
implemented for all type of loggers which Ignite supports?

On Fri, Dec 1, 2017 at 5:18 PM, Alexey Popov  wrote:

> Hi Denis,
>
> https://issues.apache.org/jira/browse/IGNITE-6971
>
> Sample quite=true output:
>
> [17:16:41]__  
> [17:16:41]   /  _/ ___/ |/ /  _/_  __/ __/
> [17:16:41]  _/ // (7 7// /  / / / _/
> [17:16:41] /___/\___/_/|_/___/ /_/ /___/
> [17:16:41]
> [17:16:41] ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
> [17:16:41] 2017 Copyright(C) Apache Software Foundation
> [17:16:41]
> [17:16:41] Ignite documentation: http://ignite.apache.org
> [17:16:41]
> [17:16:41] Quiet mode.
> [17:16:41]   ^-- Logging to file 'C:\incubator-ignite\work\log\
> ignite-7317b109.log'
> [17:16:41]   ^-- Logging by 'Log4JLogger [quiet=true,
> config=/C:/incubator-ignite/config/ignite-log4j.xml]'
> [17:16:41]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
> or "-v" to ignite.{sh|bat}
> [17:16:41]
> [17:16:41] OS: Windows 10 10.0 amd64
> [17:16:41] VM information: Java(TM) SE Runtime Environment 1.8.0_141-b15
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
> [17:16:41] Initial heap size is 254MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [17:16:41] Configured plugins:
> [17:16:41]   ^-- None
> [17:16:41]
>
> Sample verbose output:
>
> >>>__  
> >>>   /  _/ ___/ |/ /  _/_  __/ __/
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2017 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
>
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Config
> URL: n/a
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Daemon
> mode: off
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] OS:
> Windows 10 10.0 amd64
> 2017-12-01T17:06:49,404][INFO ][main][IgniteKernal%verboseLogGrid] OS
> user: gridgain
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] PID:
> 5984
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid]
> Language runtime: Java Platform API Specification ver. 1.8
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] VM
> information: Java(TM) SE Runtime Environment 1.8.0_141-b15 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
> 2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] VM
> total memory: 3.5GB
> 2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] Remote
> Management [restart: off, REST: off, JMX (remote: off)]
> 2017-12-01T17:06:49,416][INFO ][main][IgniteKernal%verboseLogGrid]
> Logger: Log4J2Logger [quiet=false, config=C:\incubator-ignite\
> modules\core\src\test\config\log4j2-verbose-test.xml]
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid]
> IGNITE_HOME=C:\incubator-ignite
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] VM
> arguments: [-ea, -Didea.test.cyclic.buffer.size=1048576,
> -javaagent:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
> 2017.2.5\lib\idea_rt.jar=64660:C:\Program Files\JetBrains\IntelliJ IDEA
> Community Edition 2017.2.5\bin, -Dfile.encoding=UTF-8]
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] System
> cache's DataRegion size is configured to 40 MB. Use
> DataStorageConfiguration.systemCacheMemorySize property to change the
> setting.
> 2017-12-01T17:06:49,427][INFO ][main][IgniteKernal%verboseLogGrid]
> Configured caches [in 'sysMemPlc' dataRegion: ['ignite-sys-cache']]
> 2017-12-01T17:06:49,430][WARN ][pub-#19%verboseLogGrid%][GridDiagnostic]
> This operating system has been tested less rigorously: Windows 10 10.0
> amd64. Our team will appreciate the feedback if you experience any problems
> running ignite in this environment.
> 2017-12-01T17:06:49,436][INFO ][main][IgniteKernal%verboseLogGrid] 3-rd
> party licenses can be found at: C:\incubator-ignite\libs\licenses
>
> Thank you,
> Alexey
>
> From: Denis Magda
> Sent: Tuesday, November 21, 2017 2:01 AM
> To: dev@ignite.apache.org
> Subject: Re: Ignite Logger & logging file config output
>
> Good point. Could you create a ticket and probably contribute this
> improvement?
>
> —
> Denis
>
> > On Nov 20, 2017, at 3:12 AM, Alexey Popov  wrote:
> >
> > Hi Igniters,
> >
> > Could you please advise why Ignite does not indicate
> > 1) the logger type it uses
> > 2) the logger configuration file (name) it applies
> > during startup?
> >
> > Can we add such output to IgniteLogger implementations?
> >
> > Thanks,
> > Alexey
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
>
>

RE: Ignite Logger & logging file config output

2017-12-01 Thread Alexey Popov

Hi Denis,

https://issues.apache.org/jira/browse/IGNITE-6971

Sample quite=true output:

[17:16:41]__   
[17:16:41]   /  _/ ___/ |/ /  _/_  __/ __/ 
[17:16:41]  _/ // (7 7// /  / / / _/   
[17:16:41] /___/\___/_/|_/___/ /_/ /___/  
[17:16:41] 
[17:16:41] ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
[17:16:41] 2017 Copyright(C) Apache Software Foundation
[17:16:41] 
[17:16:41] Ignite documentation: http://ignite.apache.org
[17:16:41] 
[17:16:41] Quiet mode.
[17:16:41]   ^-- Logging to file 
'C:\incubator-ignite\work\log\ignite-7317b109.log'
[17:16:41]   ^-- Logging by 'Log4JLogger [quiet=true, 
config=/C:/incubator-ignite/config/ignite-log4j.xml]'
[17:16:41]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[17:16:41] 
[17:16:41] OS: Windows 10 10.0 amd64
[17:16:41] VM information: Java(TM) SE Runtime Environment 1.8.0_141-b15 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
[17:16:41] Initial heap size is 254MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[17:16:41] Configured plugins:
[17:16:41]   ^-- None
[17:16:41]

Sample verbose output:

>>>__    
>>>   /  _/ ___/ |/ /  _/_  __/ __/  
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/   
>>> 
>>> ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
>>> 2017 Copyright(C) Apache Software Foundation
>>> 
>>> Ignite documentation: http://ignite.apache.org

2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Config URL: 
n/a
2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Daemon mode: 
off
2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] OS: Windows 
10 10.0 amd64
2017-12-01T17:06:49,404][INFO ][main][IgniteKernal%verboseLogGrid] OS user: 
gridgain
2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] PID: 5984
2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] Language 
runtime: Java Platform API Specification ver. 1.8
2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] VM 
information: Java(TM) SE Runtime Environment 1.8.0_141-b15 Oracle Corporation 
Java HotSpot(TM) 64-Bit Server VM 25.141-b15
2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] VM total 
memory: 3.5GB
2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] Remote 
Management [restart: off, REST: off, JMX (remote: off)]
2017-12-01T17:06:49,416][INFO ][main][IgniteKernal%verboseLogGrid] Logger: 
Log4J2Logger [quiet=false, 
config=C:\incubator-ignite\modules\core\src\test\config\log4j2-verbose-test.xml]
2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] 
IGNITE_HOME=C:\incubator-ignite
2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] VM 
arguments: [-ea, -Didea.test.cyclic.buffer.size=1048576, -javaagent:C:\Program 
Files\JetBrains\IntelliJ IDEA Community Edition 
2017.2.5\lib\idea_rt.jar=64660:C:\Program Files\JetBrains\IntelliJ IDEA 
Community Edition 2017.2.5\bin, -Dfile.encoding=UTF-8]
2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] System 
cache's DataRegion size is configured to 40 MB. Use 
DataStorageConfiguration.systemCacheMemorySize property to change the setting.
2017-12-01T17:06:49,427][INFO ][main][IgniteKernal%verboseLogGrid] Configured 
caches [in 'sysMemPlc' dataRegion: ['ignite-sys-cache']]
2017-12-01T17:06:49,430][WARN ][pub-#19%verboseLogGrid%][GridDiagnostic] This 
operating system has been tested less rigorously: Windows 10 10.0 amd64. Our 
team will appreciate the feedback if you experience any problems running ignite 
in this environment.
2017-12-01T17:06:49,436][INFO ][main][IgniteKernal%verboseLogGrid] 3-rd party 
licenses can be found at: C:\incubator-ignite\libs\licenses

Thank you,
Alexey

From: Denis Magda
Sent: Tuesday, November 21, 2017 2:01 AM
To: dev@ignite.apache.org
Subject: Re: Ignite Logger & logging file config output

Good point. Could you create a ticket and probably contribute this improvement?

—
Denis

> On Nov 20, 2017, at 3:12 AM, Alexey Popov  wrote:
> 
> Hi Igniters,
> 
> Could you please advise why Ignite does not indicate 
> 1) the logger type it uses
> 2) the logger configuration file (name) it applies
> during startup?
> 
> Can we add such output to IgniteLogger implementations?
> 
> Thanks,
> Alexey
> 
> 
> 
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Thin Client Protocol documentation

2017-12-01 Thread Pavel Tupitsyn

There are no legacy formats. JDBC and ODBC clients are not "legacy", quite
the opposite.

In future we may even want to combine JDBC Thin and general-purpose Thin
clients since they have a lot in common.
So let's keep the handshake format consistent across clients.

> exceptions for message formats
Handshake is an exception anyway, it does not have (or need) requestId, etc.

On Fri, Dec 1, 2017 at 1:38 PM, Alexey Popov  wrote:

> Pavel,
>
> I believe ClientListenerNioListener.onHandshake() could support more than
> one Handshake request format (be backward compatible), for instance, if we
> will have a new handshake code = 0xABCD that differs from 0x01 byte.
>
> It is a design vs architecture question.
>
> I can’t understand why the legacy Handshake format should be used for a
> new protocol. If this protocol is supposed to be public it should have no
> exceptions for message formats.
>
> Thank you,
> Alexey
>
> From: Pavel Tupitsyn
> Sent: Thursday, November 30, 2017 12:11 PM
> To: dev@ignite.apache.org
> Subject: Re: Thin Client Protocol documentation
>
> Hi Alexey,
>
> 1,2,3 are related only to handshake. All other operations are consistent.
>
> Handshake request format is dictated by existing client connector that is
> shared with ODBC and JDBC clients (see
> ClientListenerNioListener.onHandshake).
> so we can't add magic numbers or change operation code.
>
> But yes, we can add server version to the handshake response, and I think
> this makes sense.
>
> > 4. The same comments for success flag (1 byte) and status code (4 bytes)
> in responses. Let's leave only status code.
> We don't have a success flag in responses, there is just a 4-byte status
> code, 0 indicates success, everything else is an error.
>
> Thanks,
> Pavel
>
> On Thu, Nov 30, 2017 at 12:01 PM, Alexey Popov 
> wrote:
>
> > Hi Pavel,
> >
> > Let me add my 5 cents.
> >
> > 1. It would be great if both Handshake request & response have some
> > "magic" number (2 or 4 bytes) inside their msg body. That will simplify
> > handling situations when non-Ignite client connects to Ignite server and
> > vice versa.
> >
> > 2. It makes sense to add server version to successful Handshake response
> > as well. It will help to understand & debug possible backward
> compatibility
> > issues in the field by *.pcap logs analysis & etc.
> >
> > 3. Can we have a more strict header for all message types?
> > As far as I understand,
> > Handshake request has:
> > 1) length - 4 byte
> > 2) Handshake code - 1 byte
> > 3) body - (length - 1) bytes
> >
> > while OP_CACHE_GET request has:
> > 1) length - 4 byte
> > 2) OP_CACHE_GET code - 2 bytes
> > 3) request id - 4 bytes
> > 4) body - (length - 2 - 4) bytes
> >
> > Why some messages have Operation code with 1 byte while others - 2 bytes?
> > Why some requests/responses have request-id while others don't? Let's
> > simplify parser work )
> >
> > 4. The same comments for success flag (1 byte) and status code (4 bytes)
> > in responses. Let's leave only status code.
> >
> > Thank you,
> > Alexey
> >
> > From: Pavel Tupitsyn
> > Sent: Wednesday, November 22, 2017 4:04 PM
> > To: dev@ignite.apache.org
> > Subject: Thin Client Protocol documentation
> >
> > Igniters,
> >
> > I've put together a detailed description of our Thin Client protocol
> > in form of IEP on wiki:
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> > 9+Thin+Client+Protocol
> >
> >
> > To clarify:
> > - Protocol implementation is in master (see ClientMessageParser class)
> > - Protocol has not been released yet, so we are free to change anything
> > - Protocol is only used by .NET Thin Client for now, but is supposed to
> be
> > used from other languages by third party contributors
> > - More operations will be added in future, this is a first set of them,
> > cache-related
> >
> >
> > Please review the document and let me know your thoughts.
> > Is there anything missing or wrong?
> >
> > We should make sure that the foundation is solid and extensible.
> >
> >
> > Thanks,
> > Pavel
> >
> >
>
>

[jira] [Created] (IGNITE-7088) Wrong implementation of DIRECT comparator for ordering cache start operations

2017-12-01 Thread Evgenii Zhuravlev (JIRA)

Evgenii Zhuravlev created IGNITE-7088:
-

 Summary: Wrong implementation of DIRECT comparator for ordering 
cache start operations
 Key: IGNITE-7088
 URL: https://issues.apache.org/jira/browse/IGNITE-7088
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Evgenii Zhuravlev
Priority: Critical
 Fix For: 2.4



{code:java}
java.lang.IllegalArgumentException: Comparison method violates its general 
contract!
at java.util.TimSort.mergeHi(TimSort.java:899) ~[?:1.8.0_102]
at java.util.TimSort.mergeAt(TimSort.java:516) ~[?:1.8.0_102]
at java.util.TimSort.mergeForceCollapse(TimSort.java:457) ~[?:1.8.0_102]
at java.util.TimSort.sort(TimSort.java:254) ~[?:1.8.0_102]
at java.util.Arrays.sort(Arrays.java:1512) ~[?:1.8.0_102]
at java.util.ArrayList.sort(ArrayList.java:1454) ~[?:1.8.0_102]
at java.util.Collections.sort(Collections.java:175) ~[?:1.8.0_102]
at 
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.orderedCaches(ClusterCachesInfo.java:1616)
 ~[ignite-core-2.1.7.jar:2.1.7]
at 
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.cachesReceivedFromJoin(ClusterCachesInfo.java:839)
 ~[ignite-core-2.1.7.jar:2.1.7]
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startReceivedCaches(GridCacheProcessor.java:1709)
 ~[ignite-core-2.1.7.jar:2.1.7]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:606)
 [ignite-core-2.1.7.jar:2.1.7]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2278)
 [ignite-core-2.1.7.jar:2.1.7]
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
[ignite-core-2.1.7.jar:2.1.7]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]

{code}

When 2 not user cache will be compared using this comparator, this above 
exception will be thrown.

As a workaround can be used environment variable 
-Djava.util.Arrays.useLegacyMergeSort=true 



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

[GitHub] ignite pull request #3122: Ignite-2.4.1-p1

2017-12-01 Thread agoncharuk

GitHub user agoncharuk opened a pull request:

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

Ignite-2.4.1-p1



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

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

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

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


commit e7ca9b65a68de7752195c8f4d2b5180f3c77d19f
Author: Dmitriy Govorukhin 
Date:   2017-11-13T18:52:47Z

ignite-blt-merge -> ignite-2.4.1

commit cc8168fc184bb7f5e3cc3bbb0743397097f78bfb
Author: Dmitriy Govorukhin 
Date:   2017-11-13T19:13:01Z

merge ignite-pitr-rc1 -> ignite-2.4.1

commit 87e6d74cf6a251c7984f9e68c391f790feccc281
Author: Dmitriy Govorukhin 
Date:   2017-11-14T12:49:33Z

ignite-gg-12877 Compact consistent ID in WAL

commit 9f5a22711baea05bd37ab07c8f928a4837dd83a4
Author: Ilya Lantukh 
Date:   2017-11-14T14:12:28Z

Fixed javadoc.

commit d5af2d78dd8eef8eca8ac5391d31d8c779649bb0
Author: Alexey Kuznetsov 
Date:   2017-11-15T08:09:00Z

IGNITE-6913 Baseline: Added new options to controls.sh for baseline 
manipulations.

commit 713924ce865752b6e99b03bd624136541cea5f9f
Author: Sergey Chugunov 
Date:   2017-11-15T09:03:12Z

IGNITE-5850 failover tests for cache operations during BaselineTopology 
changes

commit b65fd134e748d496f732ec2aa0953a0531f544b8
Author: Ilya Lantukh 
Date:   2017-11-15T12:54:35Z

TX read logging if PITR is enabled.

commit 9b2a567c0e04dc33116b51f88bee75f76e9107d1
Author: Ilya Lantukh 
Date:   2017-11-15T13:45:16Z

TX read logging if PITR is enabled.

commit 993058ccf0b2b8d9e80750c3e45a9ffa31d85dfa
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:51:54Z

ignite-2.4.1 optimization for store full set node more compacted

commit 1eba521f608d39967aec376b397b7fc800234e54
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:52:22Z

Merge remote-tracking branch 'professional/ignite-2.4.1' into ignite-2.4.1

commit 564b3fd51f8a7d1d81cb6874df66d0270623049c
Author: Sergey Chugunov 
Date:   2017-11-15T14:00:51Z

IGNITE-5850 fixed issue with initialization of data regions on node 
activation, fixed issue with auto-activation when random node joins inactive 
cluster with existing BLT

commit c6d1fa4da7adfadc80abdc7eaf6452b86a4f6aa4
Author: Sergey Chugunov 
Date:   2017-11-15T16:23:08Z

IGNITE-5850 transitionResult is set earlier when request for changing 
BaselineTopology is sent

commit d65674363163e38a4c5fdd73d1c8d8e1c7610797
Author: Sergey Chugunov 
Date:   2017-11-16T11:59:07Z

IGNITE-5850 new failover tests for changing BaselineTopology up (new node 
added to topology)

commit 20552f3851fe8825191b144179be032965e0b5c6
Author: Sergey Chugunov 
Date:   2017-11-16T12:53:43Z

IGNITE-5850 improved error message when online node is removed from baseline

commit 108bbcae4505ac904a6db774643ad600bfb42c21
Author: Sergey Chugunov 
Date:   2017-11-16T13:45:52Z

IGNITE-5850 BaselineTopology should not change on cluster deactivation

commit deb641ad3bdbf260fa60ad6bf607629652e324bd
Author: Dmitriy Govorukhin 
Date:   2017-11-17T09:45:44Z

ignite-2.4.1 truncate wal and checkpoint history on move/delete snapshot

commit 3c8b06f3659af30d1fd148ccc0f40e216a56c998
Author: Alexey Goncharuk 
Date:   2017-11-17T12:48:12Z

IGNITE-6947 Abandon remap after single map if future is done (fixes NPE)

commit ba2047e5ae7d271a677e0c418375d82d78c4023e
Author: devozerov 
Date:   2017-11-14T12:26:31Z

IGNITE-6901: Fixed assertion during 
IgniteH2Indexing.rebuildIndexesFromHash. This closes #3027.

commit abfc0466d6d61d87255d0fe38cbdf11ad46d4f89
Author: Sergey Chugunov 
Date:   2017-11-17T13:40:57Z

IGNITE-5850 tests for queries in presence of BaselineTopology

commit f4eabaf2a905abacc4c60c01d3ca04f6ca9ec188
Author: Sergey Chugunov 
Date:   2017-11-17T17:23:02Z

IGNITE-5850 implementation for setBaselineTopology(long topVer) migrated 
from wc-251

commit 4edeccd3e0b671aa277f58995df9ff9935baa95a
Author: EdShangGG 
Date:   2017-11-17T18:21:17Z

GG-13074 Multiple snapshot test failures after baseline topology is 
introduced
-adding baseline test to suite
-fixing issues with baseline

commit edae228c8f55990c15ef3044be987dcb00d6c81a
Author: EdShangGG

Re: Internal problems requiring graceful node shutdown, reboot, etc.

2017-12-01 Thread Vladimir Ozerov

HI Dmitry,

I do not think it is good idea to mix failures of different threads into a
single event type.
- Practice shows that the most common source of problem is exchange thread
- if disco worker has died, not will be excluded from topology safely
- "nio-acceptor" can be spawn from multiple places where GridNioServer is
started, not all of them are ciritical
- "grid-nio-worker-tcp-comm" is internal thread which doesn't do any
complex processing, so risk of it's crash is minimal

We could track most of them, but death of different threads may result in
different actions from user side. So I propose to start with exchange
thread only for now.

Another important point, is that FailureProcessingPolicy should get enough
information on what happened in order to decide how to react. E.g., as I
explained earlier, IgniteOutOfMemoryException *is not critical error*.
Nasty, but not deadly. And node should not be stopped blindly in response
to this event.

Vladimir.


On Fri, Dec 1, 2017 at 3:50 AM, Denis Magda  wrote:

> Hi Dmitriy,
>
> I’m totally for the FailureProcessingPolicy addition to
> IgniteConfiguration.
>
> Apart of this, may I ask you to create corresponding documentation tickets
> for 2.4 release and “documentation” component? Only for the improvements
> that are getting into the next release. Basically you can aggregate them if
> it helps. Feel free to assign the ticket on me right away.
>
> —
> Denis
>
> > On Nov 30, 2017, at 10:31 AM, Дмитрий Сорокин 
> wrote:
> >
> > Hi, Igniters!
> >
> > We have a set of internal problems, which required graceful node
> shutdown,
> > or other reaction configured (See discussion thread
> > http://apache-ignite-developers.2346864.n4.nabble.
> com/Ignite-Enhancement-Proposal-7-Internal-problems-detection-td24460.html
> > ):
> > - IgniteOutOfMemoryException -
> > https://issues.apache.org/jira/browse/IGNITE-6892
> > - Persistence errors - https://issues.apache.org/jira/browse/IGNITE-6891
> > - ExchangeWorker exits with error -
> > https://issues.apache.org/jira/browse/IGNITE-6890
> >
> > First, I propose reconsider 3rd problem as "System worker exit while node
> > still running (node stopping process has not been started)", because we
> > have at least 5 worker classes, which running is critical for node
> working.
> >
> > These workers are:
> > - partition-exchanger (ExchangeWorker)
> > - disco-event-worker
> > - nio-acceptor
> > - grid-nio-worker-tcp-comm-*
> > - grid-timeout-worker
> >
> > Second, I propose to use FailureProcessingPolicy (already implemented in
> > scope of task IGNITE-6890) for reaction definition on 1st and 2nd
> detected
> > problems too. This policy can be configured similar to SegmentationPolicy
> > in IgniteConfiguration.
> >
> > Opinions?
>
>

[GitHub] ignite pull request #3121: IGNITE-7085 When PDS is enabled and IGNITE_BINARY...

2017-12-01 Thread asfedotov

GitHub user asfedotov opened a pull request:

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

IGNITE-7085 When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS is set 
and IgniteCache#put is called node hangs

CI

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

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

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

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


commit 9eabbe915b8c465033f047152fdcacd2ff41f400
Author: Ilya Lantukh 
Date:   2017-09-04T10:21:06Z

ignite-6254 : Fixed assertions for req.txState().

commit f34b5547e536d84133a1a242aaf6a369e61a4b59
Author: Alexander Belyak 
Date:   2017-09-06T14:07:33Z

ignite-5061: move rebalance enabled methods to 
GridCacheSharedContext

commit b5897d4dca6cca69f841321004550f4e43ecb66a
Author: devozerov 
Date:   2017-09-06T14:34:11Z

IGNITE-5339: JDBC thin driver: improved compliance. This closes #2112.

commit 9b5c9af084fa05dc1a5d5ab6db60eb7870647b15
Author: Alexander Paschenko 
Date:   2017-09-06T15:18:23Z

IGNITE-5572: SQL: ALTER TABLE ADD COLUMN support. This closes #2344.

commit 19e204250b05f76116c59981003bd1740a8efacd
Author: tledkov-gridgain 
Date:   2017-09-06T15:42:22Z

IGNITE-6130 JDBC thin driver: implemented type conversions. This closes 
#2510.

commit 25898aa06e161940a5b8267cc43e78e89dd1d8ef
Author: Evgenii Zhuravlev 
Date:   2017-09-07T07:17:27Z

Merge remote-tracking branch 'remotes/origin/ignite-2.1.4-p1' into 
ignite-2.1.5

commit d6fb2bf5e5f6bd978ec376c03de0346eaaff1212
Author: Vasiliy Sisko 
Date:   2017-08-22T10:51:55Z

IGNITE-6120 Lazy query execution from Web console.
(cherry picked from commit fea96f7)

commit 8a07888d7a01cc78b1cb3433af362c2b4912fda7
Author: Andrey Novikov 
Date:   2017-09-04T09:05:34Z

IGNITE-6120 Fixed lazy query since version for Web Console.
(cherry picked from commit c03549e)

commit 8173f31d621ec5cbc9e959dd02c1542397afbe1b
Author: devozerov 
Date:   2017-09-07T10:23:37Z

Better SQL tests placement.

commit 291faf9e8649a139805c755bd84b8ae008271cb1
Author: Ilya Kasnacheev 
Date:   2017-09-07T11:25:14Z

IGNITE-5855: SQL: fixed BigInteger data type handling, This closes #2512.

commit 9dba29f3bec638f1f906a515fd5c451eb2d37475
Author: Igor Sapego 
Date:   2017-09-06T14:46:56Z

IGNITE-6119: Compilation fix

(cherry picked from commit ffaf108)

commit c08b397b965ce070fa758ffe75b8c05098e96922
Author: devozerov 
Date:   2017-09-07T13:50:06Z

IGNITE-6297: JDBC: improved driver name. This closes #2613.

commit 9d0a707dd58b3b90eeb5bd2b5e48184326a10b3a
Author: Igor Sapego 
Date:   2017-09-07T14:47:14Z

IGNITE-6245: Implemented return of affected rows number.

(cherry picked from commit e881993)

commit d606870177536ce552558e2cd827d4e83318572b
Author: Igor Sapego 
Date:   2017-09-07T16:22:35Z

IGNITE-6282: CPP: Implemented lazy initialization of IgniteImpl members

(cherry picked from commit cf9e804)

commit f8ce1188f12d95038408fe4f476e295551aa802c
Author: Ivan Rakov 
Date:   2017-09-08T09:11:44Z

IGNITE-5884 Change default pageSize of page memory to 4KB

commit 27853baaecd090b737c7e3136ac61168ac364e67
Author: tledkov-gridgain 
Date:   2017-09-08T10:40:31Z

IGNITE-3558: Use default equals for GridJobWorker. This closes #1326.

commit 1921b59a0c4788a03c4be36f57a803c8008285cd
Author: devozerov 
Date:   2017-09-08T13:25:26Z

Increased available memory for DynamicIndexAbstractSelfTest.

commit afb039a1c1fc440425f9563df90224b72070dd69
Author: tledkov-gridgain 
Date:   2017-09-11T07:13:45Z

IGNITE-6288: SQL: fixed NPE in IgniteH2Indexing.bindPartitionInfoParameter. 
This closes #2617.

commit 49d8368f09cac37ad44fc3e36e84f65dbb83920a
Author: tledkov-gridgain 
Date:   2017-09-11T10:05:58Z

IGNITE-6291: JDBC thin driver: fixed borken handshake compatibility. This 
closes #2630.

commit 223b646f674177892deab7d1d55fe973fb162821
Author: sboikov 
Date:   2017-07-17T14:06:55Z

ignite-5763 Race in concurrent client cache start

(cherry picked from commit 644c9f3)

commit 9ad1613ea7e3fd9e50a00b70b1dc641eeba5b586
Author: Pavel Tupitsyn 
Date:   2017-09-06T13:54:25Z

IGNITE-6253 .NET: Use DocFX for API documentation

This closes #2588

commit

[jira] [Created] (IGNITE-7087) Ignite.destroyCache leave cache serialized config and prevent from repeatable cache creation.

2017-12-01 Thread Stanilovsky Evgeny (JIRA)

Stanilovsky Evgeny created IGNITE-7087:
--

 Summary: Ignite.destroyCache leave cache serialized config and 
prevent from repeatable cache creation.
 Key: IGNITE-7087
 URL: https://issues.apache.org/jira/browse/IGNITE-7087
 Project: Ignite
  Issue Type: Bug
  Components: cache, persistence
Affects Versions: 2.4
Reporter: Stanilovsky Evgeny


enable pds and run simple test.
{code}
public void testCreateDestroyCaches() throws Exception {
Ignite srv0 = startGrid(0);
srv0.active(true);
srv0.createCache(new CacheConfiguration("myCache"));
srv0.destroyCache("myCache");
stopAllGrids();
srv0 = startGrid(0);
srv0.active(true);
srv0.createCache(new CacheConfiguration("myCache"));
}
{code}


{code}
[ERROR][main][root] Test failed.
org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache 
with the same name is already started): myCache
{code}




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

[GitHub] ignite pull request #3120: IGNITE-6997 .NET: Thin client: Move ClientStatus ...

2017-12-01 Thread asfgit

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-7086) Backups are not updated when ReadFromBackup=true and ReadThrough happens.

2017-12-01 Thread Andrew Mashenkov (JIRA)

Andrew Mashenkov created IGNITE-7086:


 Summary: Backups are not updated when ReadFromBackup=true and 
ReadThrough happens.
 Key: IGNITE-7086
 URL: https://issues.apache.org/jira/browse/IGNITE-7086
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Andrew Mashenkov
 Fix For: 2.4


Ignite Replicated cache with CacheStore and Read-through=true and 
ReadFromBackup=true works in unexpected way from user perspective.

Get operation on backup will go to the primary node regardless of 
ReadFromBackup=true and Read-through=true when entry doesn't exists in local 
map.

So, Replicated cache works like a Partitioned with no backups.



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

Re: Time to drop Java 7?

2017-12-01 Thread Dmitry Pavlov

+1.

I am sincerely glad that we are ready to do this!

Is my understanding correct, that the level of the VM for the source code
will be 8?

пт, 1 дек. 2017 г. в 13:32, Andrey Gura :

> Good news for everyone )
>
> 30 нояб. 2017 г. 11:29 PM пользователь "Dmitriy Setrakyan" <
> dsetrak...@apache.org> написал:
>
> > +1
> >
> > On Thu, Nov 30, 2017 at 11:29 AM, Denis Magda  wrote:
> >
> > > Igniters,
> > >
> > > Considering that we’re going to support Java 9 in the next release and
> > > hitting several limitations caused by current Java 7 support (see spark
> > > issue [2] and account difficulties of Java 8 based ML development) I
> > would
> > > propose to discontinue Java 7.
> > >
> > > Let’s do both things in AI 2.4: Java 9 support and Java 7 removal.
> > >
> > > Share your thoughts on this?
> > >
> > > [1] http://apache-ignite-developers.2346864.n4.nabble.
> > > com/Java-9-support-td23612.html
> > > [2] http://apache-ignite-developers.2346864.n4.nabble.
> > > com/TC-issues-IGNITE-3084-Spark-Data-Frame-API-td24639.html <
> > > http://apache-ignite-developers.2346864.n4.nabble.
> > > com/TC-issues-IGNITE-3084-Spark-Data-Frame-API-td24639.html>
> > >
> > > —
> > > Denis
> >
>

Re: New Compatibility Testing Framework module in the project

2017-12-01 Thread Dmitry Pavlov

Hi Igniters,



recently I’ve made several updates in the framework.

- Now within the test, user can declare an extended classpath (e.g. use
ignite-indexing).

- Dumping classpath was added in case detached jvm node startup failed or
hangs. In second case stack trace is additionally dumped.

- Node join timeout was made configurable for long running post-startup
closures.



I also want to thank Eduard S.,  Alexey G. for review and Anton V. for
support.



Sincerely,

Dmitriy Pavlov


вт, 31 окт. 2017 г. в 10:51, Aleksei Zaitsev :

> Thanks for explanation
>
> 30.10.2017, 08:43, "Dmitry Pavlov" :
> > Hi Aleksei,
> >
> > Wiki in apache Ignite is used for design documents, Ignite Enhancement
> > Proposals (IEPs), introductory for ignite developers, etc, but not for
> > documentation.
> >
> > Readme.io is official Ignite documentation for ignite users.
> >
> > Recent created page describe how Ignite developer can test compatibility
> > (mostly if Persistent Store enabled) using testing framework
> > (GridAbstractTest/GridCommonAbstractTest). These classes are not used by
> > end users.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пн, 30 окт. 2017 г. в 10:06, Aleksei Zaitsev :
> >
> >>  Thanks, Dmitry, but why wiki and not readme.io[1]? It has a section
> "Test
> >>  and benchmarking", which suits well for such information.
> >>
> >>  I thought, that wiki is deprecated source of documentation. Correct me
> if
> >>  I am wrong.
> >>
> >>  [1] https://apacheignite.readme.io/docs
> >>
> >>  27.10.2017, 20:29, "Dmitry Pavlov" :
> >>  > Hi Vyacheslav , Igniters,
> >>  >
> >>  > I hope you don't mind I copied this description into wiki (new page):
> >>  >
> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Tests+How+To
> >>  >
> >>  > Hope this helps new community members to easily find the info.
> >>  >
> >>  > Sincerely,
> >>  > Dmitriy Pavlov
> >>  >
> >>  > вт, 17 окт. 2017 г. в 18:17, Vyacheslav Daradur  >:
> >>  >
> >>  >> Hi, Igniters!
> >>  >>
> >>  >> I would like to announce new Compatibility Testing Framework module
> in
> >>  >> the project.
> >>  >>
> >>  >> This module has been recently included in the project [1].
> >>  >>
> >>  >> Framework provides an opportunity to start working with Ignite
> >>  >> instances of previously released versions.
> >>  >>
> >>  >> The entire module is built on top of the Ignite Testing Framework,
> >>  >> especially on the MiltiJVM-mode classes. There is a class
> >>  >> IgniteCompatibilityAbstractTest that provides methods to start
> Ignite
> >>  >> nodes with versions which have been previously released in the Maven
> >>  >> repository in separate JVM and allows them to join topology.
> Framework
> >>  >> looking for artifacts of a specific version in the Maven local
> >>  >> repository, if they don’t exist there, they will be downloaded and
> >>  >> stored via Maven.
> >>  >>
> >>  >> The main implemented API:
> >>  >> startGrid(name, version, configurationClosure);
> >>  >> startGrid(name, version, configurationClosure, postStartupClosure);
> >>  >>
> >>  >> You can simply specify a version of Ignite, which you want to start,
> >>  >> define the configuration in the configurationClosure and set the
> >>  >> actions on the started node in the postStartupClosure. It’s very
> easy
> >>  >> to use it for writing unit tests, here is a simple example [2] which
> >>  >> demonstrates the main functional.
> >>  >>
> >>  >> I hope this framework helps us to make our project even better.
> >>  >>
> >>  >> I want to thank Anton Vinogradov for his help with API design and
> >>  >> Dmitriy Pavlov for sharing first-time user experience [3] [4].
> >>  >>
> >>  >> [1] https://issues.apache.org/jira/browse/IGNITE-5732 - Provide
> API to
> >>  >> test compatibility with old releases
> >>  >> [2]
> >>  >>
> >>
> https://github.com/apache/ignite/blob/master/modules/compatibility/src/test/java/org/apache/ignite/compatibility/persistence/DummyPersistenceCompatibilityTest.java
> >>  >> [3]
> >>  >>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/Binary-compatibility-of-persistent-storage-tp22419p22913.html
> >>  >> [4] https://issues.apache.org/jira/browse/IGNITE-6285 - Enhance
> >>  >> persistent store paths on start
> >>  >>
> >>  >> --
> >>  >> Best Regards, Vyacheslav D.
>

[jira] [Created] (IGNITE-7085) When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS property is set and IgniteCache#put is called a node hangs

2017-12-01 Thread Alexandr Fedotov (JIRA)

Alexandr Fedotov created IGNITE-7085:


 Summary: When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS 
property is set and IgniteCache#put is called a node hangs
 Key: IGNITE-7085
 URL: https://issues.apache.org/jira/browse/IGNITE-7085
 Project: Ignite
  Issue Type: Bug
  Components: binary
Affects Versions: 2.1
Reporter: Alexandr Fedotov
Assignee: Alexandr Fedotov
 Fix For: 2.4


When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS property is set and 
IgniteCache#put is called a node hangs.

The root cause is that when IGNITE_BINARY_SORT_OBJECT_FIELDS flag is enabled
BinaryMetadata#fields field is stored as TreeMap, but because 
BinaryUtils#WRAP_TREES is
set by default, that leads to BinaryMetadata#fields being wrapped into 
BinaryTreeMap.
When an update for BinaryMetadata is initiated it ends up in a discovery thread 
from where
a metadata update for BinaryTreeMap is initiated. Since this update should be 
processed by the same discovery thread, that results in a deadlock.




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

RE: Thin Client Protocol documentation

2017-12-01 Thread Alexey Popov

Pavel,

I believe ClientListenerNioListener.onHandshake() could support more than one 
Handshake request format (be backward compatible), for instance, if we will 
have a new handshake code = 0xABCD that differs from 0x01 byte. 

It is a design vs architecture question.

I can’t understand why the legacy Handshake format should be used for a new 
protocol. If this protocol is supposed to be public it should have no 
exceptions for message formats.

Thank you,
Alexey

From: Pavel Tupitsyn
Sent: Thursday, November 30, 2017 12:11 PM
To: dev@ignite.apache.org
Subject: Re: Thin Client Protocol documentation

Hi Alexey,

1,2,3 are related only to handshake. All other operations are consistent.

Handshake request format is dictated by existing client connector that is
shared with ODBC and JDBC clients (see
ClientListenerNioListener.onHandshake).
so we can't add magic numbers or change operation code.

But yes, we can add server version to the handshake response, and I think
this makes sense.

> 4. The same comments for success flag (1 byte) and status code (4 bytes)
in responses. Let's leave only status code.
We don't have a success flag in responses, there is just a 4-byte status
code, 0 indicates success, everything else is an error.

Thanks,
Pavel

On Thu, Nov 30, 2017 at 12:01 PM, Alexey Popov  wrote:

> Hi Pavel,
>
> Let me add my 5 cents.
>
> 1. It would be great if both Handshake request & response have some
> "magic" number (2 or 4 bytes) inside their msg body. That will simplify
> handling situations when non-Ignite client connects to Ignite server and
> vice versa.
>
> 2. It makes sense to add server version to successful Handshake response
> as well. It will help to understand & debug possible backward compatibility
> issues in the field by *.pcap logs analysis & etc.
>
> 3. Can we have a more strict header for all message types?
> As far as I understand,
> Handshake request has:
> 1) length - 4 byte
> 2) Handshake code - 1 byte
> 3) body - (length - 1) bytes
>
> while OP_CACHE_GET request has:
> 1) length - 4 byte
> 2) OP_CACHE_GET code - 2 bytes
> 3) request id - 4 bytes
> 4) body - (length - 2 - 4) bytes
>
> Why some messages have Operation code with 1 byte while others - 2 bytes?
> Why some requests/responses have request-id while others don't? Let's
> simplify parser work )
>
> 4. The same comments for success flag (1 byte) and status code (4 bytes)
> in responses. Let's leave only status code.
>
> Thank you,
> Alexey
>
> From: Pavel Tupitsyn
> Sent: Wednesday, November 22, 2017 4:04 PM
> To: dev@ignite.apache.org
> Subject: Thin Client Protocol documentation
>
> Igniters,
>
> I've put together a detailed description of our Thin Client protocol
> in form of IEP on wiki:
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 9+Thin+Client+Protocol
>
>
> To clarify:
> - Protocol implementation is in master (see ClientMessageParser class)
> - Protocol has not been released yet, so we are free to change anything
> - Protocol is only used by .NET Thin Client for now, but is supposed to be
> used from other languages by third party contributors
> - More operations will be added in future, this is a first set of them,
> cache-related
>
>
> Please review the document and let me know your thoughts.
> Is there anything missing or wrong?
>
> We should make sure that the foundation is solid and extensible.
>
>
> Thanks,
> Pavel
>
>

Re: Time to drop Java 7?

2017-12-01 Thread Andrey Gura

Good news for everyone )

30 нояб. 2017 г. 11:29 PM пользователь "Dmitriy Setrakyan" <
dsetrak...@apache.org> написал:

> +1
>
> On Thu, Nov 30, 2017 at 11:29 AM, Denis Magda  wrote:
>
> > Igniters,
> >
> > Considering that we’re going to support Java 9 in the next release and
> > hitting several limitations caused by current Java 7 support (see spark
> > issue [2] and account difficulties of Java 8 based ML development) I
> would
> > propose to discontinue Java 7.
> >
> > Let’s do both things in AI 2.4: Java 9 support and Java 7 removal.
> >
> > Share your thoughts on this?
> >
> > [1] http://apache-ignite-developers.2346864.n4.nabble.
> > com/Java-9-support-td23612.html
> > [2] http://apache-ignite-developers.2346864.n4.nabble.
> > com/TC-issues-IGNITE-3084-Spark-Data-Frame-API-td24639.html <
> > http://apache-ignite-developers.2346864.n4.nabble.
> > com/TC-issues-IGNITE-3084-Spark-Data-Frame-API-td24639.html>
> >
> > —
> > Denis
>

[GitHub] ignite pull request #3120: IGNITE-6997 .NET: Thin client: Move ClientStatus ...

2017-12-01 Thread ptupitsyn

GitHub user ptupitsyn opened a pull request:

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

IGNITE-6997 .NET: Thin client: Move ClientStatus to public API



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

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

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

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


commit a315a57b4bea0b2ad78dd9ee967bc31fa30e021a
Author: Pavel Tupitsyn 
Date:   2017-12-01T09:58:57Z

IGNITE-6997 .NET: Thin client: Move ClientStatus to public API




---

[GitHub] ignite pull request #3119: IGNITE-7002 .NET: Add cross-platform examples on ...

2017-12-01 Thread ptupitsyn

GitHub user ptupitsyn opened a pull request:

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

IGNITE-7002 .NET: Add cross-platform examples on .NET Core



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

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

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

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


commit b73ca9dc64a1da3619002fe022497c318e750bd3
Author: Pavel Tupitsyn 
Date:   2017-12-01T09:03:06Z

IGNITE-7002 .NET: Add cross-platform examples on .NET Core




---

47 matches

Mail list logo