[jira] [Updated] (IGNITE-1618) [Test failed] TransactionHeuristicException: Failed to locally write to cache

2015-10-05 Thread Andrey Gura (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Gura updated IGNITE-1618:

Attachment: test_deployment.log

> [Test failed] TransactionHeuristicException: Failed to locally write to cache
> -
>
> Key: IGNITE-1618
> URL: https://issues.apache.org/jira/browse/IGNITE-1618
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Andrey Gura
>  Labels: Muted_test
> Attachments: test_deployment.log
>
>
> The following test fail:
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment}}
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment6}}
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment7}}
> The stack trace:
> {noformat}
> org.apache.ignite.IgniteException: class 
> org.apache.ignite.transactions.TransactionHeuristicException: Failed to 
> locally write to cache (all transaction entries will be invalidated, however 
> there was a window when entries for this transaction were visible to others): 
> GridDhtTxLocal [nearNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> nearFutId=c5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearMiniId=d5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearFinFutId=46e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearFinMiniId=b6e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearXidVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036097, order=1444061035918], super=GridDhtTxLocalAdapter 
> [dhtThreadId=33042, needsCompletedVers=true, nearOnOriginatingNode=true, 
> nearNodes=[], dhtNodes=[100ca1fe-f561-4ddd-b6d9-88d7cf12e001], 
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1]=IgniteTxEntry 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1, 
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl 
> [val=org.apache.ignite.tests.p2p.CacheDeploymentTestValue@6c8704b3, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], entryProcessorsCol=null, 
> entryProcessorCalcVal=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPartition [id=546, mapPubSize=1, 
> rmvQueue=GridCircularBuffer [sizeMask=127, idxGen=0], state=OWNING, 
> reservations=0, empty=false, createTime=10/05/2015 16:03:56, mapPubSize=1], 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], val=null, 
> startVer=1444061035921, ver=GridCacheVersion [topVer=55541037, 
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035921], 
> hash=462848615, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> ver=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036098, order=1444061035920], timeout=0, ts=1444061036094, 
> threadId=33042, id=2544576, topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=0], reentry=null, 
> otherNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, otherVer=GridCacheVersion 
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036097, 
> order=1444061035918], mappedDhtNodes=null, mappedNearNodes=null, 
> ownerVer=null, key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=0]]], prepared=true, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, xidVer=null]}, completedBase=null, 
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036098, 
> order=1444061035920], writeVer=GridCacheVersion [topVer=55541037, 
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035922], 
> implicit=true, implicitSingle=true, loc=true, threadId=33042, 
> startTime=1444061036094, nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> startVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036098, order=1444061035920], endVer=null, 
> isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
> sysInvalidate=false, sys=false, plc=2, commitVer=null, 
> finalizing=USER_FINISH, preparing=false, invalidParts={}, state=COMMITTING, 
> timedOut=false, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0], 
> duration=10ms, onePhaseCommit=true], size=1]]]
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
> at 
>

[jira] [Updated] (IGNITE-1618) [Test failed] TransactionHeuristicException: Failed to locally write to cache

2015-10-05 Thread Andrey Gura (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Gura updated IGNITE-1618:

Description: 
The following test fail:

  * {{GridCacheDeploymentOffHeapSelfTest.testDeployment}}
  * {{GridCacheDeploymentOffHeapSelfTest.testDeployment6}}
  * {{GridCacheDeploymentOffHeapSelfTest.testDeployment7}}

The stack trace:

{noformat}
org.apache.ignite.IgniteException: class 
org.apache.ignite.transactions.TransactionHeuristicException: Failed to locally 
write to cache (all transaction entries will be invalidated, however there was 
a window when entries for this transaction were visible to others): 
GridDhtTxLocal [nearNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
nearFutId=c5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
nearMiniId=d5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
nearFinFutId=46e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
nearFinMiniId=b6e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
nearXidVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
globalTime=1444061036097, order=1444061035918], super=GridDhtTxLocalAdapter 
[dhtThreadId=33042, needsCompletedVers=true, nearOnOriginatingNode=true, 
nearNodes=[], dhtNodes=[100ca1fe-f561-4ddd-b6d9-88d7cf12e001], 
explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey 
[key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1]=IgniteTxEntry 
[key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1, 
txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl 
[val=org.apache.ignite.tests.p2p.CacheDeploymentTestValue@6c8704b3, 
hasValBytes=true]], prevVal=[op=NOOP, val=null], entryProcessorsCol=null, 
entryProcessorCalcVal=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], 
locPart=GridDhtLocalPartition [id=546, mapPubSize=1, 
rmvQueue=GridCircularBuffer [sizeMask=127, idxGen=0], state=OWNING, 
reservations=0, empty=false, createTime=10/05/2015 16:03:56, mapPubSize=1], 
super=GridDistributedCacheEntry [super=GridCacheMapEntry 
[key=KeyCacheObjectImpl [val=13, hasValBytes=true], val=null, 
startVer=1444061035921, ver=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
globalTime=1444061036098, order=1444061035921], hash=462848615, 
extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
[locs=[GridCacheMvccCandidate [nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
ver=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
globalTime=1444061036098, order=1444061035920], timeout=0, ts=1444061036094, 
threadId=33042, id=2544576, topVer=AffinityTopologyVersion [topVer=2, 
minorTopVer=0], reentry=null, otherNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
otherVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
globalTime=1444061036097, order=1444061035918], mappedDhtNodes=null, 
mappedNearNodes=null, ownerVer=null, key=KeyCacheObjectImpl [val=13, 
hasValBytes=true], 
masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0,
 prevVer=null, nextVer=null]], rmts=null]], flags=0]]], prepared=true, 
locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
transferExpiryPlc=false, flags=0, xidVer=null]}, completedBase=null, 
sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion 
[topVer=55541037, nodeOrderDrId=2, globalTime=1444061036098, 
order=1444061035920], writeVer=GridCacheVersion [topVer=55541037, 
nodeOrderDrId=2, globalTime=1444061036098, order=1444061035922], implicit=true, 
implicitSingle=true, loc=true, threadId=33042, startTime=1444061036094, 
nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, startVer=GridCacheVersion 
[topVer=55541037, nodeOrderDrId=2, globalTime=1444061036098, 
order=1444061035920], endVer=null, isolation=READ_COMMITTED, 
concurrency=OPTIMISTIC, timeout=0, sysInvalidate=false, sys=false, plc=2, 
commitVer=null, finalizing=USER_FINISH, preparing=false, invalidParts={}, 
state=COMMITTING, timedOut=false, topVer=AffinityTopologyVersion [topVer=2, 
minorTopVer=0], duration=10ms, onePhaseCommit=true], size=1]]]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
at 
org.apache.ignite.internal.IgniteComputeImpl.execute(IgniteComputeImpl.java:174)
at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentSelfTest.testDeployment6(GridCacheDeploymentSelfTest.java:344)
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

[jira] [Commented] (IGNITE-1485) Improve loading metadata from DB

2015-10-05 Thread Vasiliy Sisko (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944481#comment-14944481
 ] 

Vasiliy Sisko commented on IGNITE-1485:
---

Implemented: 
# On loading of metadata tables with key fields is selected by default. 
# Confirm on import of tables without key fields.
# Link above table of metadata to show metadata without key fields only.
# Metadata with invalid key fields are not possible to select in cache.

> Improve loading metadata from DB
> 
>
> Key: IGNITE-1485
> URL: https://issues.apache.org/jira/browse/IGNITE-1485
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: ignite-1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1594) Home page for web console

2015-10-05 Thread Dmitriy Setrakyan (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944527#comment-14944527
 ] 

Dmitriy Setrakyan commented on IGNITE-1594:
---

Several more comments:
* Log In -> Sign In
* Font for the "Sign In" text should be 2em
* There should be more white space bellow the Sign In section

> Home page for web console
> -
>
> Key: IGNITE-1594
> URL: https://issues.apache.org/jira/browse/IGNITE-1594
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> Home page should look as following:
> # Logo with Apache Ignite Web Console up top
> # Explanation of what web console is immediately below.
> # Login on the left
> # screenshots on the right



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-1594) Home page for web console

2015-10-05 Thread Dmitriy Setrakyan (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944527#comment-14944527
 ] 

Dmitriy Setrakyan edited comment on IGNITE-1594 at 10/6/15 5:25 AM:


Several more comments:
* Log In -> Sign In
* Font for the "Sign In" text should be 2em
* Sign section is too wide. Perhaps the text boxes could be made smaller.
* There should be more white space bellow the Sign In section


was (Author: dsetrakyan):
Several more comments:
* Log In -> Sign In
* Font for the "Sign In" text should be 2em
* There should be more white space bellow the Sign In section

> Home page for web console
> -
>
> Key: IGNITE-1594
> URL: https://issues.apache.org/jira/browse/IGNITE-1594
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Dmitriy Setrakyan
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> Home page should look as following:
> # Logo with Apache Ignite Web Console up top
> # Explanation of what web console is immediately below.
> # Login on the left
> # screenshots on the right



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

2015-10-05 Thread Chandresh Pancholi (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943993#comment-14943993
 ] 

Chandresh Pancholi commented on IGNITE-429:
---

GitHub user chandresh-pancholi opened a pull request:

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

[Ignite-429] Implement IgniteStormStreamer to stream data from Apache Storm

I have made some refactor changes suggested by Gian/Anton.



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

$ git pull https://github.com/chandresh-pancholi/ignite master

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

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


commit 8420e109c4d07bbf438f17dc79268c39b47e76b2
Author: chandresh pancholi 
Date:   2015-09-15T12:50:30Z

ignite-429 feature fix

commit a5adeb4c7badd52dd7724fa5a9a9ba7924e934ed
Author: chandresh pancholi 
Date:   2015-09-16T13:19:37Z

Ignite code refactor and modification

commit c6335046a07d9859a46d078e6cd8d7d2a7011df2
Author: chandresh pancholi 
Date:   2015-09-21T11:59:24Z

Code refactor

commit 4596bedfbfc756d3974b4d2270401515fa618bb5
Author: chandresh pancholi 
Date:   2015-09-28T09:12:13Z

Work completed

commit 538986b186b3d89797a34fe35c8120fecaf9
Author: chandresh pancholi 
Date:   2015-09-29T11:37:17Z

Apache ignite-storm integration

commit 3f40de788e5a050bbefb69ac2517a625e72b5299
Author: chandresh pancholi 
Date:   2015-09-29T11:37:50Z

exclusion of zookeeper

commit aa59cdade93d41d877b1966c4851aa827981b73c
Author: chandresh pancholi 
Date:   2015-10-03T12:13:18Z

Implemented Refactor suggestion given by Anton in Ignite0429

commit 2e103b915ba88b38604030092f55ed1f04b14cfe
Author: chandresh pancholi 
Date:   2015-10-05T07:43:02Z

Code refactor in storm module suggested by Gian/Anton



> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm 
> and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable 
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-1614) Displaying of labels of x-axis is broken now

2015-10-05 Thread Pavel Konstantinov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14942922#comment-14942922
 ] 

Pavel Konstantinov edited comment on IGNITE-1614 at 10/5/15 6:24 AM:
-

1) Currently I'm observe that all labels are merged at the left side of the 
X-axis.
They are unreadable. (ig-1614.png)
2) Line chart has no text labels on x-axis - only digits (see ig-1614-2.png), 
but should display 'Parking 1', 'Parking 2' and so on.


was (Author: pkonstantinov):
1) Currently I'm observe that all labels are merged at the left side of the 
X-axis.
They are unreadable.
2) Line chart has no text labels on x-axis - only digits (see ig-1614-2.png), 
but should display 'Parking 1', 'Parking 2' and so on.

> Displaying of labels of x-axis is broken now
> 
>
> Key: IGNITE-1614
> URL: https://issues.apache.org/jira/browse/IGNITE-1614
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Fix For: ignite-1.5
>
> Attachments: ig-1614-2.png, ig-1614.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1546) Rework XML for DB2

2015-10-05 Thread Pavel Konstantinov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-1546.
--

Verified. Closed.

> Rework XML for DB2
> --
>
> Key: IGNITE-1546
> URL: https://issues.apache.org/jira/browse/IGNITE-1546
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Trivial
> Fix For: ignite-1.5
>
>
> Bean which we generates now is incorrect - node cannot start with it
> I found another notation we should implement:
> 
> 
> 
> 
> 
> 
> 
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1219) Add ssl configuration

2015-10-05 Thread Pavel Konstantinov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-1219.
--
Assignee: (was: Pavel Konstantinov)

Successfully tested.

> Add ssl configuration
> -
>
> Key: IGNITE-1219
> URL: https://issues.apache.org/jira/browse/IGNITE-1219
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Vasiliy Sisko
> Fix For: ignite-1.5
>
>
> We need to add ssl configuration to cluster screen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1615) .Net: Perform AtomicLong.get() without JNI if possible.

2015-10-05 Thread Vladimir Ozerov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-1615.
---

> .Net: Perform AtomicLong.get() without JNI if possible.
> ---
>
> Key: IGNITE-1615
> URL: https://issues.apache.org/jira/browse/IGNITE-1615
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
> Fix For: ignite-1.5
>
>
> Variables with atomic/interlocked semantics are frequently used in 
> mostly-read scenarios. E.g. in spin-loops, non-blocking alogrithms, as 
> regular volatiles, etc..
> With current implementation we perform JNI call on every read which is too 
> expensive, especially with poor Java performance when performing (native -> 
> JVM) transition.
> We can optimize it with the following non-blocking algorithm:
> 1) Add atomic "stamp" field.
> 2) Add atomic "cached" field.
> 3) On any update:
> - Do the update;
> - Atomically increment the stamp;
> 4) On any read:
> - Read stamp (oldStamp);
> - Read cached value;
> - Read stamp again (newStamp);
> - if (oldStamp == newStamp == cache.stamp()), return cached value.
> - Otherwise perform real read through JNI and update cached value with a pair 
> of (readValue + oldStamp);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1615) .Net: Perform AtomicLong.get() without JNI if possible.

2015-10-05 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-1615:
---

 Summary: .Net: Perform AtomicLong.get() without JNI if possible.
 Key: IGNITE-1615
 URL: https://issues.apache.org/jira/browse/IGNITE-1615
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: ignite-1.5


Variables with atomic/interlocked semantics are frequently used in mostly-read 
scenarios. E.g. in spin-loops, non-blocking alogrithms, as regular volatiles, 
etc..

With current implementation we perform JNI call on every read which is too 
expensive, especially with poor Java performance when performing (native -> 
JVM) transition.

We can optimize it with the following non-blocking algorithm:
1) Add atomic "stamp" field.
2) Add atomic "cached" field.
3) On any update:
- Do the update;
- Atomically increment the stamp;
4) On any read:
- Read stamp (oldStamp);
- Read cached value;
- Read stamp again (newStamp);
- if (oldStamp == newStamp == cache.stamp()), return cached value.
- Otherwise perform real read through JNI and update cached value with a pair 
of (readValue + oldStamp);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1546) Rework XML for DB2

2015-10-05 Thread Pavel Konstantinov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-1546:
---
Assignee: (was: Pavel Konstantinov)

> Rework XML for DB2
> --
>
> Key: IGNITE-1546
> URL: https://issues.apache.org/jira/browse/IGNITE-1546
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Trivial
> Fix For: ignite-1.5
>
>
> Bean which we generates now is incorrect - node cannot start with it
> I found another notation we should implement:
> 
> 
> 
> 
> 
> 
> 
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1562) .Net: Remove "Generic" word from "WriteGenericCollection" and "WriteGenericDictionary".

2015-10-05 Thread Pavel Tupitsyn (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943070#comment-14943070
 ] 

Pavel  Tupitsyn commented on IGNITE-1562:
-

Renamed, fixed array usage in WriteCollection, added test.

> .Net: Remove "Generic" word from "WriteGenericCollection" and 
> "WriteGenericDictionary".
> ---
>
> Key: IGNITE-1562
> URL: https://issues.apache.org/jira/browse/IGNITE-1562
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Normally users will use these methods instead of non-generic. Lets make their 
> names as simple as possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1416) .Net: Implement AtomicLong data structure

2015-10-05 Thread Pavel Tupitsyn (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943098#comment-14943098
 ] 

Pavel  Tupitsyn commented on IGNITE-1416:
-

1,2) fixed
3) I don't think it can be optimized. We can't guarantee that AtomicLong won't 
be changed from another node or platform.
4) It is null in Java, and null is good for Cpp platform, so I think we should 
keep it consistent. Throwing exception will make it impossible for the user to 
check for existence (without try-catch, which is wrong), so we would have to 
add another method and complicate the API.

> .Net: Implement AtomicLong data structure
> -
>
> Key: IGNITE-1416
> URL: https://issues.apache.org/jira/browse/IGNITE-1416
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1617) CPP: review string usage in public API

2015-10-05 Thread Igor Sapego (JIRA) 
Igor Sapego created IGNITE-1617:
---

 Summary: CPP: review string usage in public API 
 Key: IGNITE-1617
 URL: https://issues.apache.org/jira/browse/IGNITE-1617
 Project: Ignite
  Issue Type: Task
Reporter: Igor Sapego
Assignee: Igor Sapego


Currently there is std::string type used in some parts of public API while 
const char* used in some other parts. Need to review API and suggest solution 
for the consistent string policy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1613) Platform .Net: Investigate Guid/DateTime/String interoperability with Java

2015-10-05 Thread Pavel Tupitsyn (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943217#comment-14943217
 ] 

Pavel  Tupitsyn commented on IGNITE-1613:
-

String hashcodes performance investigation: 
* PortableUtils.StringHashCode takes ~8% of IPortableWriter.WriteString
* Caching results with ConcurrentDictionary or ThreadLocal Dictionary does not 
improve performance (for short field names at least). And it is not surprising, 
because dictionary lookup includes calculating string hash code with an 
internal algorithm, which is similar.
* Other caching possibilities are Tries (https://en.wikipedia.org/wiki/Trie) 
and precompiled switches 
(http://blogs.msdn.com/b/jomo_fisher/archive/2007/03/28/fast-switching-with-linq.aspx).
 These approaches are quite complicated, so I did not try them.

> Platform .Net: Investigate Guid/DateTime/String interoperability with Java
> --
>
> Key: IGNITE-1613
> URL: https://issues.apache.org/jira/browse/IGNITE-1613
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>
> Currently in .Net we:
> * write Guid and DateTime in Java format
> * calculate string hash code for field names with Java algorithm on each call
> Need to investigate if the following makes sense:
> 1) In .Net always write Guid and DateTime in native .Net format as fast as 
> possible; Make Java understand that format. (Not every Guid written in .Net 
> will be read in Java, so we can win time).
> 2) Cache string hashcodes somehow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1610) CPP: Implement reader and writer for iterators

2015-10-05 Thread Vladimir Ozerov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-1610:
---

Assignee: Vladimir Ozerov  (was: Igor Sapego)

> CPP: Implement reader and writer for iterators
> --
>
> Key: IGNITE-1610
> URL: https://issues.apache.org/jira/browse/IGNITE-1610
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
>
> Need to try and implement portable writer and portable reader that could work 
> with iterators.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

2015-10-05 Thread Anton Vinogradov (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943314#comment-14943314
 ] 

Anton Vinogradov commented on IGNITE-429:
-

Chandresh,

Please don't forget to mention new pull request's url & change issue status to 
"Patch Available" when it will be ready for review.

> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm 
> and stream them into Ignite caches. 
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable 
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1552) Table function doesn't work properly in SQL query

2015-10-05 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943334#comment-14943334
 ] 

ASF GitHub Bot commented on IGNITE-1552:


Github user svladykin closed the pull request at:

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


> Table function doesn't work properly in SQL query
> -
>
> Key: IGNITE-1552
> URL: https://issues.apache.org/jira/browse/IGNITE-1552
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
>  Labels: user-request
> Fix For: ignite-1.5
>
> Attachments: QueryInStatementTest.java
>
>
> IN operator replacement query described in [1] doesn't seem to work properly. 
> Test reproducing the issue is attached.
> [1] 
> https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1613) Platform .Net: Investigate Guid/DateTime/String interoperability with Java

2015-10-05 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943390#comment-14943390
 ] 

ASF GitHub Bot commented on IGNITE-1613:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1613 Platform .Net: Investigate Guid/DateTime/String 
interoperability with Java



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

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

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

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


commit 703ba2a8746ab3a55616dc8a4ec56fa11f384ffe
Author: ptupitsyn 
Date:   2015-10-05T09:54:06Z

IGNITE-1613 Platform .Net: Investigate Guid/DateTime/String 
interoperability with Java

commit 5237a464d4f4d424290818ea12db092feacd2d10
Author: ptupitsyn 
Date:   2015-10-05T11:02:08Z

wip

commit 7aaaef8392657ad9183e66d4293e9ee5de9d7724
Author: ptupitsyn 
Date:   2015-10-05T11:12:39Z

Improve write benchmark

commit 3bec1711aa62a913c36117f2d6cfabb58e1783d7
Author: ptupitsyn 
Date:   2015-10-05T11:14:31Z

wip

commit 19514cf73c2f54979edb257ccd0184749d642fe4
Author: ptupitsyn 
Date:   2015-10-05T12:16:14Z

wip Guid

commit 5f710b65b3c05ba66ef6be6f748d72185d71ba65
Author: ptupitsyn 
Date:   2015-10-05T12:46:22Z

WriteGuid with structs

commit 8b04b05e92fbc9e3eef67654e1103eb05dda18bd
Author: ptupitsyn 
Date:   2015-10-05T12:50:14Z

wip

commit 815acaf56fd60bedb45bc7184d41b5e61f1ab5db
Author: ptupitsyn 
Date:   2015-10-05T13:02:43Z

wip

commit 91d067905993d37abb0ef3750334e8cfe6308568
Author: ptupitsyn 
Date:   2015-10-05T13:23:19Z

bitshifts

commit 0e5560cb041b3906cb45c5b6315c33871b7bfd51
Author: ptupitsyn 
Date:   2015-10-05T13:28:17Z

wip guids

commit cd5756c4e26ad7e3f5abc05a2594ee6e6f45acdd
Author: ptupitsyn 
Date:   2015-10-05T13:46:31Z

Guid marshalling cleanup




> Platform .Net: Investigate Guid/DateTime/String interoperability with Java
> --
>
> Key: IGNITE-1613
> URL: https://issues.apache.org/jira/browse/IGNITE-1613
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>
> Currently in .Net we:
> * write Guid and DateTime in Java format
> * calculate string hash code for field names with Java algorithm on each call
> Need to investigate if the following makes sense:
> 1) In .Net always write Guid and DateTime in native .Net format as fast as 
> possible; Make Java understand that format. (Not every Guid written in .Net 
> will be read in Java, so we can win time).
> 2) Cache string hashcodes somehow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1617) CPP: review string usage in public API

2015-10-05 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/IGNITE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943611#comment-14943611
 ] 

ASF GitHub Bot commented on IGNITE-1617:


GitHub user isapego opened a pull request:

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

IGNITE-1617: Strings usage adjusted



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

$ git pull https://github.com/isapego/ignite ignite-1617

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

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


commit cfd3355414b0fe425b8cba5dd032715ae5f6837f
Author: isapego 
Date:   2015-10-02T16:52:26Z

IGNITE-1610: Implemented portable reader and writer for iterators.

commit 61410e8ea4a1dba5c8122ad519d375f085f65bed
Author: isapego 
Date:   2015-10-05T09:35:49Z

Revert "IGNITE-1610: Implemented portable reader and writer for iterators."

This reverts commit cfd3355414b0fe425b8cba5dd032715ae5f6837f.

commit cdf2bb19f076d35f8b25d7a27682bf22412f18a0
Author: isapego 
Date:   2015-10-05T16:17:14Z

IGNITE-1617: Strings usage adjusted




> CPP: review string usage in public API 
> ---
>
> Key: IGNITE-1617
> URL: https://issues.apache.org/jira/browse/IGNITE-1617
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>
> Currently there is std::string type used in some parts of public API while 
> const char* used in some other parts. Need to review API and suggest solution 
> for the consistent string policy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)