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

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-5482



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

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

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

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


commit d6e7050280817b4705302346e170a1809a3d1a91
Author: Ivan Rakov 
Date:   2017-05-03T08:24:01Z

IGNITE-5134: Fixed ClassCastException in IgniteCacheDatabaseSharedManager. 
This closes #1895.

commit ff08c8e09033a1a703aae602c36a21565fbae606
Author: Anton Vinogradov 
Date:   2017-05-03T09:49:18Z

Hibernate module deploy fix

commit bc4735f7f5e3fe97aa5f30ef8bdf88e0749d6e2e
Author: Igor Sapego 
Date:   2017-05-03T15:12:49Z

IGNITE-5132: Fixed PutGet example.

(cherry picked from commit ed72663ff8e6b6f46d77c91471400ec1c9ff0dfa)

commit a5ae1834621e3c09ed911777ba652ce4e53ea7e1
Author: devozerov 
Date:   2017-05-05T09:16:36Z

Fixed JavaDocs in MemoryMetricsImpl.

commit b051163be08b50fc1ead70e8640703376f4c1642
Author: devozerov 
Date:   2017-05-05T15:06:00Z

Removed ML from GG PE build for now.

commit 0c45750bdcaabf72980f775e0bc2f18edc603607
Author: Sergi Vladykin 
Date:   2017-05-11T13:01:38Z

IGNITE-5190 - ArrayIndexOutOfBoundsException in GridMergeIndexSorted

(cherry picked from commit 3a9dba5)

commit 1e1198555358eca9163753249fbef8bd1a3ef702
Author: Sergi Vladykin 
Date:   2017-05-09T03:11:34Z

master - fixed SELECT (SELECT COUNT(1)) FROM

(cherry picked from commit d10091d)

commit b4d8c341930f8873f03427b6e25d2c9f30514c0b
Author: Sergi Vladykin 
Date:   2017-05-09T15:17:40Z

master - minor fix for subqueries with aggregates

(cherry picked from commit b039d05)

commit b7d926e71e7e0af3a5f067891bd8115b21af9318
Author: AMRepo 
Date:   2017-05-26T09:44:20Z

Fixed segmented indices snapshots. - Fixes #1936.

Signed-off-by: Sergi Vladykin 

(cherry picked from commit 1554a16)

commit 5658c45549eef86d94ad806e76e48fb997e99a94
Author: Andrey V. Mashenkov 
Date:   2017-05-15T17:24:10Z

IGNITE-5225: Fix NPE caused by changes in IGNITE-4577.

(cherry picked from commit d463840)

(cherry picked from commit 95850b4)

commit 51868846b5792561ef345f4b90f41a3026528a1e
Author: Andrey V. Mashenkov 
Date:   2017-05-24T10:19:16Z

IGNITE-5252: Expose getFieldName method to SqlFieldsQuery result. - Fixes 
#1982.

Signed-off-by: Sergi Vladykin 
(cherry picked from commit 647fd195b310df10b230b67c92a8df04b5a064e2)

(cherry picked from commit 4155d42)

commit 318f2816f84c3f1b69001ee157aabe83f2c290fb
Author: AMRepo 
Date:   2017-05-26T17:08:43Z

IGNITE-11423: all changes.

commit f3757ce315c5b2e4a222a0cefed3ce0704f6
Author: Alexander Paschenko 
Date:   2017-06-14T16:37:38Z

IGNITE-5482 MAP query results reuse.

commit 551a44341c620a7c6573f17679e5b35232dc870d
Author: Alexander Paschenko 
Date:   2017-06-15T14:08:32Z

IGNITE-5482 Continued

commit 0a4dec754604ce409b6ad2a2738cb21e88a2a223
Author: Alexander Paschenko 
Date:   2017-06-15T18:05:23Z

IGNITE-5482 Finished

commit 2dcf98cd7641f5f99da5e7dd0bf0e8c95d2e9014
Author: Alexander Paschenko 
Date:   2017-06-15T18:14:35Z

Added comments.




---
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: Persistence enabled for all caches

[Dmitriy Setrakyan]

Sergey, the case you describe should fail with an error. I think I would
want users to delete the persistence store for that cache manually before
restarting, if they want to disable the persistence.

On Thu, Jun 15, 2017 at 3:24 AM, Sergey Kozlov  wrote:

> I agree and would note that we need to investigate more various corner
> cases like user has cache with PS , then stop grid, switch in memory and
> start again. Is there a chance to load data (if it can place in memory).
> Also would be interesting to switch mode runtime.
>
> On Tue, Jun 13, 2017 at 12:38 PM, Dmitriy Setrakyan  >
> wrote:
>
> > +1
> >
> > On Tue, Jun 13, 2017 at 1:13 AM, Yakov Zhdanov 
> > wrote:
> >
> > > Sam,
> > >
> > > Absolutely agree. Good catch!
> > >
> > > --Yakov
> > >
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

[jira] [Created] (IGNITE-5515) GridCacheReplicatedNodeRestartSelfTest hangs

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5515:
---

 Summary: GridCacheReplicatedNodeRestartSelfTest hangs
 Key: IGNITE-5515
 URL: https://issues.apache.org/jira/browse/IGNITE-5515
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 2.1


Sample log: 
http://ci.ignite.apache.org/viewLog.html?buildId=06=buildResultsDiv=Ignite20Tests_IgniteDataGridRestarts

Most probably this is the trigger:
{code}
[23:26:52]W: [org.apache.ignite:ignite-core] [2017-06-15 
20:26:52,349][ERROR][sys-stripe-22-#191189%replicated.GridCacheReplicatedNodeRestartSelfTest3%][GridNearTxLocal]
 Commit failed.
[23:26:52]W: [org.apache.ignite:ignite-core] class 
org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
Commit produced a runtime exception (all transaction entries will be 
invalidated): 
GridDhtTxRemote[id=e8aef6dac51--067f-cbd2--0002, 
concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=COMMITTING, 
invalidate=false, rollbackOnly=false, 
nodeId=64eba958-5741-4cee-ba4b-7ac75d81, duration=0]
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:721)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:790)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1208)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1116)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:95)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:177)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:175)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1032)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:553)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:371)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:301)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:104)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:291)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1095)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
[23:26:52]W: [org.apache.ignite:ignite-core]at 
java.lang.Thread.run(Thread.java:745)
[23:26:52]W: [org.apache.ignite:ignite-core] Caused by: class 
org.apache.ignite.internal.NodeStoppingException: Operation has been cancelled 
(node is stopping).
[23:26:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1313)
[23:26:52]W: 

[jira] [Created] (IGNITE-5514) IgnitePdsCacheRebalancingAbstractTest hangs

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5514:
---

 Summary: IgnitePdsCacheRebalancingAbstractTest hangs
 Key: IGNITE-5514
 URL: https://issues.apache.org/jira/browse/IGNITE-5514
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Dmitriy Govorukhin
 Fix For: 2.1


Affected tests:
{{IgnitePdsCacheRebalancingAbstractTest.testTopologyChangesWithConstantLoadExplicitTx}}
{{IgnitePdsCacheRebalancingAbstractTest.testTopologyChangesWithConstantLoad}}
{{IgnitePdsCacheRebalancingAbstractTest.testRebalancingOnRestartAfterCheckpoint}}

Sample log: 
http://ci.ignite.apache.org/viewLog.html?buildId=664931=buildResultsDiv=Ignite20Tests_IgnitePdsIndexing

No obvious reasons.



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

[jira] [Created] (IGNITE-5513) WalRecoveryTxLogicalRecordsTest is broken, probably due to "inactive" cluster state

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5513:
---

 Summary: WalRecoveryTxLogicalRecordsTest is broken, probably due 
to "inactive" cluster state
 Key: IGNITE-5513
 URL: https://issues.apache.org/jira/browse/IGNITE-5513
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Dmitriy Govorukhin
 Fix For: 2.1


The following tests hang:
{{WalRecoveryTxLogicalRecordsTest.testRecoveryNoPageLost1}}
{{WalRecoveryTxLogicalRecordsTest.testRecoveryNoPageLost2}}
{{WalRecoveryTxLogicalRecordsTest.testRecoveryRandomPutRemove}}
{{WalRecoveryTxLogicalRecordsTest.testWalAfterPreloading}}

The following exception is seen nearby, most probably this is the root cause
{code}
[16:47:05]W: [org.apache.ignite:ignite-indexing] class 
org.apache.ignite.IgniteException: can not perform operation, because cluster 
inactive
[16:47:05]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.IgniteKernal.checkClusterState(IgniteKernal.java:3666)
[16:47:05]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.IgniteKernal.cache(IgniteKernal.java:2712)
[16:47:05]W: [org.apache.ignite:ignite-indexing]at 
org.apache.ignite.internal.processors.cache.persistence.db.wal.WalRecoveryTxLogicalRecordsTest.testFreeListRecovery(WalRecoveryTxLogicalRecordsTest.java:775)
[16:47:05]W: [org.apache.ignite:ignite-indexing]at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[16:47:05]W: [org.apache.ignite:ignite-indexing]at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
{code}:



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

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

[Denis Magda]

Meeting details have beed added to the site:
https://ignite.apache.org/news.html#meetup-an-overview-of-ignite-persistent-store
 


You can see a reference in “News & Events” block on the main page.

—
Denis

> On Jun 13, 2017, at 1:30 PM, Dmitriy Setrakyan  wrote:
> 
> On Tue, Jun 13, 2017 at 11:53 AM, Denis Magda  wrote:
> 
>> It’s not intended to be a public event but rather a meeting of Ignite’s
>> committers and contributors to discuss the store. This is why I personally
>> prefer not going out of the dev list boundaries.
>> 
> 
> If you post on the website, with instructions on how to join, it will make
> it easier for the community. On top of that, some folks who are not
> currently in the community  may join as well.
> 
> 
>> —
>> Denis
>> 
>>> On Jun 13, 2017, at 11:36 AM, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Denis, any chance you can post info for this webinar on the website?
>>> 
>>> On Tue, Jun 13, 2017 at 10:05 AM, Denis Magda  wrote:
>>> 
 Roman,
 
 Sure, will do.
 
 —
 Denis
 
> On Jun 12, 2017, at 8:35 PM, Roman Shtykh 
 wrote:
> 
> Denis,
> Can you please share slides (or video) after the webinar? I would like
 to attend it but it's midnight in Japan.
> -- Roman
> 
> 
> 
>  On Tuesday, June 13, 2017 7:56 AM, Denis Magda 
 wrote:
> 
> 
> Good, we have a quorum then ;)
> 
> I plan to schedule webinar for this Friday, June 16th, 8.00 - 9.00 AM
 Pacific Time. If nobody steps up proposing more suitable time I’ll send
>> the
 webinar details tomorrow.
> 
> —
> Denis
> 
>> On Jun 11, 2017, at 8:15 PM, Konstantin Boudnik 
>> wrote:
>> 
>> Guys,
>> 
>> I will most like have 10-15 developers from EPAM attending this.
>> Mostly
 people
>> who are working on the seamless snapshotting and the replication
 system, but a
>> few others as well.
>> 
>> Thanks for setting this up!
>> Cos
>> 
>> On Thu, Jun 08, 2017 at 12:54PM, Denis Magda wrote:
>>> Igniters,
>>> 
>>> What’d you think if we arrange an internal webinar for our community
 to walk
>>> through the features, capabilities and implementation details of the
 Ignite
>>> Persistent Store [1]? That should help us understanding the donation
 better.
>>> 
>>> Please reply if you will be happy to attend.
>>> 
>>> [1] https://apacheignite.readme.io/docs/distributed-persistent-store
>> <
 https://apacheignite.readme.io/docs/distributed-persistent-store>
>>> 
>>> —
>>> Denis
> 
> 
 
 
>> 
>> 

[jira] [Created] (IGNITE-5512) AssertionError: GridDhtPartitionsExchangeFuture

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5512:
---

 Summary: AssertionError: GridDhtPartitionsExchangeFuture
 Key: IGNITE-5512
 URL: https://issues.apache.org/jira/browse/IGNITE-5512
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 2.1


Reproducer: {{IgniteDynamicCacheStartSelfTest.testStartStopWithClientJoin}}
Sample log: 
http://ci.ignite.apache.org/viewLog.html?buildId=664862=buildResultsDiv=Ignite20Tests_IgniteCache4

Stack trace:
{code}
[17:30:52]W: [org.apache.ignite:ignite-core] Exception in thread 
"exchange-worker-#12653%cache.IgniteDynamicCacheStartSelfTest3%" 
java.lang.AssertionError: GridDhtPartitionsExchangeFuture [dummy=false, 
forcePreload=false, reassign=false, discoEvt=DiscoveryCustomEvent 
[customMsg=null, affTopVer=AffinityTopologyVersion [topVer=30, minorTopVer=2], 
super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=94a7350b-cae3-4381-a458-55e55001, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
lastExchangeTime=1497537052792, loc=false, ver=2.1.0#19700101-sha1:, 
isClient=false], topVer=30, nodeId8=24ab11ae, msg=null, 
type=DISCOVERY_CUSTOM_EVT, tstamp=1497537052823]], crd=TcpDiscoveryNode 
[id=1d00ae44-d805-4edc-a49f-e4630c70, addrs=[127.0.0.1], 
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1497537052792, loc=false, ver=2.1.0#19700101-sha1:, 
isClient=false], exchId=GridDhtPartitionExchangeId 
[topVer=AffinityTopologyVersion [topVer=30, minorTopVer=2], nodeId=94a7350b, 
evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter 
[ignoreInterrupts=false, state=DONE, res=false, hash=1608702177], init=false, 
lastVer=null, partReleaseFut=null, exchActions=null, affChangeMsg=null, 
skipPreload=true, clientOnlyExchange=false, initTs=1497537052823, 
centralizedAff=false, changeGlobalStateE=null, 
exchangeOnChangeGlobalState=false, forcedRebFut=null, done=true, evtLatch=0, 
remaining=[1d00ae44-d805-4edc-a49f-e4630c70, 
e0eb00f0-1f63-4aa6-8c70-60a4b352, 94a7350b-cae3-4381-a458-55e55001], 
super=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=class 
org.apache.ignite.internal.IgniteInterruptedCheckedException: Node is stopping: 
cache.IgniteDynamicCacheStartSelfTest3, hash=1631759081]]
[17:30:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:569)
[17:30:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1858)
[17:30:52]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[17:30:52]W: [org.apache.ignite:ignite-core]at 
java.lang.Thread.run(Thread.java:745)
{code}



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

[jira] [Created] (IGNITE-5511) AssertionError: Handler for class already registered

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5511:
---

 Summary: AssertionError: Handler for class already registered
 Key: IGNITE-5511
 URL: https://issues.apache.org/jira/browse/IGNITE-5511
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 2.1


Reproducer: {{CacheLateAffinityAssignmentTest.testRandomOperations}}
Sample log: 
http://ci.ignite.apache.org/viewLog.html?buildId=666034=buildResultsDiv=Ignite20Tests_IgniteCache5

Stack trace:
{code}
[19:13:29]W: [org.apache.ignite:ignite-core] Exception in thread 
"exchange-worker-#54313%client-1%" java.lang.AssertionError: Handler for class 
already registered [hndId=151442180, cls=class 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtAffinityAssignmentResponse,
 
old=org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$2@5cc87411,
 
new=org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$2@6c3c37ad]
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.addHandler(GridCacheIoManager.java:1419)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.addCacheGroupHandler(GridCacheIoManager.java:1376)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheGroupCreated(CacheAffinitySharedManager.java:331)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:870)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1918)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1843)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCacheStartRequests(CacheAffinitySharedManager.java:407)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCachesChanges(CacheAffinitySharedManager.java:576)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:406)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:1752)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1835)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[19:13:29]W: [org.apache.ignite:ignite-core]at 
java.lang.Thread.run(Thread.java:745)
{code}



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

[jira] [Created] (IGNITE-5510) AssertionError: null instead of GridCacheReturnCompletableWrapper

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5510:
---

 Summary: AssertionError: null instead of 
GridCacheReturnCompletableWrapper
 Key: IGNITE-5510
 URL: https://issues.apache.org/jira/browse/IGNITE-5510
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 2.1


Reproducer: {{CacheLateAffinityAssignmentTest#testNoForceKeysRequests}}
Sample log: 
http://ci.ignite.apache.org/viewLog.html?buildId=666034=buildResultsDiv=Ignite20Tests_IgniteCache5

Stack trace:
{code}
java.lang.AssertionError: null instead of GridCacheReturnCompletableWrapper
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.removeTxReturn(IgniteTxManager.java:1040)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxOnePhaseCommitAckRequest(IgniteTxHandler.java:1070)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$700(IgniteTxHandler.java:95)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$8.apply(IgniteTxHandler.java:183)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$8.apply(IgniteTxHandler.java:181)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1032)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:553)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:371)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:301)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:104)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:291)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1095)
at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
at java.lang.Thread.run(Thread.java:745)
{code}



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

[jira] [Created] (IGNITE-5509) Test CacheLateAffinityAssignmentTest#testRandomOperations() is hanging

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5509:
---

 Summary: Test 
CacheLateAffinityAssignmentTest#testRandomOperations() is hanging
 Key: IGNITE-5509
 URL: https://issues.apache.org/jira/browse/IGNITE-5509
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Pavel Kovalenko
Priority: Critical
 Fix For: 2.1


Error:

{noformat}
[ERROR][exchange-worker-#30%server-1%][GridCachePartitionExchangeManager] 
Runtime error caught during grid runnable execution: GridWorker 
[name=partition-exchanger, igniteInstanceName=server-1, finished=false, 
hashCode=523538103, interrupted=false, runner=exchange-worker-#30%server-1%]
java.lang.AssertionError: Handler for class already registered 
[hndId=151442180, cls=class 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtAffinityAssignmentRequest,
 old=org.apache.ignite.internal.processors.cache.CacheGroupContext$2@2eec0c42, 
new=org.apache.ignite.internal.processors.cache.CacheGroupContext$2@1048d9d4]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.addHandler(GridCacheIoManager.java:1420)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.addCacheGroupHandler(GridCacheIoManager.java:1376)
at 
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:840)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1926)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1851)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCacheStartRequests(CacheAffinitySharedManager.java:407)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCachesChanges(CacheAffinitySharedManager.java:576)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:406)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:1764)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1847)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Exception in thread "exchange-worker-#30%server-1%" java.lang.AssertionError: 
Handler for class already registered [hndId=151442180, cls=class 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtAffinityAssignmentRequest,
 old=org.apache.ignite.internal.processors.cache.CacheGroupContext$2@2eec0c42, 
new=org.apache.ignite.internal.processors.cache.CacheGroupContext$2@1048d9d4]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.addHandler(GridCacheIoManager.java:1420)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.addCacheGroupHandler(GridCacheIoManager.java:1376)
at 
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:840)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1926)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1851)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCacheStartRequests(CacheAffinitySharedManager.java:407)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCachesChanges(CacheAffinitySharedManager.java:576)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:406)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:1764)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1847)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{noformat}




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

[jira] [Created] (IGNITE-5508) Document Web Console Installation from Docker Image

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5508:
---

 Summary: Document Web Console Installation from Docker Image
 Key: IGNITE-5508
 URL: https://issues.apache.org/jira/browse/IGNITE-5508
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
Assignee: Alexey Kuznetsov
 Fix For: 2.1


We need to add a section to the very beginning of the doc below explaining how 
to install and set up the console from the Docker image:
https://apacheignite-tools.readme.io/docs/build-and-deploy





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

[jira] [Created] (IGNITE-5507) .NET: IIgnite.Active

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5507:
--

 Summary: .NET: IIgnite.Active
 Key: IGNITE-5507
 URL: https://issues.apache.org/jira/browse/IGNITE-5507
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.1






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

Re: Cassandra related SO question

[Igor Rudyak]

I'll look it it.

Igor

On Thu, Jun 15, 2017 at 3:24 AM, Igor Sapego  wrote:

> Igor,
>
> Can you please take a look at this question at SO?
>
> https://stackoverflow.com/questions/44512192/ignite-put-
> function-for-cassandra-malfunction-in-c
>
> Best Regards,
> Igor
>

[GitHub] ignite pull request #2138: Ignite 1219

[ntikhonov]

GitHub user ntikhonov opened a pull request:

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

Ignite 1219



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

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

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

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


commit 18598574bb2992aa193eed1d72ca333a1e21ad72
Author: Andrey V. Mashenkov 
Date:   2016-12-08T09:36:07Z

GG-11746: Backport of IGNITE-4379:  Fixed broken local SqlFieldsQuery.

commit 671a77a2d81cac401765dddf25f30fba4e4ab17f
Author: sboikov 
Date:   2016-12-08T09:56:46Z

ignite-4154 Fixed node version check for compression feature usage

commit 391f4be4c687a7f325aeec8b727c9c85ca003454
Author: agura 
Date:   2016-12-07T17:11:50Z

ignite-2358 toString() method for cache store implementations

commit bc977d3211906ef94e1f7d3f0f988efbed65034f
Author: Alexey Kuznetsov 
Date:   2016-12-09T09:11:31Z

IGNITE-4350 Reworked JdbcTypesDefaultTransformed logic. Improved improved 
error messages in CacheJdbcPojoStore.

commit b83ec8e57c7c48f2baa4780cf3b2e46df075f3df
Author: sboikov 
Date:   2016-12-09T11:32:42Z

IGNITE-500 CacheLoadingConcurrentGridStartSelfTest fails: prevent 
'localUpdate' execution while top read lock is held.

commit 6e485637e2738a7e809eac1a802f0964dc12383d
Author: Andrey V. Mashenkov 
Date:   2016-12-09T12:42:40Z

IGNITE-4379: Fixed local query execution. This closes #1323.

commit 6fd8bf6338470275e687a686044c7d935d3714ff
Author: Andrey V. Mashenkov 
Date:   2016-12-07T15:49:06Z

Fixed tests for IGNITE-4379 commit.

commit c143bc1a77baa13f61d6ba00509fa1fcb33757b1
Author: tledkov-gridgain 
Date:   2016-12-09T13:05:03Z

IGNITE-4063:  Preserved order of fields in the metadata according with 
schema. This closes #1270.

commit 6616a878598b8ed74b71558290a22b266a8ac03e
Author: devozerov 
Date:   2016-12-09T13:05:24Z

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

commit f087b661c466c9fd27d049efa8e55a2d7bdf9834
Author: Andrey V. Mashenkov 
Date:   2016-12-09T14:45:33Z

IGNITE-4264: Fixed cluster wide cache metrics. This closes #1336.

commit ceb60d27d38782d82ec5275a56a6f77851b6
Author: Andrey V. Mashenkov 
Date:   2016-12-09T14:46:21Z

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

commit 6d744db27111c68e13b06ec99428a4c4148d97b6
Author: dkarachentsev 
Date:   2016-12-12T08:44:57Z

IGNITE-4231 - Hangs on compute result serialization error. Fix

commit eeb2f2a38fb792b711eb665e380d14bc00f6e078
Author: dkarachentsev 
Date:   2016-12-12T09:14:01Z

IGNITE-3862 - GridServiceProxy invocation never times out. Fix

commit 8dd4ada6287af49a243aba1e58daffa7e44f39a9
Author: sboikov 
Date:   2016-12-12T11:56:44Z

GridClosureProcessor: fixed javadoc.

commit 83d961cff88cf2ead0bbc4ded3285f4faf9157fc
Author: Pavel Tupitsyn 
Date:   2016-12-12T14:52:22Z

IGNITE-4413 .NET: Fix DateTime argument handling in SqlQuery

This closes #1341

# Conflicts:
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/Query/CacheQueriesCodeConfigurationTest.cs

commit 83710a9d1bb7379e5f3d891ed95c86096263740b
Author: Pavel Tupitsyn 
Date:   2016-12-12T14:52:22Z

IGNITE-4413 .NET: Fix DateTime argument handling in SqlQuery

This closes #1341

commit bf1770bcebfb17d36ac90e157373901b5a181c05
Author: Igor Sapego 
Date:   2016-12-14T09:26:27Z

IGNITE-4421: Added BinaryObject handling in ODBC. Added test.

commit ae903c59c10bb9fad58842221f3e720d1b4d54b8
Author: devozerov 
Date:   2016-12-05T11:57:25Z

IGNITE-4276: Hadoop: added configurable throttle for shuffle message 
sending. Disabled by default.

commit 2488f340c85301c0ec39cac80a8426f5f4c3caf0
Author: devozerov 
Date:   2016-12-05T12:28:54Z

IGNITE-4274: Hadoop: added new property to control shuffle message size.

commit 3c384212603dd31b933205d1c127dc9d0f1785e1
Author: devozerov 
Date:   2016-12-05T12:42:24Z

IGNITE-4295: Added specialized methods for memory copying, depending on 
their nature (heap/offheap). Heap->heap copying is now performed using 
System.arraycopy when possible. Also it is possible to fallback to byte-by-byte 
copying until certain threshold is reached (see 

[jira] [Created] (IGNITE-5506) Datagrid.StoreExample fails when run with standalone Apache Ignite.NET node

[Irina Zaporozhtseva (JIRA)]

Irina Zaporozhtseva created IGNITE-5506:
---

 Summary: Datagrid.StoreExample fails when run with standalone 
Apache Ignite.NET node
 Key: IGNITE-5506
 URL: https://issues.apache.org/jira/browse/IGNITE-5506
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.1
Reporter: Irina Zaporozhtseva


Datagrid.StoreExample fails when run with standalone Apache Ignite.NET node

Apache.Ignite.Core.Cache.CacheException was unhandled
  HResult=-2146233088
  Message=class org.apache.ignite.IgniteCheckedException: Could not load file 
or assembly 'Apache.Ignite.ExamplesDll, Version=1.0.6375.29467, 
Culture=neutral, PublicKeyToken=c27524977cb332ce' or one of its dependencies. 
The system cannot find the file specified.
  Source=Apache.Ignite.Core
  StackTrace:
   at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* 
target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte* 
errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32 
stackTraceCharsLen, Void* errData, Int32 errDataLen)
   at 
Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.TargetInLongOutLong(Void*
 ctx, Void* target, Int32 opType, Int64 val)
   at 
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInLongOutLong(IUnmanagedTarget
 target, Int32 opType, Int64 memPtr)
   at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.Clear()
   at Apache.Ignite.Examples.Datagrid.StoreExample.Main() in 
C:\work\gridgain-professional-fabric-2.1.1.b3_23\platforms\dotnet\examples\Apache.Ignite.Examples\Datagrid\StoreExample.cs:line
 67
   at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] 
args)
   at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence 
assemblySecurity, String[] args)
   at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext 
executionContext, ContextCallback callback, Object state, Boolean 
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, ContextCallback callback, Object state, Boolean 
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
  InnerException: 
   HResult=-2146233088
   Message=Could not load file or assembly 'Apache.Ignite.ExamplesDll, 
Version=1.0.6375.29467, Culture=neutral, PublicKeyToken=c27524977cb332ce' or 
one of its dependencies. The system cannot find the file specified.
   InnerException: 
HResult=-2146233088
JavaClassName=javax.cache.CacheException
JavaMessage=class org.apache.ignite.IgniteCheckedException: Could 
not load file or assembly 'Apache.Ignite.ExamplesDll, Version=1.0.6375.29467, 
Culture=neutral, PublicKeyToken=c27524977cb332ce' or one of its dependencies. 
The system cannot find the file specified.
Message=javax.cache.CacheException: class 
org.apache.ignite.IgniteCheckedException: Could not load file or assembly 
'Apache.Ignite.ExamplesDll, Version=1.0.6375.29467, Culture=neutral, 
PublicKeyToken=c27524977cb332ce' or one of its dependencies. The system cannot 
find the file specified.
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1323)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:2629)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.clear(IgniteCacheProxy.java:2049)
at 
org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInLongOutLong(PlatformCache.java:1088)
at 
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inLongOutLong(PlatformTargetProxyImpl.java:53)
Caused by: class org.apache.ignite.IgniteCheckedException: Could not load file 
or assembly 'Apache.Ignite.ExamplesDll, Version=1.0.6375.29467, 
Culture=neutral, PublicKeyToken=c27524977cb332ce' or one of its dependencies. 
The system cannot find the file specified.
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7229)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:170)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
at 
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:166)
at 
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.clearLocally(GridCacheProxyImpl.java:974)
at 

[GitHub] ignite pull request #2137: MemoryMetricsTest fix

[sergey-chugunov-1985]

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

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

MemoryMetricsTest fix



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

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

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

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


commit 30ba7698dfcf2e9eb4376afb704e0ab615ffde5e
Author: EdShangGG 
Date:   2017-04-25T15:48:07Z

fixing isFirstJvm method

commit 401b7a0b76e8372841e4170b14de75da7f45fa76
Author: Ilya Lantukh 
Date:   2017-04-25T16:30:03Z

ignite-5068 : Fixed diff calculation, added workaround when requested 
affVer != diffFromAffinityVer.

commit a011f575e7fa974f33d6adbf18a3a4fa32c197d0
Author: Ilya Lantukh 
Date:   2017-04-27T13:50:00Z

ignite-5068 : WIP.

commit c67dc6f81c3c69fd58c3440fd8ab524edbd18d8d
Author: Ilya Lantukh 
Date:   2017-04-28T11:06:01Z

ignite-5068 : WIP.

commit cc528344169ab89453ad376a3ee8ff2b56a7513f
Author: Ilya Lantukh 
Date:   2017-04-28T12:48:30Z

ignite-5068 : WIP.

commit 03586bc7c75e4b18aba9bdb875e5a7d7a77de062
Author: Ilya Lantukh 
Date:   2017-04-28T13:01:12Z

ignite-5068 : WIP.

commit 8374f6c919c3ba46a8138af7638a000e4c22778b
Author: Ilya Lantukh 
Date:   2017-04-28T14:02:03Z

ignite-5068 : First stable solution.

commit 3a10973e3555ea1bd23f59da84b936db1b656755
Author: Ilya Lantukh 
Date:   2017-04-28T14:34:31Z

ignite-5068 : Optimized loop.

commit 58f1998afbf921eea352ac0d9d409de2a342b68a
Author: Ilya Lantukh 
Date:   2017-04-28T14:56:15Z

Merge branch 'master' of https://github.com/apache/ignite into ignite-5068

commit 0955308b8832200aa8ac86c84e967c1d50ebefb1
Author: Ilya Lantukh 
Date:   2017-04-28T15:19:50Z

ignite-5068 : Cosmetic changes.

commit 0fd7ca27ebd3e144f64f11417558f691eb4d62f2
Author: Dmitriy Govorukhin 
Date:   2017-05-02T15:55:34Z

ignite-gg-12163 dirty replace snapshot and and grid shared manager

commit 6d22a91e412943d80c440e89b52d808ac0d5fdb1
Author: Dmitriy Govorukhin 
Date:   2017-05-03T08:59:27Z

ignite-gg-12163 code style refactoring

commit 28edd6171f273eb3e039d42135cae2fb89a4e3df
Author: Ivan Rakov 
Date:   2017-05-03T12:04:10Z

GG-12118: Tests affected by DDL implementation

commit c0da061f90dcd56f345c3c70a49bd82f0f5e6111
Author: Dmitriy Govorukhin 
Date:   2017-05-03T12:29:21Z

ignite-gg-12163  refactoring updates, move copy page to snapshot manager

commit c4deff8f59ba39802502284acb3a40c745e13844
Author: EdShangGG 
Date:   2017-05-03T16:32:51Z

fixing issue with message id

commit 0a1939b97fcb4197d3fbbeafc9d69ad62c2e83e7
Author: Sergey Chugunov 
Date:   2017-05-04T12:15:36Z

first compilable version of PDS code

commit 52f5004007bb7a3716f29ecb438d5a590b608764
Author: Sergey Chugunov 
Date:   2017-05-04T12:16:14Z

Merge branch 'ignite-gg-12163' of https://github.com/gridgain/apache-ignite 
into ignite-gg-12163

commit dfc35388d45ea2596d9a9e855f9e4a5ed8fa13cd
Author: Sergey Chugunov 
Date:   2017-05-04T14:25:15Z

first although failing test for PDS functionality

commit 984f35f4a1e3ddec24cfa0bc86f6256055dc42d0
Author: Dmitriy Govorukhin 
Date:   2017-05-04T14:35:13Z

ignite-12163 final move pds

commit d0ee7ad8ed69d40da7215a122c01af01fead6a2f
Author: Dmitriy Govorukhin 
Date:   2017-05-04T14:35:58Z

Merge remote-tracking branch 'professional/ignite-gg-12163' into 
ignite-gg-12163

commit 8f85be55769f18c4d5ff2182dc1acb88c7cdd1a9
Author: Sergey Chugunov 
Date:   2017-05-04T14:38:44Z

header removed

commit 9a0ad843f20d82e800cd9934ea1ca19f88d92db9
Author: Dmitriy Govorukhin 
Date:   2017-05-04T14:40:22Z

ignite-12163 header revert

commit b0e4a92e8e1b9f236a76612737d7fc3613d5dd8f
Author: Dmitriy Govorukhin 
Date:   2017-05-04T14:40:42Z

Merge remote-tracking branch 'professional/ignite-gg-12163' into 
ignite-gg-12163

commit 4d55ba1202f5bf1ab32ad9e840b4a6144dba1295
Author: Sergey Chugunov 
Date:   2017-05-04T16:13:49Z

changes to CacheProcessor, first test passing (although assertion exception 
in logs)

commit 9fc4054b62d6d1381d2bc13a120a0c22a982f384
Author: Sergey Chugunov 
Date:   2017-05-04T16:15:31Z

[jira] [Created] (IGNITE-5505) @AffinityKeyMapped annotation is ignored if class names are configured on BinaryConfiguration

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-5505:
---

 Summary: @AffinityKeyMapped annotation is ignored if class names 
are configured on BinaryConfiguration
 Key: IGNITE-5505
 URL: https://issues.apache.org/jira/browse/IGNITE-5505
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Andrey Gura


{{@AffinityKeyMapped}} annotation on key class field is ignored in case when 
class names passed to {{inaryConfiguration}} via {{setClassNames()}} method.

The problem is that Ignite uses {{IgniteConfiguration.cacheKeyCfg}} during 
{{BinaryContext.configure()}} execution and doesn't check class fileds on 
{{@AffinityKeyMapped}} annotation.

Possible solution: check class fields on {{@AffinityKeyMapped}} annotation if 
there is no any mapping for cache key type.



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

[GitHub] ignite pull request #2136: IGNITE-5377 ODBC: Exposed SqlFieldsQuery hints as...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-5377 ODBC: Exposed SqlFieldsQuery hints as parameters.



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

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

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

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


commit 9ba3769e689685e1ce704d63dd9f66a651c2b1d9
Author: Igor Sapego 
Date:   2017-06-15T13:18:58Z

IGNITE-5377: Added hints to driver

commit b28b8af7440433cf889e9f99d045f46589484a89
Author: Igor Sapego 
Date:   2017-06-15T13:29:45Z

IGNITE-5377: Added handling of flags in ODBC processor.




---
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-5504) Failures in GridTcpCommunicationSpiRecoverySelfTest

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5504:
---

 Summary: Failures in GridTcpCommunicationSpiRecoverySelfTest
 Key: IGNITE-5504
 URL: https://issues.apache.org/jira/browse/IGNITE-5504
 Project: Ignite
  Issue Type: Bug
Reporter: Vladimir Ozerov
 Fix For: 2.1


Reproducible only on TeamCity.

Affected tests:
{{GridTcpCommunicationSpiRecoverySelfTest.testBlockRead1}}
{{GridTcpCommunicationSpiRecoverySelfTest.testBlockRead2}}
{{GridTcpCommunicationSpiRecoverySelfTest.testBlockRead3}}

Root cause:
{code}
[2017-06-14 18:16:30,016][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError: Failed to wait for session close
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at 
org.apache.ignite.spi.communication.tcp.GridTcpCommunicationSpiRecoverySelfTest.testBlockRead1(GridTcpCommunicationSpiRecoverySelfTest.java:333)
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:1992)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:131)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1907)
at java.lang.Thread.run(Thread.java:745)
{code}



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

[GitHub] ignite pull request #2106: IGNITE-4370: Implemented writing of batch of para...

[isapego]

Github user isapego closed the pull request at:

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


---
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 #2127: IGNITE-5484 DataStructuresCacheKey and DataStruct...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-5503) Affinity information for cache is not cleared after cache destroy

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5503:
---

 Summary: Affinity information for cache is not cleared after cache 
destroy
 Key: IGNITE-5503
 URL: https://issues.apache.org/jira/browse/IGNITE-5503
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Pavel Kovalenko
Priority: Critical
 Fix For: 2.1


Test CacheLateAffinityAssignmentTest#testCacheDestroyAndCreate2

Error:

{noformat}
[16:43:38] (err) Failed to notify listener: 
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$4@40ba6d7e[16:43:38]
 (err) Failed to notify listener: 
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$4...@22c13489java.lang.AssertionError:
 Affinity partition is out of range [part=10, partitions=10]
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignment.getIds(GridAffinityAssignment.java:163)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.update(GridDhtPartitionTopologyImpl.java:1157)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionFullMap(GridDhtPartitionsExchangeFuture.java:1926)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processMessage(GridDhtPartitionsExchangeFuture.java:1898)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$700(GridDhtPartitionsExchangeFuture.java:107)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$4.apply(GridDhtPartitionsExchangeFuture.java:1869)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$4.apply(GridDhtPartitionsExchangeFuture.java:1857)
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.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1857)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processFullPartitionUpdate(GridCachePartitionExchangeManager.java:1301)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1400(GridCachePartitionExchangeManager.java:124)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:329)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$3.onMessage(GridCachePartitionExchangeManager.java:327)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2197)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2179)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1032)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:553)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:371)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:301)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:104)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:291)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1095)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
java.lang.AssertionError: Affinity partition is out of range [part=12, 
partitions=10]
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignment.getIds(GridAffinityAssignment.java:163)
at 

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

[ilantukh]

GitHub user ilantukh opened a pull request:

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

Data structures redesign based on cache groups



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

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

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

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


commit b1719ac58927032bc0a3608e781fa2b7b24163a3
Author: Dmitriy Govorukhin 
Date:   2017-05-05T11:32:08Z

ignite-12163 minor update configuration

commit 92a490d7f5ca18ceb5b6fdf6364aa2e194d83f14
Author: Dmitriy Govorukhin 
Date:   2017-05-05T12:10:59Z

ignite-12163 remove unnecessary delegate

commit f9fdd2c0d146da489e4c2a2b40f1736f7a15fad4
Author: Dmitriy Govorukhin 
Date:   2017-05-05T12:17:28Z

ignite-12163 remove unnecessary delegate

commit 9cf52ace2943eb8a48ab944f449691e2c5b72982
Author: Dmitriy Govorukhin 
Date:   2017-05-05T12:20:59Z

ignite-12163 fix error on start

commit e224ff026121c59b348d260cd98b97fa298b9200
Author: EdShangGG 
Date:   2017-05-03T16:32:51Z

fixing issue with message id

(cherry picked from commit c4deff8)

commit 1aa2fe740c2d1db9f98aeeaa88844e9baecc1953
Author: Dmitriy Govorukhin 
Date:   2017-05-08T09:11:02Z

ignite-gg-12163 fix testWalDirectOutOfMemory

commit ce32505e352a72b1fd9ef04bf1d65d13cfaab669
Author: Dmitriy Govorukhin 
Date:   2017-05-08T09:40:32Z

ignite-gg-12163 minor refactoring updates

commit f6ea4a1b2269ac97708860afceb84da2f31f1a29
Author: Dmitriy Govorukhin 
Date:   2017-05-08T11:15:34Z

ignite-gg-12163 fix oom in test

commit a383df739163fac9525730a3ecdca0213d358142
Author: Dmitriy Govorukhin 
Date:   2017-05-08T12:20:57Z

ignite-gg-12163 provide callback handler, flush or evict page for snapshot 
Manager

commit c51de7fbe170a9d0e44c1943a509ff0b27944ab4
Author: Dmitriy Govorukhin 
Date:   2017-05-08T12:31:12Z

ignite-gg-12163 remove unnecessary method in dbSharedManager

commit 0c37da097830bab64ab9983f77d37c8d51cca101
Author: Dmitriy Govorukhin 
Date:   2017-05-09T11:01:15Z

ignite-gg-12163 test refactoring

commit a14a594d2168c7e5bda56bc0cdc2492c5ffc1f82
Author: Dmitriy Govorukhin 
Date:   2017-05-09T12:27:17Z

ignite-gg-12163 provide cache name

commit c3874579ea9d03342161b0f5c33052d6570e7ad0
Author: Dmitriy Govorukhin 
Date:   2017-05-10T13:45:57Z

ignite-12163 simplify snapshot callback

commit c60118daf9f185db2eab4c742da299dc98aa7ae2
Author: Dmitriy Govorukhin 
Date:   2017-05-10T13:56:44Z

ignite-12163 minor renaming

commit 8004287cfef875089a926a5422ebe09e4dc0ad7b
Author: Sergey Chugunov 
Date:   2017-05-10T14:40:24Z

IGNITE-GG-12163 IgniteComponentType mechanism employed to instantiate PDS 
managers

commit 79a510dce099f5fc77040cf51f5b21de564f4abf
Author: Sergey Chugunov 
Date:   2017-05-10T14:40:38Z

Merge branch 'ignite-gg-12163' of https://github.com/gridgain/apache-ignite 
into ignite-gg-12163

commit 2e3e97141502a3e4120d46ef314f8d3ac368e050
Author: Dmitriy Govorukhin 
Date:   2017-05-11T08:17:07Z

ignite-12163 remove completeSavingAllocatedIndex method, add  test for 
fullPageIdTable

commit 1cce2fcc960c5098cc684b6138ed306daf5dd5e4
Author: Sergey Chugunov 
Date:   2017-05-11T12:33:05Z

IGNITE-GG-12163 test dependencies were cleaned up in pom file

commit 94a305332882113bc68e6feb0263d104f0c673ad
Author: Alexey Kuznetsov 
Date:   2017-05-12T09:31:04Z

GG-11898 Fixed VisorSnapshotsStatusTask.

commit 96c293caa79f8d448077e1c7272df371cadaa0d2
Author: Dmitriy Govorukhin 
Date:   2017-05-12T16:50:41Z

IGNITE-GG-12163 (revert) test dependencies were cleaned up in pom file

commit 38e9baa883f9f626ea477c9e935954d31a7134cb
Author: Alexey Goncharuk 
Date:   2017-05-15T08:53:53Z

Merged ignite-2.0 into gg-8.0.4.ea2

commit 9b7c4ac8f337e8af7b8ef1dfab7e1ee86357bc7c
Author: Ivan Rakov 
Date:   2017-05-02T13:40:57Z

IGNITE-5134: Explicit cast to PageMemoryNoStoreImpl in 
IgniteCacheDatabaseSharedManager (cherry picked from commit 77a2c20)

commit 5eea8adaf2f5d4d39e5a629dc3261988ab6669c0
Author: Sergey Chugunov 
Date:   2017-05-16T07:59:02Z

apache headers are added, RAT checks pass

commit 

Re: Data compression in Ignite 2.0

[Vyacheslav Daradur]

Hi Igniters.

Vladimir, I want to propose another design of an implementation of the
per-field compression.

1) We will add new step in the method prepareForCache (for example) of
CacheObject, or in GridCacheMapEntry.

At the step, after marshalling of an object, we will compress fields of the
object which described in advance.
User will describe class fields which he wants to compess in an another
entity like Metadata.

For compression, we will introduce another entity, for example
CompressionProcessor, which will work with bytes array (marshalled object).
The entity will read bytes array of described fields, compress it and
rewrite binary representation of the whole object.
After processing the object will be put in the cache.

In this case design not to relate to binary infrastructure.
But there is big overhead to heap-memory for the buffer.

2) Another solution is to compress bytes array of whole object on copying
to off-heap.
But, in this case I don't understand yet, how to provide support of
querying and indexing.


2017-06-09 11:21 GMT+03:00 Sergey Kozlov :

> Hi
>
> * "Per-field compression" is applicable for huge BLOB fields and will
> impose the restrictions like unable ot index such fields, slower getting
> data, potential OOM issues if compression ration is too high.
> But for some cases it makes sense
>
> On Fri, Jun 9, 2017 at 11:11 AM, Антон Чураев 
> wrote:
>
> > Seems that Dmitry is referring to transparent data encryption. It is used
> > throughout the whale database industry.
> >
> > 2017-06-09 10:50 GMT+03:00 Vladimir Ozerov :
> >
> > > Dima,
> > >
> > > Encryption of certain fields is as bad as compression. First, it is a
> > huge
> > > change, which makes already complex binary protocol even more complex.
> > > Second, it have to be ported to CPP, .NET platforms, as well as to JDBC
> > and
> > > ODBC.
> > > Last, but the most important - this is not our headache to encrypt
> > > sensitive data. This is user responsibility. Nobody in a sane mind will
> > > store passwords in plain form. Instead, user should encrypt it on his
> > own,
> > > choosing proper encryption parameters - algorithms, key lengths, salts,
> > > etc.. How are you going to expose this in API or configuration?
> > >
> > > We should not implement data encryption on binary level, this is out of
> > > question. Encryption should be implemented on application level (user
> > > efforts), transport layer (SSL - we already have it), and possibly on
> > > disk-level (there are tools for this already).
> > >
> > >
> > > On Fri, Jun 9, 2017 at 9:06 AM, Vyacheslav Daradur <
> daradu...@gmail.com>
> > > wrote:
> > >
> > > > >> which is much less useful.
> > > > I note, in some cases there is profit more than twice per size of an
> > > > object.
> > > >
> > > > >> Would it be possible to change your implementation to handle the
> > > > encryption instead?
> > > > Yes, of cource, there's not much difference between compression and
> > > > encryption, including in my implementation of per-field-compression.
> > > >
> > > > 2017-06-09 8:55 GMT+03:00 Dmitriy Setrakyan :
> > > >
> > > > > Vyacheslav,
> > > > >
> > > > > When this feature started out as data compression in Ignite, it
> > sounded
> > > > > very useful. Now it is unfolding as a per-field compression, which
> is
> > > > much
> > > > > less useful. In fact, it is questionable whether it is useful at
> all.
> > > The
> > > > > fact that this feature is implemented does not make it mandatory
> for
> > > the
> > > > > community to accept it.
> > > > >
> > > > > However, as I mentioned before, per-field encryption is very
> useful,
> > as
> > > > it
> > > > > would allow users automatically encrypt certain sensitive fields,
> > like
> > > > > passwords, credit card numbers, etc. There is not much conceptual
> > > > > difference between compressing a field vs encrypting a field. Would
> > it
> > > be
> > > > > possible to change your implementation to handle the encryption
> > > instead?
> > > > >
> > > > > D.
> > > > >
> > > > > On Thu, Jun 8, 2017 at 10:42 PM, Vyacheslav Daradur <
> > > daradu...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Guys, I want to be clear:
> > > > > > * "Per-field compression" design is the result of a research of
> the
> > > > > binary
> > > > > > infrastructure of Ignite and some other its places (querying,
> > > indexing,
> > > > > > etc.)
> > > > > > * Full-compression of object will be more effective, but in this
> > case
> > > > > there
> > > > > > is no capability with querying and indexing (or there is large
> > > overhead
> > > > > by
> > > > > > way of decompressing of full object (or caches pages) on demand)
> > > > > > * "Per-field compression" is a one of ways to implement the
> > > compression
> > > > > > feature
> > > > > >
> > > > > > I'm new to Ignite also I can be mistaken in some things.
> > > > > > Last 3-4 month I've tryed to 

[jira] [Created] (IGNITE-5502) .NET: Persistent Store tests

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5502:
--

 Summary: .NET: Persistent Store tests
 Key: IGNITE-5502
 URL: https://issues.apache.org/jira/browse/IGNITE-5502
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.1
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.1


Configuration is propagated in IGNITE-5341, now add proper tests that 
persistence works via .NET as expected.



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

[jira] [Created] (IGNITE-5501) IgniteCachePartitionMapUpdateTest hangs

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5501:
---

 Summary: IgniteCachePartitionMapUpdateTest hangs
 Key: IGNITE-5501
 URL: https://issues.apache.org/jira/browse/IGNITE-5501
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 2.1


Currently all tests in {{IgniteCachePartitionMapUpdateTest}} hang. Reproducible 
locally. No obvious deadlock is visible from thread dumps. No assertions or 
obvious exceptions. Log is not informative:
{code}
org.apache.ignite.IgniteException: Timeout of waiting for topology map update 
[igniteInstanceName=cache.IgniteCachePartitionMapUpdateTest1, 
cache=ignite-atomics-sys-cache, cacheId=689859866, 
topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0], p=2, 
readVer=AffinityTopologyVersion [topVer=5, minorTopVer=0], 
locNode=TcpDiscoveryNode [id=fe63c3eb-1715-4f9a-a183-acb6bfe1, 
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, 
intOrder=2, lastExchangeTime=1497465751500, loc=true, 
ver=2.1.0#19700101-sha1:, isClient=false]]
at 
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:691)
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.IgniteCachePartitionMapUpdateTest.testPartitionMapUpdate1(IgniteCachePartitionMapUpdateTest.java:145)
{code}



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

[jira] [Created] (IGNITE-5500) IgniteDiagnosticMessagesMultipleConnectionsTest.testLongRunning fails

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5500:
---

 Summary: 
IgniteDiagnosticMessagesMultipleConnectionsTest.testLongRunning fails
 Key: IGNITE-5500
 URL: https://issues.apache.org/jira/browse/IGNITE-5500
 Project: Ignite
  Issue Type: Bug
 Environment: Stack trace:
{code}
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.internal.managers.IgniteDiagnosticMessagesTest.testLongRunning(IgniteDiagnosticMessagesTest.java:170)
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:1992)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:131)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1907)
at java.lang.Thread.run(Thread.java:745)
{code}
Reporter: Vladimir Ozerov
Assignee: Alexey Goncharuk
 Fix For: 2.1






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

[jira] [Created] (IGNITE-5499) Binary metadata is persisted when persistence is enabled

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5499:
---

 Summary: Binary metadata is persisted when persistence is enabled
 Key: IGNITE-5499
 URL: https://issues.apache.org/jira/browse/IGNITE-5499
 Project: Ignite
  Issue Type: Task
  Components: persistence
Reporter: Sergey Chugunov


h2. Notes
Roughly speaking current model of binary metadata handling has two modes: 
compactFooter on and off, flag to switch is available at 
*IgniteConfiguration#BinaryConfiguration#compactFooter* configuration setting.

If compact footer is on (default configuration) than metadata isn't persisted 
anywhere even if persisting of caches content is enabled (see IGNITE-5267 for 
more details about persistence feature in Ignite).
Thus after full cluster restart all metadata gets lost and persisted data 
cannot be deserialized and used.

h2. Acceptance Criteria
# All metadata changes are persisted when persistence is enabled.
# On full cluster restart persisted metadata is used.

h2. Performance and Durability Concerns
# As persisting metadata to disk requires IO activity, it must be properly 
handled in metadata exchange protocol as it is executed from discovery thread 
(must never be blocked on IO).
Changes to protocol may be required.
# Possible metadata conflicts must be taken into account as nodes with 
differences in persisted metadata may be started and stopped in different 
orders.
Other corner cases may arise here.



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

[jira] [Created] (IGNITE-5498) Failures in GridNioSslSelfTest

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5498:
---

 Summary: Failures in GridNioSslSelfTest
 Key: IGNITE-5498
 URL: https://issues.apache.org/jira/browse/IGNITE-5498
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Vladimir Ozerov
Assignee: Semen Boikov
 Fix For: 2.1


Affected tests:
{{GridNioSslSelfTest.testConcurrentConnects}}
{{GridNioSslSelfTest.testSimpleMessages}}

{code}
junit.framework.AssertionFailedError: Unexpected exception occurred while 
handling connection: class 
org.apache.ignite.internal.util.nio.GridNioException: An established connection 
was aborted by the software in your host machine
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at 
org.apache.ignite.internal.util.nio.GridNioSelfTest$EchoListener.onDisconnected(GridNioSelfTest.java:1361)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onExceptionCaught(GridNioFilterChain.java:261)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
at 
org.apache.ignite.internal.util.nio.GridNioCodecFilter.onExceptionCaught(GridNioCodecFilter.java:80)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
at 
org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter.onExceptionCaught(GridNioSslFilter.java:241)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedExceptionCaught(GridNioFilterAdapter.java:102)
at 
org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onExceptionCaught(GridNioServer.java:3188)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain.onExceptionCaught(GridNioFilterChain.java:160)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.close(GridNioServer.java:2437)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2199)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1968)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1669)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}



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

[jira] [Created] (IGNITE-5497) MemoryMetricsSelfTest.testAllocationRateMultiThreaded fails

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5497:
---

 Summary: MemoryMetricsSelfTest.testAllocationRateMultiThreaded 
fails
 Key: IGNITE-5497
 URL: https://issues.apache.org/jira/browse/IGNITE-5497
 Project: Ignite
  Issue Type: Bug
Reporter: Vladimir Ozerov
Assignee: Sergey Chugunov
 Fix For: 2.1


Stack trace: 
{code}
[2017-06-14 22:53:33,664][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.internal.processors.database.MemoryMetricsSelfTest.testAllocationRateMultiThreaded(MemoryMetricsSelfTest.java:94)
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:1992)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:131)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1907)
at java.lang.Thread.run(Thread.java:745)
{code}



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

[jira] [Created] (IGNITE-5496) Externalizable classes get registered twice

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5496:


 Summary: Externalizable classes get registered twice
 Key: IGNITE-5496
 URL: https://issues.apache.org/jira/browse/IGNITE-5496
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.2


I observed a strange behavior on ignite-1.7. If I have an externalizable class 
inside of a serializable class and BinaryMarshaller is used, the externalizable 
class gets registered twice with different typeIds.

Looks like this happens because in BinaryWriterExImpl#marshal0 we first call 
ctx.descriptorForClass(cls, false) which will calculate and register type with 
one typeId. Then we figure out that the class is externalizable and switch to 
optimized marshaller (U.marshal(ctx.optimizedMarsh(), obj)) which will register 
another type ID.

Need to check if this is still reproducible in 2.1-2.2 as it may be a 
performance issue.



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

[jira] [Created] (IGNITE-5495) TcpDiscoveryS3IpFinder tests fail

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5495:
---

 Summary: TcpDiscoveryS3IpFinder tests fail
 Key: IGNITE-5495
 URL: https://issues.apache.org/jira/browse/IGNITE-5495
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Vladimir Ozerov
 Fix For: 2.1


Affected test:
{{TcpDiscoveryS3IpFinderAwsCredentialsProviderSelfTest.testIpFinder}}
{{TcpDiscoveryS3IpFinderAwsCredentialsSelfTest.testIpFinder}}

Root cause:
{code}
Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: The AWS Access 
Key Id you provided does not exist in our records. (Service: Amazon S3; Status 
Code: 403; Error Code: InvalidAccessKeyId; Request ID: 3E504B75D197BC05)
{code}



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

Cassandra related SO question

[Igor Sapego]

Igor,

Can you please take a look at this question at SO?

https://stackoverflow.com/questions/44512192/ignite-put-function-for-cassandra-malfunction-in-c

Best Regards,
Igor

Re: Persistence enabled for all caches

[Sergey Kozlov]

I agree and would note that we need to investigate more various corner
cases like user has cache with PS , then stop grid, switch in memory and
start again. Is there a chance to load data (if it can place in memory).
Also would be interesting to switch mode runtime.

On Tue, Jun 13, 2017 at 12:38 PM, Dmitriy Setrakyan 
wrote:

> +1
>
> On Tue, Jun 13, 2017 at 1:13 AM, Yakov Zhdanov 
> wrote:
>
> > Sam,
> >
> > Absolutely agree. Good catch!
> >
> > --Yakov
> >
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

[GitHub] ignite pull request #2133: IGNITE-5492: Local cache metrics are broken.

[shroman]

GitHub user shroman opened a pull request:

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

IGNITE-5492: Local cache metrics are broken.



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

$ git pull https://github.com/shroman/ignite IGNITE-5492

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

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


commit 01a6b8cb3f57a390cc74692c7099f4bed5131b6d
Author: shroman 
Date:   2017-06-15T09:41:01Z

IGNITE-5492: Local cache metrics are broken.




---
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-5494) Web console: Improve admin panel load.

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-5494:
--

 Summary: Web console: Improve admin panel load.
 Key: IGNITE-5494
 URL: https://issues.apache.org/jira/browse/IGNITE-5494
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Affects Versions: 2.0
Reporter: Andrey Novikov
 Fix For: 2.1


* users list requests twice on page load
* incorrect metrics calculation.



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

[GitHub] ignite pull request #2131: IGNITE-5344 JDBC thin driver: support Statement.c...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5344  JDBC thin driver: support Statement.closeOnCompletion



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

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

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

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


commit f35f87c8550b9e75e7aedbfa9721f9c0b4261fd8
Author: tledkov-gridgain 
Date:   2017-06-14T12:39:14Z

IGNITE-5344: Statement.closeOnCompletion save the progress

commit e6e70c312114dda4b163a75030122c3f1bbcd76d
Author: tledkov-gridgain 
Date:   2017-06-14T15:05:37Z

IGNITE-5344: add the test

commit 41aa55affd129fc10565ecad6b6fa2a26778f673
Author: tledkov-gridgain 
Date:   2017-06-14T15:22:11Z

IGNITE-5344: add comment

commit d3f7f50e393c9f989c56439b6ee6faf0bfbb833f
Author: tledkov-gridgain 
Date:   2017-06-15T08:19:57Z

IGNITE-5344: fix 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 #2132: Ignite 2.1.1 Hanging partition map exchanges fix

[Jokser]

GitHub user Jokser opened a pull request:

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

Ignite 2.1.1 Hanging partition map exchanges fix



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

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

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

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


commit ea02f6a025994a7f0567ac1959ff03cf1cb9d982
Author: EdShangGG 
Date:   2017-04-13T14:59:56Z

GG-12064 Need to have an ability to cancel snapshot operations
-fixing issues with client nodes

commit 4b8dc799fcd0173576e7e3439d5c7e88531fd1b7
Author: EdShangGG 
Date:   2017-04-14T10:26:34Z

GG-12064 Need to have an ability to cancel snapshot operations
-fixing issues with multiple exchange future completion

commit 0db2c2037117cf377915768c9bcf97b9d33ee3dd
Author: Alexey Goncharuk 
Date:   2017-04-17T06:41:02Z

Merge branch 'ignite-gg-8.0.3.ea5' of 
https://github.com/gridgain/apache-ignite into ignite-gg-8.0.4.ea1

commit 9f2ff8f99daec2c313e086a734ab61af4bf2b994
Author: Alexey Goncharuk 
Date:   2017-04-17T11:31:29Z

Merge branch master  into ignite-gg-8.0.4.ea1

commit 0a3830ae004e0bcbd6512604fc1008602b78a034
Author: Alexey Goncharuk 
Date:   2017-04-17T11:31:59Z

Fixing compilation after merge

commit 346373a75387ea0e1c07bb7a5824c7910faf78e6
Author: EdShangGG 
Date:   2017-04-17T15:32:21Z

GG-12064 Need to have an ability to cancel snapshot operations
-cancel for RESTORE

commit 633db6f1b011450f5e926375c24d1ac2fa5e1dd7
Author: EdShangGG 
Date:   2017-04-18T14:30:59Z

GG-12064 Need to have an ability to cancel snapshot operations
-added handling start on broken restore

commit 7eccf755659b52e35755e5fc3e51736c72aaa0e7
Author: Ivan Rakov 
Date:   2017-04-18T15:20:56Z

Merge branch 'master' into ignite-gg-8.0.4.ea1

commit 51c18a27347239479117311ef9ec6f6ffaffdb92
Author: Alexey Goncharuk 
Date:   2017-04-18T15:29:47Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-gg-8.0.4.ea1

commit eff4201ab5ccfa4cfe874d300a975e6a53f94ba1
Author: Ivan Rakov 
Date:   2017-04-18T15:49:11Z

Fixing compilation after merge

commit 7808492b7dee12bdd0c3922e1760ffa364183bc2
Author: Alexey Kuznetsov 
Date:   2017-04-18T16:52:30Z

8.0.4.ea1 Fixed snapshot utility tests.

commit c812cc843e3fdfbc17a99920247320af997b3aa4
Author: Eduard Shangareev 
Date:   2017-04-19T10:30:15Z

GG-12118 Stabilize tests in 8.0.4.ea1 after master merge
-fixing NPE in exchange future

commit 553288b11d9d6ed2f8cd9c612399944533d64988
Author: Ivan Rakov 
Date:   2017-04-19T10:36:42Z

GG-12118: Page counter increment fix

commit 40bbc5d12b20c3ebf3e4c9dba0675c080a811d3c
Author: Alexey Goncharuk 
Date:   2017-04-19T15:15:36Z

Merge ignite-2.0 into ignite-gg-8.0.4.ea1

commit be8b260bd90e951c84ccbbb733e89fcd6c758279
Author: Ivan Rakov 
Date:   2017-04-19T16:00:17Z

IGNITE-4861: Export rebalance metrics and state as MBeans

commit 58995f668a172f3acdb2bd6386dc5390f0dca9a2
Author: Alexey Kuznetsov 
Date:   2017-04-19T16:27:27Z

8.0.4.ea1 Fixed compilation.

commit d8c6ffafa0923544dbb9814c2ea0cbbddde7a5d0
Author: EdShangGG 
Date:   2017-04-19T16:24:36Z

GG-12118 Stabilize tests in 8.0.4.ea1 after master merge
-fixing issued with message ids

commit 097b4f67e48e31b61ffa5c1220d7ada8b51f4516
Author: Ivan Rakov 
Date:   2017-04-20T08:53:14Z

GG-12118: Build fix

commit 22826bc93dc2f186ef6e129d687a28b1c1f384b0
Author: Ivan Rakov 
Date:   2017-04-20T11:44:08Z

IGNITE-4861: Counting expected amount of keys for rebalance metrics hangs 
exchange, fix TBD

commit 75c760aa0f16aee7c1a77c9d1a87114f141659ab
Author: Ivan Rakov 
Date:   2017-04-20T13:47:45Z

IGNITE-4861: Metrics fix

commit a527e4123aad5233995d643d1a9bc1dc330a9949
Author: Ilya Lantukh 
Date:   2017-04-20T14:06:00Z

gg-12095 : part2node usage optimization

commit 1be7d4a8cba88ffdca35d9d2936d2f92a51f02db
Author: Ilya Lantukh 
Date:   2017-04-20T14:16:41Z

gg-12095 : part2node usage optimization for client topology.

commit 6e93d04d0117ff4977ad5f2ffe2a4c990c5ab0cb
Author: Alexey Kuznetsov 
Date:   2017-04-20T16:17:48Z

GG-12050 

Re: IGNITE-4636 .NET: Support local collection joins in LINQ ready for review

[Guru Stron]

My pleasure)

On 14 June 2017 at 18:26, Pavel Tupitsyn  wrote:

> Changes have been reviewed and merged, thank you for another great
> contribution!
>
> Pavel
>
> On Tue, Jun 13, 2017 at 1:30 PM, Pavel Tupitsyn 
> wrote:
>
> > Hi, I'll have a look and reply in JIRA.
> >
> > On Tue, Jun 13, 2017 at 10:34 AM, Guru Stron 
> > wrote:
> >
> >> Hi guys,
> >>
> >> Can anyone please review?
> >>
> >> Pull request:
> >> https://github.com/apache/ignite/pull/2118
> >>
> >> Also i've scheduled some build jobs:
> >>
> >> http://ci.ignite.apache.org/viewQueued.html?itemId=659286
> >> b=queuedBuildOverviewTab
> >> http://ci.ignite.apache.org/viewQueued.html?itemId=659287
> >> b=queuedBuildOverviewTab
> >>
> >
> >
>

[jira] [Created] (IGNITE-5493) Assertion in GridDhtPartitionMap.writeExternal

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5493:
---

 Summary: Assertion in GridDhtPartitionMap.writeExternal
 Key: IGNITE-5493
 URL: https://issues.apache.org/jira/browse/IGNITE-5493
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Ilya Lantukh
 Fix For: 2.1


Test to reproduce: {{IgnitePdsTxCacheRebalancingTest}}
Cause: invalid invariant in {{writeExternal}} method - we have more than 3 
values in {{GridDhtPartitionState}} enum.

The whole {{Ignite PDS Indexing}} suite hangs due to it.



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