[jira] [Created] (IGNITE-5696) A localListenAsync method is missing in the IgniteMessaging interface.

[Yujue Li (JIRA)]

Yujue Li created IGNITE-5696:


 Summary: A localListenAsync method is missing in the 
IgniteMessaging interface.
 Key: IGNITE-5696
 URL: https://issues.apache.org/jira/browse/IGNITE-5696
 Project: Ignite
  Issue Type: Bug
  Components: messaging
Affects Versions: 2.0
Reporter: Yujue Li
Priority: Critical
 Fix For: 2.1


Prior to version 2.0, the localListen method supports asynchronous mode because 
of the presence of the withAsync method.
But in version 2.0, this is a problem because the withAsync method is obsolete 
and does not provide a localListenAsync method.



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

[GitHub] ignite pull request #2241: IGNITE-5695 FlinkIgniteSinkSelfTest is failing du...

[samaitra]

GitHub user samaitra opened a pull request:

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

IGNITE-5695 FlinkIgniteSinkSelfTest is failing due to conflicting def…

…ault test timeout and default flush frequency

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

$ git pull https://github.com/samaitra/ignite IGNITE-5695

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

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


commit 38f3e947f47ed0cdd876ec16e3bba3763400a8bc
Author: samaitra 
Date:   2017-07-04T22:55:06Z

IGNITE-5695 FlinkIgniteSinkSelfTest is failing due to conflicting default 
test timeout and default flush frequency




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

[jira] [Created] (IGNITE-5695) FlinkIgniteSinkSelfTest is failing due to conflicting default test timeout and default flush frequency

[Saikat Maitra (JIRA)]

Saikat Maitra created IGNITE-5695:
-

 Summary: FlinkIgniteSinkSelfTest is failing due to conflicting 
default test timeout and default flush frequency
 Key: IGNITE-5695
 URL: https://issues.apache.org/jira/browse/IGNITE-5695
 Project: Ignite
  Issue Type: Bug
  Components: streaming
Affects Versions: 2.0
Reporter: Saikat Maitra
Assignee: Saikat Maitra
Priority: Minor
 Fix For: 2.1


FlinkIgniteSinkSelfTest is failing due to conflicting default test timeout and 
default flush frequency.

Caused by: class org.apache.ignite.spi.IgniteSpiException: Thread has been 
interrupted.
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl.spiStart(ClientImpl.java:275)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1834)
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
... 26 more
Caused by: java.lang.InterruptedException
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1302)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl.spiStart(ClientImpl.java:267)
... 28 more
[2017-07-04 16:49:24,883][WARN 
][test-runner-#37%flink.FlinkIgniteSinkSelfTest%][IgniteKernal] Grid startup 
routine has been interrupted (will rollback).
[2017-07-04 16:49:24,947][INFO 
][test-runner-#37%flink.FlinkIgniteSinkSelfTest%][IgniteKernal] 



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

[GitHub] ignite pull request #887: IGNITE-2344 WebSessionFilter doesn't support sessi...

[samaitra]

Github user samaitra closed the pull request at:

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


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

[GitHub] ignite pull request #926: IGNITE-3263 Affinity function must check for null ...

[samaitra]

Github user samaitra closed the pull request at:

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


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

[GitHub] ignite pull request #847: IGNITE-945 HTTP REST prepend/append commands faile...

[samaitra]

Github user samaitra closed the pull request at:

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


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

[GitHub] ignite pull request #392: IGNITE-255 Jvm8 warns that MaxPermSize is ignored

[samaitra]

Github user samaitra closed the pull request at:

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


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

Re: IGNITE-5468 ticket description looks confusing.

[Dmitriy Setrakyan]

Yakov,

Since you filed this ticket, can you please comment?

D.

On Tue, Jul 4, 2017 at 6:47 AM, Vitaliy Biryukov <
biryukovvitali...@gmail.com> wrote:

> Andrew Mashenkov wrote
> > Thus,
> > *there will no need to pass cache context to methods and classes
> > increasing
> > code complexity.
> > *end user will have ability to tune every single query.
> > *avoid confusing situation with running same query on different caches.
>
> To satisfy all these points, I need to add these 2 parameters into Query
> class.
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/IGNITE-5468-ticket-
> description-looks-confusing-tp19436p19438.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>

[GitHub] ignite pull request #2240: ignite-5694 : Retries for getCollection().

[ilantukh]

GitHub user ilantukh opened a pull request:

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

ignite-5694 : Retries for getCollection().



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

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

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

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


commit 5e38f377482089cb45c93d8da1ad1cf0b13f07d2
Author: Ilya Lantukh 
Date:   2017-07-04T17:59:49Z

ignite-5694 : Retries for getCollection().




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

[jira] [Created] (IGNITE-5694) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover() fails sometimes

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-5694:


 Summary: 
IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover() 
fails sometimes
 Key: IGNITE-5694
 URL: https://issues.apache.org/jira/browse/IGNITE-5694
 Project: Ignite
  Issue Type: Bug
  Components: data structures
Affects Versions: 2.1
Reporter: Ilya Lantukh
Assignee: Ilya Lantukh






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

[GitHub] ignite pull request #2239: ignite-5693 : Fixed flaky test.

[ilantukh]

GitHub user ilantukh opened a pull request:

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

ignite-5693 : Fixed flaky test.



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

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

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

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


commit 31dc7ba80cf44b299eed9f7cece09e47a2dc44bc
Author: Ilya Lantukh 
Date:   2017-07-04T17:04:08Z

ignite-5693 : Fixed flaky test.




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

[GitHub] ignite pull request #2238: ignite-5693

[ilantukh]

Github user ilantukh closed the pull request at:

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


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

[GitHub] ignite pull request #2238: ignite-5693

[ilantukh]

GitHub user ilantukh opened a pull request:

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

ignite-5693



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

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

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

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


commit a5abdd579cc7ace5d17ebcc6555e3ce66c777917
Author: Vasiliy Sisko 
Date:   2017-07-04T11:44:42Z

ignite-2.1 Fixed minor issues and typos.

commit 6c9d2228d2aba6ba5be64bd20ef244e634aeaa5a
Author: Alexey Kuznetsov 
Date:   2017-07-04T12:30:46Z

ignite-2.1 Added persistent store metrics.

commit b69f53e0ccf9d3da42a99d4423fb3d8bdd60a7bb
Author: Pavel Tupitsyn 
Date:   2017-07-04T14:42:31Z

IGNITE-5629 .NET: CacheConfiguration copy constructor

commit 2e7adbfbbab62f3b98e0409d2f4ceabad89b4120
Author: agura 
Date:   2017-07-04T13:56:40Z

ignite-5685 JDBC prepared statement shouldn't clear parameters after 
execution

commit 31dc7ba80cf44b299eed9f7cece09e47a2dc44bc
Author: Ilya Lantukh 
Date:   2017-07-04T17:04:08Z

ignite-5693 : Fixed flaky test.




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

[GitHub] ignite pull request #2237: IGNITE-5663: ODBC: Closing cursor do not reset pr...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-5663: ODBC: Closing cursor do not reset prepared statement anymore



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

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

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

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


commit 0c6c7d98a887a13aca07a2adca2d1b13f9ad69c8
Author: Igor Sapego 
Date:   2017-07-04T16:01:21Z

IGNITE-5663: Fixed an issue.

commit a429648bcbae5b9faabc6d8ec7882763601486ea
Author: Igor Sapego 
Date:   2017-07-04T16:33:41Z

IGNITE-5663: Added test




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

[GitHub] ignite pull request #2236: test-PR-ignite-5097

[daradurvs]

GitHub user daradurvs opened a pull request:

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

test-PR-ignite-5097



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

$ git pull https://github.com/Sberbank-Technology/ignite ignite-5097

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

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


commit 1e1e8432dc936df7c62557575a57c4a159b4bca6
Author: Vyacheslav Daradur 
Date:   2017-05-31T08:41:56Z

ignite-5097: writing arrays length in varint encoding was implemented

commit d162d3e3d9036cddb275b4a3d86b8f5de9795185
Author: daradurvs 
Date:   2017-06-01T18:35:13Z

ignite-5097: doUnsafeWriteUnsignedVarint method was added

commit bfe381b3a7498eb5bebeb25026a43d36656c6041
Author: daradurvs 
Date:   2017-06-04T21:25:48Z

ignite-5097: dotNET - writing arrays length in varint encoding was 
implemented

commit 516fcf41e4e973abf41cdd19acd2c9ea1bfb9445
Author: daradurvs 
Date:   2017-06-04T21:26:00Z

ignite-5097: dotNET - hardcoded hashcode values in the tests were changed 
according to new conditions




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

Re: abbrevation rules plugin

[Dmitry Pavlov]

Hi, Val,

No, this plugin is not available in apache-ignite code base.
May be we should remove reference from JIRA or add this plugin (and also
other code inspections) into AI code base.
Thoughts?

Sincerely,
Dmitriy Pavlov

вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:

> The plugin actually exists, not sure why it's not attached. Does anyone has
> it?
>
> -Val
>
> On Mon, Jul 3, 2017 at 5:27 AM, ALEKSEY KUZNETSOV <
> alkuznetsov...@gmail.com>
> wrote:
>
> > Igntrs!
> > There is a plugin , mentioned  in Abbreviation Rules
> > 
> > page
> > that performs on-the-fly check.Is somebody going to add it some day?
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
>

Re: Apache Ignite 2.1 scope

[Vladimir Ozerov]

Igniters,

We have 536 tickets assinged to 2.1 release [1]. I propose to move all the
tickets which will not be ready by the end of the week to the next release.
You may use this report [2], which will show all the issues which are
either reported by you or assigned to you (you must be logged in to JIRA to
get correct results).

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20status%20not%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.1
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20status%20not%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.1%20AND%20(assignee%20%3D%20currentUser()%20or%20reporter%20%3D%20currentUser())

On Tue, Jul 4, 2017 at 1:20 PM, Vladimir Ozerov 
wrote:

> Igniters,
>
> Persistent store has been merged to master branch! "master-bak" branch was
> created to keep the state before merge for safety. As release date for 2.1
> is mid July, I created "ignite-2.1" branch where we will stabilize the
> release as usual. Please push features and fixes planned for 2.1 release to
> this branch. The rest commits should go to master.
>
> Vladimir.
>
> On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov 
> wrote:
>
>> Hi Denis,
>>
>> Awesome news! I'll take care of necessary release procedures if nobody
>> minds.
>>
>> Vladimir.
>>
>> On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda  wrote:
>>
>>> Igniters,
>>>
>>> It’s time to refresh this abandoned thread and finally rollout out all
>>> the changes appeared in 2.1.
>>>
>>> In addition, recently donated Persistent Store got the green light [1]
>>> to become a part of the master branch (no one asked for extra time to dive
>>> into its details) and, personally, it’s absolutely fine to make it
>>> available in the nearest release.
>>>
>>> My proposal is to do the release by mid of July (closer to July 15th).
>>> Is there anyone who is ready to take over as a release manager creating the
>>> page like this [2] and handling all release related activities?
>>>
>>>
>>> [1] http://apache-ignite-developers.2346864.n4.nabble.com/Ignite
>>> -Persistent-Store-Ready-for-merge-td19160.html
>>> [2] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0
>>>
>>> —
>>> Denis
>>>
>>> > On Jun 1, 2017, at 9:24 AM, Alexander Paschenko <
>>> alexander.a.pasche...@gmail.com> wrote:
>>> >
>>> > IGNITE-5327 Create predefined cache templates for CREATE TABLE command
>>> > - minor comments left, ETA is Friday.
>>> >
>>> > IGNITE-5380 Validate cache QueryEntities in discovery thread - in
>>> > progress, the meat of code is written, but need to add lots of tests.
>>> > ETA is Friday.
>>> >
>>> > IGNITE-5188 Support AFFINITY KEY keyword for CREATE TABLE command - in
>>> > progress, made few first small steps, ETA is Friday.
>>> >
>>> > Rest is closed/patch available, ignite-4994 has been moved to 2.2.
>>> >
>>> > - Alex
>>> >
>>> > 2017-06-01 19:03 GMT+03:00 Sergey Chugunov >> >:
>>> >>   1. IGNITE-5386 Inactive mode must be forced on starting up grid with
>>> >>   persistence is enabled
>>> >>   It is important improvement to fix critical bug IGNITE-5363.
>>> >>   Working on it, ETA - tomorrow.
>>> >>   2. IGNITE-5375 New PersistentStoreMetrics, MemoryMetrics interface
>>> >>   improvements
>>> >>   A lot of discussions were on this topic, ticket created only today
>>> and
>>> >>   requires several days to implement.
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Jun 1, 2017 at 6:56 PM, Taras Ledkov 
>>> wrote:
>>> >>
>>> >>> Folks,
>>> >>>
>>> >>> IGNITE-4922 JDBC Driver: renew thin client based solution:
>>> >>>
>>> >>> On 2.1 the functionality of the new thin client JDBC driver will be
>>> >>> between deprecated Ignite thin JDBC and Ignite JDBCv2.
>>> >>> 1. The most functions of SQL query (include DML) are implemented and
>>> ready
>>> >>> for review;
>>> >>> 2. The most functions of JDBC metadata are implemented and ready for
>>> >>> review;
>>> >>> 3. Transactions, batching, streaming, blobs, scrollable / writable
>>> cursors
>>> >>> will not be supported in 2.1.
>>> >>>
>>> >>>
>>> >>>
>>> >>> On 01.06.2017 18:43, Vladimir Ozerov wrote:
>>> >>>
>>>  Folks,
>>> 
>>>  We are almost reached proposed feature-complete date (June 2),
>>> Could you
>>>  please share current status of your major features?
>>> 
>>>  On Tue, May 16, 2017 at 3:51 AM, Dmitriy Setrakyan <
>>> dsetrak...@apache.org
>>> >
>>>  wrote:
>>> 
>>>  Looks a little tight. Let's hope we can make it.
>>> >
>>> > On Mon, May 15, 2017 at 1:29 PM, Denis Magda 
>>> wrote:
>>> >
>>> > Well, let me propose the following milestones for 2.1 release then.
>>> >>
>>> >> Code freeze: June 2nd.
>>> >> Final QA and benchmarking: June 5 - June 8
>>> >> Voting: ~ June 9
>>> >> Release: ~ June 13
>>> >>
>>> >> Also I heard H2 has to 

[jira] [Created] (IGNITE-5692) IgnitePdsCacheRebalancingAbstractTest suite hangs on TC

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5692:
---

 Summary: IgnitePdsCacheRebalancingAbstractTest suite hangs on TC
 Key: IGNITE-5692
 URL: https://issues.apache.org/jira/browse/IGNITE-5692
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Kovalenko
Priority: Critical


Exact tests are testTopologyChangesWithConstantLoad and 
testTopologyChangesWithConstantLoadExplicitTx in IgnitePdsTxCacheRebalancingTest

Cause of hanging is unfinished partition map exchange:

{noformat}
[2017-07-04 18:08:31,112][WARN 
][test-runner-#1%persistence.IgnitePdsTxCacheRebalancingTest%][root] Waiting 
for topology map update 
[igniteInstanceName=persistence.IgnitePdsTxCacheRebalancingTest3, 
cache=indexed, cacheId=1943292145, topVer=AffinityTopologyVersion [topVer=13, 
minorTopVer=0], p=0, affNodesCnt=2, ownersCnt=1, 
affNodes=[c9c01bd9-e15d-4b62-86be-f1a18383, 
de98b611-fc6d-4149-857c-9a325314], 
owners=[c9c01bd9-e15d-4b62-86be-f1a18383], 
topFut=GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=b71b30b7-2df9-4f35-aeaf-cefd0e95, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47505], discPort=47505, order=12, intOrder=9, 
lastExchangeTime=1499180827453, loc=false, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=13, nodeId8=c9c01bd9, msg=Node left: TcpDiscoveryNode 
[id=b71b30b7-2df9-4f35-aeaf-cefd0e95, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47505], discPort=47505, order=12, intOrder=9, 
lastExchangeTime=1499180827453, loc=false, ver=2.1.0#19700101-sha1:, 
isClient=false], type=NODE_LEFT, tstamp=1499180845215], crd=TcpDiscoveryNode 
[id=1a513139-cfce-48c9-aab0-71b7ecb0, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1499180791749, loc=false, ver=2.1.0#19700101-sha1:, 
isClient=false], exchId=GridDhtPartitionExchangeId 
[topVer=AffinityTopologyVersion [topVer=13, minorTopVer=0], nodeId=b71b30b7, 
evt=NODE_LEFT], added=true, initFut=GridFutureAdapter [ignoreInterrupts=false, 
state=DONE, res=true, hash=1444700749], init=true, lastVer=null, 
partReleaseFut=GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=4, 
done=true, cancelled=false, err=null, futs=[true, true, true, true]], 
exchActions=null, affChangeMsg=null, skipPreload=false, 
clientOnlyExchange=false, initTs=1499180845227, centralizedAff=true, 
changeGlobalStateE=null, exchangeOnChangeGlobalState=false, forcedRebFut=null, 
done=true, evtLatch=0, remaining=[89a60809-876d-4ea7-845d-a41ddea2, 
de98b611-fc6d-4149-857c-9a325314, 1a513139-cfce-48c9-aab0-71b7ecb0, 
b2e733e4-35e2-4860-ae90-d0a8b0a1], super=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=AffinityTopologyVersion [topVer=13, 
minorTopVer=0], hash=1954469014]], locNode=TcpDiscoveryNode 
[id=c9c01bd9-e15d-4b62-86be-f1a18383, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47503], discPort=47503, order=10, intOrder=7, 
lastExchangeTime=1499180911088, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false]]
{noformat}




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

[GitHub] ignite pull request #2235: two tests unmuted, one test removed as obsolete (...

[sergey-chugunov-1985]

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

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

two tests unmuted, one test removed as obsolete (IGNITE-5592)



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

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

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

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


commit 9a60e4fe11c2c9f301e9c93a9ce4cb4a7afd1666
Author: Sergey Chugunov 
Date:   2017-07-04T14:53:57Z

IGNITE-4536 two tests unmuted, one test removed as obsolete (IGNITE-5592)




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

[GitHub] ignite pull request #2234: IGNITE-5482

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-5482



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

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

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

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






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

[GitHub] ignite pull request #2139: IGNITE-5482

[alexpaschenko]

Github user alexpaschenko closed the pull request at:

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


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

[jira] [Created] (IGNITE-5690) JavaEmbeddedIgniteRDDSelfTest sometimes hangs on TC

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-5690:


 Summary: JavaEmbeddedIgniteRDDSelfTest sometimes hangs on TC
 Key: IGNITE-5690
 URL: https://issues.apache.org/jira/browse/IGNITE-5690
 Project: Ignite
  Issue Type: Bug
  Components: spark
Affects Versions: 2.1
Reporter: Ilya Lantukh


Test hangs when IgniteContext.close(...) is called:
{noformat}
[12:20:47]W: [org.apache.ignite:ignite-spark] Thread 
[name="test-runner-#1%spark.JavaEmbeddedIgniteRDDSelfTest%", id=77, 
state=WAITING, blockCnt=59, waitCnt=10012]
[12:20:47]W: [org.apache.ignite:ignite-spark] Lock 
[object=scala.concurrent.impl.Promise$CompletionLatch@77d938ab, ownerName=null, 
ownerId=-1]
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
sun.misc.Unsafe.park(Native Method)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
scala.concurrent.impl.Promise$DefaultPromise.tryAwait(Promise.scala:202)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:218)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:153)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:619)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.SparkContext.runJob(SparkContext.scala:1918)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.SparkContext.runJob(SparkContext.scala:1931)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.SparkContext.runJob(SparkContext.scala:1944)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.SparkContext.runJob(SparkContext.scala:1958)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1.apply(RDD.scala:925)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1.apply(RDD.scala:923)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:112)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.rdd.RDD.withScope(RDD.scala:362)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
org.apache.spark.rdd.RDD.foreachPartition(RDD.scala:923)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
o.a.i.spark.IgniteContext.close(IgniteContext.scala:168)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
o.a.i.spark.JavaIgniteContext.close(JavaIgniteContext.scala:68)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
o.a.i.spark.JavaEmbeddedIgniteRDDSelfTest.testReadDataFromIgnite(JavaEmbeddedIgniteRDDSelfTest.java:181)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
java.lang.reflect.Method.invoke(Method.java:606)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
junit.framework.TestCase.runTest(TestCase.java:176)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
[12:20:47]W: [org.apache.ignite:ignite-spark] at 
o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
[12:20:47]W: 

[GitHub] ignite pull request #2233: IGNITE-5679: add JDBC example

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5679: add JDBC example



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

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

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

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






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

[GitHub] ignite pull request #2232: IGNITE-5679 JDBC thin driver: add example

[tledkov-gridgain]

Github user tledkov-gridgain closed the pull request at:

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


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

[GitHub] ignite pull request #2232: IGNITE-5679 JDBC thin driver: add example

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5679  JDBC thin driver: add example



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

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

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

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


commit a5abdd579cc7ace5d17ebcc6555e3ce66c777917
Author: Vasiliy Sisko 
Date:   2017-07-04T11:44:42Z

ignite-2.1 Fixed minor issues and typos.

commit 6c9d2228d2aba6ba5be64bd20ef244e634aeaa5a
Author: Alexey Kuznetsov 
Date:   2017-07-04T12:30:46Z

ignite-2.1 Added persistent store metrics.




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

[jira] [Created] (IGNITE-5689) IgniteCommunicationBalanceTest hangs on Windows

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-5689:


 Summary: IgniteCommunicationBalanceTest hangs on Windows
 Key: IGNITE-5689
 URL: https://issues.apache.org/jira/browse/IGNITE-5689
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ilya Lantukh


Test runner is waiting for ComputeTask to finish:
{noformat}
"test-runner-#40602%communication.IgniteCommunicationBalanceMultipleConnectionsTest%"
 prio=6 tid=0x766d6000 nid=0x7934 waiting on condition 
[0xeacfe000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
at 
org.apache.ignite.internal.AsyncSupportAdapter.saveOrGet(AsyncSupportAdapter.java:112)
at 
org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
at 
org.apache.ignite.internal.managers.communication.IgniteCommunicationBalanceTest$1.apply(IgniteCommunicationBalanceTest.java:158)
at 
org.apache.ignite.testframework.GridTestUtils.waitForCondition(GridTestUtils.java:1603)
at 
org.apache.ignite.internal.managers.communication.IgniteCommunicationBalanceTest.testBalance1(IgniteCommunicationBalanceTest.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
at java.lang.Thread.run(Thread.java:745)
{noformat}

While thread that tried to send job result got stuck in 
IgniteUtils.reachable(...):
{noformat}
"pub-#40657%communication.IgniteCommunicationBalanceMultipleConnectionsTest5%" 
prio=6 tid=0x11b8 nid=0x3868 runnable [0xeecfe000]
   java.lang.Thread.State: RUNNABLE
at java.net.Inet4AddressImpl.isReachable0(Native Method)
at java.net.Inet4AddressImpl.isReachable(Inet4AddressImpl.java:70)
at java.net.InetAddress.isReachable(InetAddress.java:475)
at java.net.InetAddress.isReachable(InetAddress.java:434)
at 
org.apache.ignite.internal.util.IgniteUtils.reachable(IgniteUtils.java:2113)
at 
org.apache.ignite.internal.util.IgniteUtils.filterReachable(IgniteUtils.java:1877)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2955)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2763)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2655)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2516)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2480)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1643)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1715)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:928)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:773)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:625)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 

[jira] [Created] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Artem Malykh (JIRA)]

Artem Malykh created IGNITE-5688:


 Summary: Fix SparseDistributedMatrixTest::testCacheBehaviour crash
 Key: IGNITE-5688
 URL: https://issues.apache.org/jira/browse/IGNITE-5688
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Artem Malykh
Assignee: Artem Malykh
 Fix For: 2.1






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

Re: IGNITE-5123

[Evgeniy Ignatiev]

As it is explicitly stated in Javadoc of PluginProvider#onIgniteStart 
that all internal components should be started before this method is 
called, which is not true, as internal component callbacks are called 
right after the PluginProvider#onIgniteStart.


On 7/2/2017 12:58 PM, Evgeniy Ignatiev wrote:

Hello, Igniters.

Looking at the ticket 
https://issues.apache.org/jira/browse/IGNITE-5123, the 
IgniteKernal#start notifies plugin providers, calling 
PluginProvider#onIgniteStart, before components are notified, when 
caches are created in GridCacheProcessor#onIgniteStart. Does it make 
sense to move plugin providers notification after components are 
notified, probably right before lifecycle beans notification, so to 
ensure that caches are started before PluginProvider#onIgniteStart 
method is called?

Re: IGNITE-5468 ticket description looks confusing.

[Vitaliy Biryukov]

Andrew Mashenkov wrote
> Thus,
> *there will no need to pass cache context to methods and classes
> increasing
> code complexity.
> *end user will have ability to tune every single query.
> *avoid confusing situation with running same query on different caches.

To satisfy all these points, I need to add these 2 parameters into Query
class.



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-5468-ticket-description-looks-confusing-tp19436p19438.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[jira] [Created] (IGNITE-5687) .NET: Store deserialized values on heap optionally

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5687:
--

 Summary: .NET: Store deserialized values on heap optionally
 Key: IGNITE-5687
 URL: https://issues.apache.org/jira/browse/IGNITE-5687
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn


Add an option to store deserialized cache values in .NET heap for quick access 
(Java side has this: IGNITE-4535).

.NET filters and predicates (scan query, entry processors, etc) require binary 
object copy and deserialization on every call. Storing deserialized entries in 
.NET memory would remove this overhead.

Java uses eviction policy to control size and behavior of on-heap cache.



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

IGNITE-5468 ticket description looks confusing.

[Andrey Mashenkov]

Guys,

We have a ticket that is implemented, but the ticket itseft and the
solution looks confusing as ticket title is differs to its description:
"IGNITE-5468: Need to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE on per query
basis" [1]


Seems, initially, we want to have ability to change these 2 parameters  as
on per-query basis as its defaults.

Having defaults in cache configuration is error prone as we can run same
query on different caches with different defaults.
With this approach we will get confused if same query will work fine with
one cache and fails with OOME on another.
Furthermore, we have a plans to move sql configuration options out from
cache configuration in future releases.

Lets introduce additional options in SqlQuery and SqlFieldsQuery classes
and leave CacheConfiguration without changes.

Thus,
*there will no need to pass cache context to methods and classes increasing
code complexity.
*end user will have ability to tune every single query.
*avoid confusing situation with running same query on different caches.


Thoughts?

[1] https://issues.apache.org/jira/browse/IGNITE-5468

-- 
Best regards,
Andrey V. Mashenkov

[GitHub] ignite pull request #2231: IGNITE-GG-11209 Extract File I/O interface

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-GG-11209 Extract File I/O interface



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

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

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

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


commit 255d73ec779bb71bd17ddff0d875448031d16c51
Author: Pavel Kovalenko 
Date:   2017-07-03T17:07:26Z

GG-12418 Fixed WAL hanging during flush. Refactored and added test for it.

commit 0421146e47e9a273ebb47b77f566e3e72f6e8398
Author: Pavel Kovalenko 
Date:   2017-07-04T07:53:57Z

GG-12418 Test fixes and small refactoring.

commit 845cf6d4ed8375f8aeff792235ea261ffc95cd85
Author: Pavel Kovalenko 
Date:   2017-07-04T10:56:02Z

GG-11209 Introduced File I/O interface and factory.
Introduced implementation for File I/O based on RandomAccessFile.
Delegate all file I/O logic for WAL and FileStore to FileIO interface.
Fixed IgniteWalFlushFailoverTest.




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

[jira] [Created] (IGNITE-5686) Endless partition eviction during node shutdown

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5686:


 Summary: Endless partition eviction during node shutdown
 Key: IGNITE-5686
 URL: https://issues.apache.org/jira/browse/IGNITE-5686
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.1
Reporter: Alexey Goncharuk
 Fix For: 2.1


Observed the following behavior on TC:
A node cannot stop because system threads are continuously trying to clean 
partitions.

Attached is a thread dump from the test



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

Re: Apache Ignite 2.1 scope

[Vladimir Ozerov]

Igniters,

Persistent store has been merged to master branch! "master-bak" branch was
created to keep the state before merge for safety. As release date for 2.1
is mid July, I created "ignite-2.1" branch where we will stabilize the
release as usual. Please push features and fixes planned for 2.1 release to
this branch. The rest commits should go to master.

Vladimir.

On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov 
wrote:

> Hi Denis,
>
> Awesome news! I'll take care of necessary release procedures if nobody
> minds.
>
> Vladimir.
>
> On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda  wrote:
>
>> Igniters,
>>
>> It’s time to refresh this abandoned thread and finally rollout out all
>> the changes appeared in 2.1.
>>
>> In addition, recently donated Persistent Store got the green light [1] to
>> become a part of the master branch (no one asked for extra time to dive
>> into its details) and, personally, it’s absolutely fine to make it
>> available in the nearest release.
>>
>> My proposal is to do the release by mid of July (closer to July 15th). Is
>> there anyone who is ready to take over as a release manager creating the
>> page like this [2] and handling all release related activities?
>>
>>
>> [1] http://apache-ignite-developers.2346864.n4.nabble.com/
>> Ignite-Persistent-Store-Ready-for-merge-td19160.html
>> [2] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0
>>
>> —
>> Denis
>>
>> > On Jun 1, 2017, at 9:24 AM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>> >
>> > IGNITE-5327 Create predefined cache templates for CREATE TABLE command
>> > - minor comments left, ETA is Friday.
>> >
>> > IGNITE-5380 Validate cache QueryEntities in discovery thread - in
>> > progress, the meat of code is written, but need to add lots of tests.
>> > ETA is Friday.
>> >
>> > IGNITE-5188 Support AFFINITY KEY keyword for CREATE TABLE command - in
>> > progress, made few first small steps, ETA is Friday.
>> >
>> > Rest is closed/patch available, ignite-4994 has been moved to 2.2.
>> >
>> > - Alex
>> >
>> > 2017-06-01 19:03 GMT+03:00 Sergey Chugunov :
>> >>   1. IGNITE-5386 Inactive mode must be forced on starting up grid with
>> >>   persistence is enabled
>> >>   It is important improvement to fix critical bug IGNITE-5363.
>> >>   Working on it, ETA - tomorrow.
>> >>   2. IGNITE-5375 New PersistentStoreMetrics, MemoryMetrics interface
>> >>   improvements
>> >>   A lot of discussions were on this topic, ticket created only today
>> and
>> >>   requires several days to implement.
>> >>
>> >>
>> >>
>> >> On Thu, Jun 1, 2017 at 6:56 PM, Taras Ledkov 
>> wrote:
>> >>
>> >>> Folks,
>> >>>
>> >>> IGNITE-4922 JDBC Driver: renew thin client based solution:
>> >>>
>> >>> On 2.1 the functionality of the new thin client JDBC driver will be
>> >>> between deprecated Ignite thin JDBC and Ignite JDBCv2.
>> >>> 1. The most functions of SQL query (include DML) are implemented and
>> ready
>> >>> for review;
>> >>> 2. The most functions of JDBC metadata are implemented and ready for
>> >>> review;
>> >>> 3. Transactions, batching, streaming, blobs, scrollable / writable
>> cursors
>> >>> will not be supported in 2.1.
>> >>>
>> >>>
>> >>>
>> >>> On 01.06.2017 18:43, Vladimir Ozerov wrote:
>> >>>
>>  Folks,
>> 
>>  We are almost reached proposed feature-complete date (June 2), Could
>> you
>>  please share current status of your major features?
>> 
>>  On Tue, May 16, 2017 at 3:51 AM, Dmitriy Setrakyan <
>> dsetrak...@apache.org
>> >
>>  wrote:
>> 
>>  Looks a little tight. Let's hope we can make it.
>> >
>> > On Mon, May 15, 2017 at 1:29 PM, Denis Magda 
>> wrote:
>> >
>> > Well, let me propose the following milestones for 2.1 release then.
>> >>
>> >> Code freeze: June 2nd.
>> >> Final QA and benchmarking: June 5 - June 8
>> >> Voting: ~ June 9
>> >> Release: ~ June 13
>> >>
>> >> Also I heard H2 has to be released once again to support Ignite’s
>> CREATE
>> >> table command. Think that we should talk to H2 folks to make it
>> happen
>> >> in
>> >> June 22nd - June 2nd time frame.
>> >>
>> >> —
>> >> Denis
>> >>
>> >> On May 11, 2017, at 2:26 AM, Pavel Tupitsyn 
>> >>>
>> >> wrote:
>> >>
>> >>> As for .NET, I would propose to concentrate on peer deployment
>> >>>
>> >> (IGNITE-2492)
>> >>
>> >>> and related stuff, like IGNITE-1894 .NET: Delegate support in the
>> API
>> >>>
>> >> via
>> >
>> >> extension methods.
>> >>>
>> >>> SQL Dependency does not look important to me, we can reschedule
>> it for
>> >>> later versions.
>> >>>
>> >>> On Thu, May 11, 2017 at 12:01 PM, Dmitriy Setrakyan <
>> >>>
>> >> dsetrak...@apache.org>
>> >>
>> >>> wrote:
>> >>>
>> >>> Vyacheslav, I 

[GitHub] ignite pull request #2029: IGNITE-5301 JVM crashes on H2TreeIndex destroy

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2157: Ignite 2.1.2

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2145: IGNITE-5519

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2169: Ignite-gg-12336 Visor node throws NPE on exit

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2156: Ignite-gg-12335 Fail activation after fail get fi...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2152: Fixed handling of DS cache not present on local n...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2135: Data structures redesign based on cache groups

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2002: Ignite 5267

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2171: Ingite-gg-12329 Do not update partition map if cl...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #1821: 8.0.4.ea1 tests run

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2120: Ignite 2.1.1

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #1924: Ignite-gg-12163 Persistent store

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #1864: ignite-5068

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #1859: Replaced AssertionError with IgniteCheckedExcepti...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Created] (IGNITE-5685) JDBC: Prepared statement shouldn't clear params after query execution

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-5685:
---

 Summary: JDBC: Prepared statement shouldn't clear params after 
query execution
 Key: IGNITE-5685
 URL: https://issues.apache.org/jira/browse/IGNITE-5685
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.0
Reporter: Andrey Gura
Assignee: Andrey Gura
 Fix For: 2.1


`JdbcPreparedStatement` implementations (both Java client and Ignite client 
node based) clears query parameters in `executeQuery` method after query 
execution. It's wrong behavior because `PreparedStatement` allows repeatable 
use.



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

[GitHub] ignite pull request #1842: part2node map optimizations

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] ignite pull request #2230: IGNITE-5554 ServiceProcessor may process failed r...

[mcherkasov]

GitHub user mcherkasov opened a pull request:

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

IGNITE-5554 ServiceProcessor may process failed reassignments in timeout 
thread



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

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

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

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


commit 7734a7d0adbd5f43bcaa4d726231388fcd0d4784
Author: mcherkasov 
Date:   2017-06-30T17:23:55Z

Deployment re-try operations are moved to deployment executor.




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

[jira] [Created] (IGNITE-5684) IgniteClientCacheStartFailoverTest.testClientStartLastServerFails* fails

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5684:
---

 Summary: 
IgniteClientCacheStartFailoverTest.testClientStartLastServerFails* fails
 Key: IGNITE-5684
 URL: https://issues.apache.org/jira/browse/IGNITE-5684
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Alexey Goncharuk
 Fix For: 2.1


This is a regression appeared during persistent store migration. Affected tests:
- testClientStartLastServerFailsTx
- testClientStartLastServerFailsAtomic

{code}
[2017-07-04 
11:46:46,937][ERROR][test-runner-#566%cache.IgniteClientCacheStartFailoverTest%][GridDhtColocatedCache]
  Failed to rollback transaction (cache may contain stale locks): 
GridNearTxLocal [mappings=IgniteTxMappingsSingleImpl [mapping=null], 
nearLocallyMapped=false, colocatedLocallyMapped=false, needCheckBackup=null, 
hasRemoteLocks=false, 
thread=test-runner-#566%cache.IgniteClientCacheStartFailoverTest%, 
mappings=IgniteTxMappingsSingleImpl [mapping=null], super=GridDhtTxLocalAdapter 
[nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false, 
super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false, 
depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true, 
recovery=false], super=IgniteTxAdapter [xidVer=GridCacheVersion 
[topVer=110637994, order=1499158001738, nodeOrder=4], writeVer=null, 
implicit=true, loc=true, threadId=696, startTime=1499158006925, 
nodeId=3088492b-e01e-4bd0-b06b-52e088a3, startVer=GridCacheVersion 
[topVer=110637994, order=1499158001738, nodeOrder=4], endVer=null, 
isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
sysInvalidate=false, sys=false, plc=2, commitVer=null, finalizing=NONE, 
invalidParts=null, state=ROLLED_BACK, timedOut=false, 
topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0], duration=0ms, 
onePhaseCommit=false], size=1]]]
class org.apache.ignite.IgniteCheckedException: Failed to commit transaction: 
GridNearTxLocal[id=a48b7cc0d51--0698-33aa--0004, 
concurrency=OPTIMISTIC, isolation=READ_COMMITTED, state=ROLLED_BACK, 
invalidate=false, rollbackOnly=true, 
nodeId=3088492b-e01e-4bd0-b06b-52e088a3, duration=0]
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:423)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.rollbackNearTxLocalAsync(GridNearTxLocal.java:3255)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$10.applyx(GridNearTxLocal.java:2401)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$10.applyx(GridNearTxLocal.java:2383)
at 
org.apache.ignite.internal.util.lang.IgniteClosureX.apply(IgniteClosureX.java:38)
at 
org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:78)
at 
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
at 
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter$ChainFuture.(GridFutureAdapter.java:556)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.chain(GridFutureAdapter.java:357)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.optimisticPutFuture(GridNearTxLocal.java:2382)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:623)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:386)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$21.op(GridCacheAdapter.java:2337)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$21.op(GridCacheAdapter.java:2335)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4037)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2335)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2316)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2293)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1501)
at 
org.apache.ignite.internal.processors.cache.IgniteClientCacheStartFailoverTest$4.call(IgniteClientCacheStartFailoverTest.java:220)
at 

[jira] [Created] (IGNITE-5683) Web Console: missing fully qualified name for generated indexed types on Models Screen

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-5683:


 Summary: Web Console: missing fully qualified name for generated 
indexed types on Models Screen
 Key: IGNITE-5683
 URL: https://issues.apache.org/jira/browse/IGNITE-5683
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Alexey Kuznetsov


https://stackoverflow.com/questions/44468342/automatic-persistence-unable-to-bring-up-cache-with-web-console-generated-mode



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

[jira] [Created] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5682:
---

 Summary: GridCacheRabalancingDelayedPartitionMapExchangeSelfTest 
fails
 Key: IGNITE-5682
 URL: https://issues.apache.org/jira/browse/IGNITE-5682
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
 Fix For: 2.1


This appears to be a regression introduced during persistent store migration. 

{code}
class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
update 
[igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
 cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion [topVer=10, 
minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10, 
minorTopVer=0], locNode=TcpDiscoveryNode 
[id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:, 
isClient=false]]

at 
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
at 
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
at 
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
at 
org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
at java.lang.Thread.run(Thread.java:745)
{code}



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

[jira] [Created] (IGNITE-5681) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover fails

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5681:
---

 Summary: 
IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover 
fails
 Key: IGNITE-5681
 URL: https://issues.apache.org/jira/browse/IGNITE-5681
 Project: Ignite
  Issue Type: Bug
  Components: data structures
Reporter: Vladimir Ozerov
 Fix For: 2.1


This is a regression introduced during persistent store migration.

{code}
[2017-07-04 11:20:46,993][ERROR][main][root] Test failed.
class org.apache.ignite.IgniteException: Failed to update keys (retry update if 
possible).: [GridCacheQueueHeaderKey [name=q-3]]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:3648)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:164)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:155)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testFailoverWithClient(IgniteAtomicLongChangingTopologySelfTest.java:221)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover(IgniteAtomicLongChangingTopologySelfTest.java:155)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
at java.lang.Thread.run(Thread.java:745)
Caused by: class 
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException: 
Failed to update keys (retry update if possible).: [GridCacheQueueHeaderKey 
[name=q-3]]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:398)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:155)
at 
org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1353)
at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:895)
at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:344)
at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:311)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2401)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2598)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2430)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
... 1 more
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
update keys on primary node.
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKeys(UpdateErrors.java:124)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:342)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.primaryFailedResponse(GridNearAtomicAbstractUpdateFuture.java:435)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:149)
... 10 more
Suppressed: class 
org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Primary 
node left grid 

[jira] [Created] (IGNITE-5679) JDBC thin driver: add example

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5679:
---

 Summary: JDBC thin driver: add example
 Key: IGNITE-5679
 URL: https://issues.apache.org/jira/browse/IGNITE-5679
 Project: Ignite
  Issue Type: Task
  Components: jdbc
Reporter: Vladimir Ozerov
Assignee: Taras Ledkov
Priority: Critical
 Fix For: 2.1


We need to add an example for new JDBC driver.



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

[GitHub] ignite pull request #2229: IGNITE-GG-12418 Fix hanging WAL flusher

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-GG-12418 Fix hanging WAL flusher



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

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

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

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


commit 9ebdc1106555d9233d5d328fd6cc71f7a1402490
Author: Alexey Kuznetsov 
Date:   2017-06-14T07:58:20Z

IGNITE-5239 Web Console show full stack trace on Queries screen.

commit 87c6bf2b761f585dee095f9a56641b4741d0db3b
Author: Andrey Novikov 
Date:   2017-06-14T08:04:11Z

IGNITE-5366 Web Console: Added user notifications.

commit b7a19ae7b54f05a0f2fe8223397e59f34b4f63cf
Author: Vasiliy Sisko 
Date:   2017-06-14T08:32:00Z

IGNITE-5240 Fixed repository name.

commit 42c04ddb17f560f4120636431da20e6e0b1422a9
Author: Alexey Kuznetsov 
Date:   2017-06-14T08:46:40Z

IGNITE-5481 Reworked rebalance detection.

commit 29df01dd2196fda7ed927e67e5e8bad194ce6f34
Author: Andrey Novikov 
Date:   2017-06-14T08:55:03Z

IGNITE-5402 Web Console: Fixed near cache generation for client mode.

commit 0cb8a0ea43fc9dc1902655c32ba03968a3c3b517
Author: Igor Sapego 
Date:   2017-06-13T16:14:38Z

GNITE-5478: ODBC: SQLNumParams now returns number of required parameters.

commit 3f8ef4f821908b1a910a36c07457553b17f763e4
Author: Alexey Kuznetsov 
Date:   2017-06-13T16:30:43Z

master - Fixed typo.

commit 3bf8b0319fc50cb4a9294f90f4cf7b689bc48a77
Author: dpavlov 
Date:   2017-06-14T10:57:40Z

Fixing snapshot tests for 8.2.1 release: Activating grid in tests, NPE fix, 
class cast fix

commit 5f5c5f1ba07cccd1ee072f4b1f95d32459d9507b
Author: dpavlov 
Date:   2017-06-14T10:58:21Z

Merge remote-tracking branch 'apache-gridgain-fork/ignite-2.1.1' into 
ignite-2.1.1

commit 40db31ef76303215db1703166c94b795cd2eb2b2
Author: Dmitriy Govorukhin 
Date:   2017-06-14T11:16:08Z

ignite-2.1.1 do not create database shared manger on client + cosmetic 
changes

commit 4e973551a4264395aa7fe167aba61736a0d259e6
Author: Dmitriy Govorukhin 
Date:   2017-06-14T11:49:13Z

ignite-2.1.1 invoke activate/deactivate for snapshot manager.

commit 69aa299c9f9f864086266d618d28b78ca407b8ac
Author: devozerov 
Date:   2017-06-14T11:55:48Z

Fixed missing Apache header in HttpIgniteUpdatesChecker.

commit 4eb8c5e4c687edb1c695d2d38ad93cca09cd024a
Author: Dmitriy Govorukhin 
Date:   2017-06-14T12:08:01Z

ignite-2.1.1 validate operation change global state if snapshot operation 
in progress

commit 752dd65f82221fdc7570c50ae4c0d41652541422
Author: Dmitriy Govorukhin 
Date:   2017-06-14T12:08:29Z

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

commit 3d269d7d5094acb9b8ac86de16fc16c8c80ec5e6
Author: Ilya Lantukh 
Date:   2017-06-14T12:20:20Z

Minors.

commit 73df0354241bff62c854847c4c98abac8a5b4c24
Author: Ilya Lantukh 
Date:   2017-06-14T12:39:17Z

Minors.

commit 8b85477eabd6e9059d3849a277b9494845b67293
Author: Ilya Lantukh 
Date:   2017-06-14T12:47:29Z

Cache type validation.

commit 51e6aed7c82e4c7885b85c57a7235f0d5872b7e7
Author: dpavlov 
Date:   2017-06-14T13:00:46Z

GG-12283: disabled handing tests to run others

commit 0292110a0427ecce0b10f9b3393d0c1b94b254f6
Author: dpavlov 
Date:   2017-06-14T13:37:15Z

IGNITE-5487: disabled handing tests to run others

commit d285f82b2540f84a88d4c655d6e3a74680b0f766
Author: oleg-ostanin 
Date:   2017-06-14T13:47:46Z

IGNITE-5488 Build failure: maven-remote-resources-plugin

commit e7a7751a9d60c541c57f570779a6301abdb696b5
Author: Dmitriy Govorukhin 
Date:   2017-06-14T13:53:22Z

ignite-gg-12290 fix npe in cluster processor if got exception on start in 
plugin processor.

commit c5882ba94a21859dd5fac7f50b792512492c7018
Author: Dmitriy Govorukhin 
Date:   2017-06-14T13:53:42Z

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

commit 59dace5a3883596d7edb661e6f8a328cca4a059e
Author: Ilya Lantukh 
Date:   2017-06-14T15:11:23Z

Fixed assertion error when tried to aquire affinity assignment for NONE 
topology version.

commit b1d8a4975585dddc6256496c3c797362eddac0ed
Author: devozerov