[jira] [Commented] (IGNITE-3414) Hadoop: Optimize map-reduce job planning.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-3414:
-

Yes, I meant LinkedHashSet here.

> Hadoop: Optimize map-reduce job planning.
> -
>
> Key: IGNITE-3414
> URL: https://issues.apache.org/jira/browse/IGNITE-3414
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.7
>
>
> Currently Hadoop module has inefficient map-reduce planning engine. In 
> particular, it assigns tasks only to affinity nodes. It could lead to 
> situation when very huge tasks is processed by a single cluster node, while 
> other cluster nodes are idle. 
> We should implement configurable map-reduce planner which will be able to 
> utilize the whole cluster.



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

[jira] [Commented] (IGNITE-3443) Implement collecting what SQL statements executed on cluster and their metrics.

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan commented on IGNITE-3443:
---

Would be nice to see the list of all the collected data here. Also, whatever we 
collect, we should make sure that the information is available via API and, if 
possible, via MBeans. We should also document it.

> Implement collecting what SQL statements executed on cluster and their 
> metrics.
> ---
>
> Key: IGNITE-3443
> URL: https://issues.apache.org/jira/browse/IGNITE-3443
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 1.7
>
>
> We could collect last 1000 (maybe configurable) sql statements with per  
> statement statistics: count, min time, max time, avg time,
> May be execution plan (explain) ?



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

[jira] [Commented] (IGNITE-2969) Optimistic transactions support in deadlock detection

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-2969:
-

Race found in {{IgniteTxManager.txLockInfo}} method. When methods creates 
{{TxLock}} instances based on local {{GridCacheMvccCandidate}}'s it is possible 
to find more than one owner {{GridCacheMvccCandidate}} because it can be 
changed during iteration. It leads to {{AssertionError}} in 
{{TxDeadlockFuture.updateWaitForGraph}} method. As simple solution I just treat 
all owners (except first) as candidates. But should exist more accurate 
solution.

At this moment {{TxDeadlockDetectionNoHangsTest.testNoHangsOptimistic}} test 
fails periodically with {{AssertionError}}. Need investigate:

{noformat}
java.lang.AssertionError: Transaction does not own lock for update 
[entry=GridDhtColocatedCacheEntry [super=GridDhtCacheEntry [rdrs=[], 
locPart=GridDhtLocalPartition [id=36, mapPubSize=1, rmvQueue=GridCircularBuffer 
[sizeMask=31, idxGen=0], cntr=0, state=OWNING, reservations=0, empty=false, 
createTime=07/06/2016 20:25:20, mapPubSize=1], super=GridDistributedCacheEntry 
[super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=36, hasValBytes=true], 
val=null, startVer=1467825951227, ver=GridCacheVersion [topVer=79305930, 
nodeOrderDrId=3, globalTime=1467825954832, order=1467825951227], 
hash=-1934024054, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
[locs=[GridCacheMvccCandidate [nodeId=fe033852-4308-417a-b726-c517bdb2, 
ver=GridCacheVersion [topVer=79305930, nodeOrderDrId=3, 
globalTime=1467825954831, order=1467825951226], timeout=500, ts=1467825954823, 
threadId=49974, id=96645, topVer=AffinityTopologyVersion [topVer=13, 
minorTopVer=0], reentry=null, otherNodeId=fe033852-4308-417a-b726-c517bdb2, 
otherVer=GridCacheVersion [topVer=79305930, nodeOrderDrId=3, 
globalTime=1467825954831, order=1467825951226], mappedDhtNodes=null, 
mappedNearNodes=null, ownerVer=null, serOrder=null, key=KeyCacheObjectImpl 
[val=36, hasValBytes=true], 
masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0,
 prevVer=null, nextVer=null]], rmts=null]], flags=0, tx=GridNearTxLocal 
[mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false, 
colocatedLocallyMapped=true, needCheckBackup=null, hasRemoteLocks=false, 
mappings=IgniteTxMappingsImpl [], super=GridDhtTxLocalAdapter 
[nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false, 
super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false, 
depEnabled=true, txState=IgniteTxStateImpl [activeCacheIds=GridLongList [idx=1, 
arr=[94416770]], txMap={IgniteTxKey [key=KeyCacheObjectImpl [val=14, 
hasValBytes=true], cacheId=94416770]=IgniteTxEntry [key=KeyCacheObjectImpl 
[val=14, hasValBytes=true], cacheId=94416770, txKey=IgniteTxKey 
[key=KeyCacheObjectImpl [val=14, hasValBytes=true], cacheId=94416770], 
val=[op=UPDATE, val=UserCacheObjectImpl [val=0, hasValBytes=true]], 
prevVal=[op=UPDATE, val=UserCacheObjectImpl [val=0, hasValBytes=true]], 
entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
explicitVer=null, dhtVer=GridCacheVersion [topVer=79305930, nodeOrderDrId=2, 
globalTime=1467825955336, order=1467825951423], filters=[], 
filtersPassed=false, filtersSet=true, entry=GridDhtDetachedCacheEntry 
[super=GridDistributedCacheEntry [super=GridCacheMapEntry 
[key=KeyCacheObjectImpl [val=14, hasValBytes=true], val=null, 
startVer=1467825951345, ver=GridCacheVersion [topVer=79305930, nodeOrderDrId=3, 
globalTime=1467825954833, order=1467825951345], hash=14, extras=null, 
flags=0]]], prepared=false, locked=false, 
nodeId=584b2f41-c474-4fe7-88c7-6dcbbc70, locMapped=false, expiryPlc=null, 
transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
xidVer=GridCacheVersion [topVer=79305930, nodeOrderDrId=3, 
globalTime=1467825954833, order=1467825951311]], IgniteTxKey 
[key=KeyCacheObjectImpl [val=37, hasValBytes=true], 
cacheId=94416770]=IgniteTxEntry [key=KeyCacheObjectImpl [val=37, 
hasValBytes=true], cacheId=94416770, txKey=IgniteTxKey [key=KeyCacheObjectImpl 
[val=37, hasValBytes=true], cacheId=94416770], val=[op=UPDATE, 
val=UserCacheObjectImpl [val=0, hasValBytes=false]], prevVal=[op=UPDATE, 
val=UserCacheObjectImpl [val=0, hasValBytes=false]], entryProcessorsCol=null, 
ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null, 
filters=[], filtersPassed=false, filtersSet=true, 
entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry 
[super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=37, hasValBytes=true], 
val=null, startVer=1467825951346, ver=GridCacheVersion [topVer=79305930, 
nodeOrderDrId=3, globalTime=1467825954833, order=1467825951346], hash=37, 
extras=null, flags=0]]], prepared=false, locked=false, 
nodeId=f98ebdda-7833-4e5d-bfdd-2f6ad8c1, locMapped=false, expiryPlc=null, 

[jira] [Updated] (IGNITE-3444) Documentation for odbc-example should be updated

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-3444:

Component/s: documentation

> Documentation for odbc-example should be updated
> 
>
> Key: IGNITE-3444
> URL: https://issues.apache.org/jira/browse/IGNITE-3444
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, odbc
>Affects Versions: 1.6
>Reporter: Vasilisa  Sidorova
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 1.7
>
>
> -
> DESCRIPTION
> -
> # After user Install ignite odbc driver according to 
> platforms\cpp\odbc\README.txt he/she should add directories with 
> libignite-odbc.so to the LD_LIBRARY_PATH (this information is in 
> platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once 
> # After that user can build and run odbc-example and this action could 
> happens many times and this can be done much later after driver installation 
> # Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the 
> platforms/cpp/examples/README.txt for odbc-example running
> -
> PROPOSAL
> -
> Add information about  adding path to libignite-odbc.so to the 
> LD_LIBRARY_PATH into "Running examples on Linux" part of the 
> platforms/cpp/examples/README.txt
> For example, this text:
> {noformat}
> * Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it 
> is /usr/local/lib)
> {noformat}



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

[jira] [Commented] (IGNITE-3444) Documentation for odbc-example should be updated

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3444:


GitHub user isapego opened a pull request:

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

IGNITE-3444: Updated documentation for odbc-example.



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

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

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

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


commit d26a588686bee379aacd8ec2d14d0e04e026da78
Author: isapego 
Date:   2016-07-06T17:23:27Z

IGNITE-3444: Updated documentation for odbc-example.




> Documentation for odbc-example should be updated
> 
>
> Key: IGNITE-3444
> URL: https://issues.apache.org/jira/browse/IGNITE-3444
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 1.6
>Reporter: Vasilisa  Sidorova
>Assignee: Igor Sapego
>Priority: Minor
>
> -
> DESCRIPTION
> -
> # After user Install ignite odbc driver according to 
> platforms\cpp\odbc\README.txt he/she should add directories with 
> libignite-odbc.so to the LD_LIBRARY_PATH (this information is in 
> platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once 
> # After that user can build and run odbc-example and this action could 
> happens many times and this can be done much later after driver installation 
> # Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the 
> platforms/cpp/examples/README.txt for odbc-example running
> -
> PROPOSAL
> -
> Add information about  adding path to libignite-odbc.so to the 
> LD_LIBRARY_PATH into "Running examples on Linux" part of the 
> platforms/cpp/examples/README.txt
> For example, this text:
> {noformat}
> * Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it 
> is /usr/local/lib)
> {noformat}



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

[jira] [Assigned] (IGNITE-3444) Documentation for odbc-example should be updated

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-3444:
---

Assignee: Igor Sapego

> Documentation for odbc-example should be updated
> 
>
> Key: IGNITE-3444
> URL: https://issues.apache.org/jira/browse/IGNITE-3444
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 1.6
>Reporter: Vasilisa  Sidorova
>Assignee: Igor Sapego
>Priority: Minor
>
> -
> DESCRIPTION
> -
> # After user Install ignite odbc driver according to 
> platforms\cpp\odbc\README.txt he/she should add directories with 
> libignite-odbc.so to the LD_LIBRARY_PATH (this information is in 
> platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once 
> # After that user can build and run odbc-example and this action could 
> happens many times and this can be done much later after driver installation 
> # Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the 
> platforms/cpp/examples/README.txt for odbc-example running
> -
> PROPOSAL
> -
> Add information about  adding path to libignite-odbc.so to the 
> LD_LIBRARY_PATH into "Running examples on Linux" part of the 
> platforms/cpp/examples/README.txt
> For example, this text:
> {noformat}
> * Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it 
> is /usr/local/lib)
> {noformat}



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

[jira] [Updated] (IGNITE-3444) Documentation for odbc-example should be updated

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-3444:
---
Description: 
-
DESCRIPTION
-
# After user Install ignite odbc driver according to 
platforms\cpp\odbc\README.txt he/she should add directories with 
libignite-odbc.so to the LD_LIBRARY_PATH (this information is in 
platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once 
# After that user can build and run odbc-example and this action could happens 
many times and this can be done much later after driver installation 
# Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the 
platforms/cpp/examples/README.txt for odbc-example running

-
PROPOSAL
-
Add information about  adding path to libignite-odbc.so to the LD_LIBRARY_PATH 
into "Running examples on Linux" part of the platforms/cpp/examples/README.txt
For example, this text:
{noformat}
* Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it 
is /usr/local/lib)
{noformat}


  was:
-
DESCRIPTION
-
# After user Install ignite odbc driver according to 
platforms\cpp\odbc\README.txt he/she should add directories with 
libignite-odbc.so to the LD_LIBRARY_PATH (this information is in 
platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once 
# After that user can build and run odbc-example and this action could happens 
many times and this can be done much later after driver installation 
# Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the 
platforms/cpp/examples/README.txt for odbc-example running
-
PROPOSAL
-
Add information about  adding path to libignite-odbc.so to the LD_LIBRARY_PATH 
into "Running examples on Linux" part of the platforms/cpp/examples/README.txt
For example, this text:
{noformat}
* Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it 
is /usr/local/lib)
{noformat}



> Documentation for odbc-example should be updated
> 
>
> Key: IGNITE-3444
> URL: https://issues.apache.org/jira/browse/IGNITE-3444
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 1.6
>Reporter: Vasilisa  Sidorova
>Priority: Minor
>
> -
> DESCRIPTION
> -
> # After user Install ignite odbc driver according to 
> platforms\cpp\odbc\README.txt he/she should add directories with 
> libignite-odbc.so to the LD_LIBRARY_PATH (this information is in 
> platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once 
> # After that user can build and run odbc-example and this action could 
> happens many times and this can be done much later after driver installation 
> # Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the 
> platforms/cpp/examples/README.txt for odbc-example running
> -
> PROPOSAL
> -
> Add information about  adding path to libignite-odbc.so to the 
> LD_LIBRARY_PATH into "Running examples on Linux" part of the 
> platforms/cpp/examples/README.txt
> For example, this text:
> {noformat}
> * Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it 
> is /usr/local/lib)
> {noformat}



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

[jira] [Created] (IGNITE-3444) Documentation for odbc-example should be updated

[Vasilisa Sidorova (JIRA)]

Vasilisa  Sidorova created IGNITE-3444:
--

 Summary: Documentation for odbc-example should be updated
 Key: IGNITE-3444
 URL: https://issues.apache.org/jira/browse/IGNITE-3444
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Affects Versions: 1.6
Reporter: Vasilisa  Sidorova
Priority: Minor


-
DESCRIPTION
-
# After user Install ignite odbc driver according to 
platforms\cpp\odbc\README.txt he/she should add directories with 
libignite-odbc.so to the LD_LIBRARY_PATH (this information is in 
platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once 
# After that user can build and run odbc-example and this action could happens 
many times and this can be done much later after driver installation 
# Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the 
platforms/cpp/examples/README.txt for odbc-example running
-
PROPOSAL
-
Add information about  adding path to libignite-odbc.so to the LD_LIBRARY_PATH 
into "Running examples on Linux" part of the platforms/cpp/examples/README.txt
For example, this text:
{noformat}
* Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it 
is /usr/local/lib)
{noformat}




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

[jira] [Commented] (IGNITE-3207) Rename IgniteConfiguration.gridName

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-3207:
-

Is it ready for review?

> Rename IgniteConfiguration.gridName
> ---
>
> Key: IGNITE-3207
> URL: https://issues.apache.org/jira/browse/IGNITE-3207
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Biao Ma
> Fix For: 1.7
>
>
> We have got a TON of questions on gridName property. Everyone thinks that 
> clusters are formed based on the gridName, that is, nodes with the same grid 
> name will join one cluster, and nodes with a different name will be in a 
> separate cluster.
> Let's do the following:
> * Deprecate IgniteConfiguration.gridName
> * Add IgniteConfiguration.localInstanceName
> * Rename related parameters in Ignition class (and other places, if present)
> * Update Javadoc: clearly state that this name only works locally and has no 
> effect on topology.



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

[jira] [Commented] (IGNITE-945) HTTP REST prepend/append commands failed

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-945:


[~samaitra], please use the approach suggested by Yakov above. In your current 
implementation the whole operation is not atomic. Use {{cache.invoke}} - it was 
suggested by Yakov when he mentioned {{EntryProcessor}}.

> HTTP REST prepend/append commands failed
> 
>
> Key: IGNITE-945
> URL: https://issues.apache.org/jira/browse/IGNITE-945
> Project: Ignite
>  Issue Type: Bug
>  Components: newbie
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>  Labels: newbie
> Fix For: 1.7
>
>
> Requests 
> http://localhost:8080/ignite?cacheName=partitioned_cache=1=prepend=p
> http://localhost:8080/ignite?cacheName=partitioned_cache=1=append=a
> returns same error:
> {noformat}
> {"error":"Failed to start transaction on non-transactional cache: 
> partitioned_cache","response":null,"sessionToken":"","successStatus":1}
> {noformat}
> Node output is following:
> {noformat}
> [14:01:32,555][SEVERE][ignite-#12%pub-null%][GridRestProcessor] Failed to 
> handle request: CACHE_PREPEND
> class org.apache.ignite.IgniteCheckedException: Failed to start transaction 
> on non-transactional cache: partitioned_cache
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6732)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:901)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   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:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to start 
> transaction on non-transactional cache: partitioned_cache
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTransactionsImpl.checkTransactional(IgniteTransactionsImpl.java:193)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTransactionsImpl.txStartEx(IgniteTransactionsImpl.java:121)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.txStartEx(GridCacheAdapter.java:3239)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.txStartEx(GridCacheProxyImpl.java:808)
>   at 
> org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler$1.call(GridCacheCommandHandler.java:405)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6124)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:893)
>   ... 4 more
> {noformat}
> Is there a limitation for use non-transactional caches for prepend/append 
> commands?



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

[jira] [Commented] (IGNITE-3417) Cassandra packages have no descriptions

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-3417:
-

[~irudyak], thanks! I've merged your changes into the master.

[~skozlov], please validate the fix.

> Cassandra packages have no descriptions
> ---
>
> Key: IGNITE-3417
> URL: https://issues.apache.org/jira/browse/IGNITE-3417
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.6
>Reporter: Sergey Kozlov
>Assignee: Igor Rudyak
>
> Generated javadoc (overview-summary.html) has no decriptions for Cassandra 
> package



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

[jira] [Created] (IGNITE-3443) Implement collecting what SQL statements executed on cluster and their metrics.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3443:


 Summary: Implement collecting what SQL statements executed on 
cluster and their metrics.
 Key: IGNITE-3443
 URL: https://issues.apache.org/jira/browse/IGNITE-3443
 Project: Ignite
  Issue Type: Task
  Components: SQL
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7


We could collect last 1000 (maybe configurable) sql statements with per  
statement statistics: count, min time, max time, avg time,
May be execution plan (explain) ?



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

[jira] [Commented] (IGNITE-3416) CPP: Review and optimize serialization and deserialization.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3416:


GitHub user isapego opened a pull request:

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

IGNITE-3416: Performance improvements.



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

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

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

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


commit 857d56caca3c992d80be5671edf96778ff625038
Author: isapego 
Date:   2016-07-06T15:19:10Z

IGNITE-3416: Performance improvements.




> CPP: Review and optimize serialization and deserialization.
> ---
>
> Key: IGNITE-3416
> URL: https://issues.apache.org/jira/browse/IGNITE-3416
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.7
>
>
> It seems like some operations can be optimized a lot, for example 
> {{BinaryReaderImpl::ReadTopObject()}} reads string from the 
> stream byte by byte, makeing 2 additional calls to {{EnsureEnoughData()}} and 
> {{Shift()}} for every byte.



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

[jira] [Created] (IGNITE-3441) Caches and Summary: move client near cache config from Summary to Caches

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3441:


 Summary: Caches and Summary: move client near cache config from 
Summary to Caches
 Key: IGNITE-3441
 URL: https://issues.apache.org/jira/browse/IGNITE-3441
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7


Also it would be useful to apply same near cache settings for all or selected 
caches.



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

[jira] [Comment Edited] (IGNITE-3440) Ignite Services: ServiceTopologyCallable is executed before system cache is started

[Denis Magda (JIRA)]

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

Denis Magda edited comment on IGNITE-3440 at 7/6/16 3:12 PM:
-

[~vkulichenko], [~agoncharuk],

Please review the fix. The changes are minor and attached in the diff file.

BTW, will such a fix work for caches which have SYNC rebalance mode (like the 
utility cache)?


was (Author: dmagda):
[~vkulichenko], [~agoncharuk],

Please review the fix. The changes are minor and attached in the diff file.

> Ignite Services: ServiceTopologyCallable is executed before system cache is 
> started
> ---
>
> Key: IGNITE-3440
> URL: https://issues.apache.org/jira/browse/IGNITE-3440
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.7
>
> Attachments: ignite-3440.diff
>
>
> In rare cases it's possible to get the following exception
> {code}
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-0] 2016-07-01 
> 16:03:54,120 22971 INFO  
> [com.workday.fabric.ignite.management.QuorumEventDispatcher] Storage count 
> changed - oldvalue: 3 - newvalue: 4 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] 2016-07-01 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] 2016-07-01 
> 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] class org.apache.ignite.IgniteException: null
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] class 
> org.apache.ignite.IgniteException: null
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)

[jira] [Commented] (IGNITE-3440) Ignite Services: ServiceTopologyCallable is executed before system cache is started

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-3440:
-

[~vkulichenko], [~agoncharuk],

Please review the fix. The changes are minor and attached in the diff file.

> Ignite Services: ServiceTopologyCallable is executed before system cache is 
> started
> ---
>
> Key: IGNITE-3440
> URL: https://issues.apache.org/jira/browse/IGNITE-3440
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.7
>
> Attachments: ignite-3440.diff
>
>
> In rare cases it's possible to get the following exception
> {code}
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-0] 2016-07-01 
> 16:03:54,120 22971 INFO  
> [com.workday.fabric.ignite.management.QuorumEventDispatcher] Storage count 
> changed - oldvalue: 3 - newvalue: 4 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] 2016-07-01 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] 2016-07-01 
> 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] class org.apache.ignite.IgniteException: null
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] class 
> org.apache.ignite.IgniteException: null
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> 

[jira] [Updated] (IGNITE-3440) Ignite Services: ServiceTopologyCallable is executed before system cache is started

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-3440:

Attachment: ignite-3440.diff

> Ignite Services: ServiceTopologyCallable is executed before system cache is 
> started
> ---
>
> Key: IGNITE-3440
> URL: https://issues.apache.org/jira/browse/IGNITE-3440
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.7
>
> Attachments: ignite-3440.diff
>
>
> In rare cases it's possible to get the following exception
> {code}
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-0] 2016-07-01 
> 16:03:54,120 22971 INFO  
> [com.workday.fabric.ignite.management.QuorumEventDispatcher] Storage count 
> changed - oldvalue: 3 - newvalue: 4 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] 2016-07-01 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] 2016-07-01 
> 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] class org.apache.ignite.IgniteException: null
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] class 
> org.apache.ignite.IgniteException: null
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6484)
> [16:03:54] :   

[jira] [Created] (IGNITE-3442) Header: Configuration menu should dropdown on hover

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3442:


 Summary: Header: Configuration menu should dropdown on hover
 Key: IGNITE-3442
 URL: https://issues.apache.org/jira/browse/IGNITE-3442
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7


On click go to Clusters.



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

[jira] [Updated] (IGNITE-3440) Ignite Services: ServiceTopologyCallable is executed before system cache is started

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-3440:

Fix Version/s: 1.7

> Ignite Services: ServiceTopologyCallable is executed before system cache is 
> started
> ---
>
> Key: IGNITE-3440
> URL: https://issues.apache.org/jira/browse/IGNITE-3440
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.7
>
>
> In rare cases it's possible to get the following exception
> {code}
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-0] 2016-07-01 
> 16:03:54,120 22971 INFO  
> [com.workday.fabric.ignite.management.QuorumEventDispatcher] Storage count 
> changed - oldvalue: 3 - newvalue: 4 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] 2016-07-01 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] 2016-07-01 
> 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] class org.apache.ignite.IgniteException: null
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] class 
> org.apache.ignite.IgniteException: null
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6484)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> 

[jira] [Created] (IGNITE-3440) Ignite Services: ServiceTopologyCallable is executed before system cache is started

[Denis Magda (JIRA)]

Denis Magda created IGNITE-3440:
---

 Summary: Ignite Services: ServiceTopologyCallable is executed 
before system cache is started
 Key: IGNITE-3440
 URL: https://issues.apache.org/jira/browse/IGNITE-3440
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
Assignee: Denis Magda


In rare cases it's possible to get the following exception

{code}
[16:03:54] : [:fabric-tests:test] [FabricRunner-0] 2016-07-01 
16:03:54,120 22971 INFO  
[com.workday.fabric.ignite.management.QuorumEventDispatcher] Storage count 
changed - oldvalue: 3 - newvalue: 4 
[16:03:54] : [testQuorumEvents] [Test Output]
[FabricRunner-7] 2016-07-01 16:03:54,242 1492  ERROR 
[org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute job 
[jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, ses=GridJobSessionImpl 
[ses=GridTaskSessionImpl 
[taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
 dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, loc=true, 
sampleClsName=java.lang.String, pendingUndeploy=false, undeployed=false, 
usage=0]], 
taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
 sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
startTime=1467389034118, endTime=9223372036854775807, 
taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
failSpi=null, loadSpi=null, usage=1, fullSup=false, 
subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
[orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 

[16:03:54] : [:fabric-tests:test] [FabricRunner-7] 2016-07-01 
16:03:54,242 1492  ERROR 
[org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute job 
[jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, ses=GridJobSessionImpl 
[ses=GridTaskSessionImpl 
[taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
 dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, loc=true, 
sampleClsName=java.lang.String, pendingUndeploy=false, undeployed=false, 
usage=0]], 
taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
 sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
startTime=1467389034118, endTime=9223372036854775807, 
taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
failSpi=null, loadSpi=null, usage=1, fullSup=false, 
subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
[orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
[16:03:54] : [testQuorumEvents] [Test Output]
[FabricRunner-7] class org.apache.ignite.IgniteException: null

[16:03:54] : [:fabric-tests:test] [FabricRunner-7] class 
org.apache.ignite.IgniteException: null
[16:03:54] : [testQuorumEvents] [Test Output]
[FabricRunner-7]at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)

[16:03:54] : [:fabric-tests:test] [FabricRunner-7]  at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
[16:03:54] : [testQuorumEvents] [Test Output]
[FabricRunner-7]at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)

[16:03:54] : [:fabric-tests:test] [FabricRunner-7]  at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
[16:03:54] : [testQuorumEvents] [Test Output]
[FabricRunner-7]at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6484)

[16:03:54] : [:fabric-tests:test] [FabricRunner-7]  at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6484)
[16:03:54] : [testQuorumEvents] [Test Output]
[FabricRunner-7]at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)

[16:03:54] : [:fabric-tests:test] [FabricRunner-7]  at 

[jira] [Updated] (IGNITE-3440) Ignite Services: ServiceTopologyCallable is executed before system cache is started

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-3440:

Affects Version/s: 1.6

> Ignite Services: ServiceTopologyCallable is executed before system cache is 
> started
> ---
>
> Key: IGNITE-3440
> URL: https://issues.apache.org/jira/browse/IGNITE-3440
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Denis Magda
>
> In rare cases it's possible to get the following exception
> {code}
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-0] 2016-07-01 
> 16:03:54,120 22971 INFO  
> [com.workday.fabric.ignite.management.QuorumEventDispatcher] Storage count 
> changed - oldvalue: 3 - newvalue: 4 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] 2016-07-01 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] 2016-07-01 
> 16:03:54,242 1492  ERROR 
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to execute 
> job [jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  dep=LocalDeployment [super=GridDeployment [ts=1467389033352, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, 
> clsLdrId=989b337a551-b26cd969-888f-4580-a2cb-ad10019da322, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.service.GridServiceProcessor$ServiceTopologyCallable,
>  sesId=9c1b337a551-33dedfed-ef93-405c-af02-cd37d7426df9, 
> startTime=1467389034118, endTime=9223372036854775807, 
> taskNodeId=33dedfed-ef93-405c-af02-cd37d7426df9, 
> clsLdr=sun.misc.Launcher$AppClassLoader@14dad5dc, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=33dedfed-ef93-405c-af02-cd37d7426df9, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1467389034228, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=ac1b337a551-b26cd969-888f-4580-a2cb-ad10019da322]] 
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7] class org.apache.ignite.IgniteException: null
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7] class 
> org.apache.ignite.IgniteException: null
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2007)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
> [16:03:54] :   [testQuorumEvents] [Test Output]
> [FabricRunner-7]  at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6484)
> [16:03:54] :   [:fabric-tests:test] [FabricRunner-7]  at 
> 

[jira] [Created] (IGNITE-3438) Caches: Add more info and examples to "Escape table and filed names" tooltip

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3438:


 Summary: Caches: Add more info and examples to "Escape table and 
filed names" tooltip
 Key: IGNITE-3438
 URL: https://issues.apache.org/jira/browse/IGNITE-3438
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7






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

[jira] [Resolved] (IGNITE-3363) Forward Java output to the .NET console

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-3363.

Resolution: Implemented

> Forward Java output to the .NET console
> ---
>
> Key: IGNITE-3363
> URL: https://issues.apache.org/jira/browse/IGNITE-3363
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.7
>
>
> Java console output is not visible in .NET tools (unit test runners, linqpad, 
> etc).
> On JVM start we should redirect all output via 
> java.lang.System.setOut()
> java.lang.System.setErr()



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

[jira] [Created] (IGNITE-3439) Caches: Add possibility to specify custom store and configure it via XML if needed.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3439:


 Summary: Caches: Add possibility to specify custom store and 
configure it via XML if needed.
 Key: IGNITE-3439
 URL: https://issues.apache.org/jira/browse/IGNITE-3439
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7


For now we could select only builtin stores (pojo, hibernate,...) but no way 
for user store. We should fix this.



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

[jira] [Commented] (IGNITE-3363) Forward Java output to the .NET console

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3363:


Github user asfgit closed the pull request at:

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


> Forward Java output to the .NET console
> ---
>
> Key: IGNITE-3363
> URL: https://issues.apache.org/jira/browse/IGNITE-3363
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.7
>
>
> Java console output is not visible in .NET tools (unit test runners, linqpad, 
> etc).
> On JVM start we should redirect all output via 
> java.lang.System.setOut()
> java.lang.System.setErr()



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

[jira] [Created] (IGNITE-3437) Caches: Start size - rename to Onheap start size and add more info into tooltip

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3437:


 Summary: Caches: Start size - rename to Onheap start size and add 
more info into tooltip
 Key: IGNITE-3437
 URL: https://issues.apache.org/jira/browse/IGNITE-3437
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7


And moe under "Mode"



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

[jira] [Created] (IGNITE-3436) Caches: make SQL schema tooltip more informative, add example.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3436:


 Summary: Caches: make SQL schema tooltip more informative, add 
example.
 Key: IGNITE-3436
 URL: https://issues.apache.org/jira/browse/IGNITE-3436
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7


For now it is not clear why we need this field.



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

[jira] [Created] (IGNITE-3435) Caches: rework off-heap memory selection

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3435:


 Summary: Caches: rework off-heap memory selection
 Key: IGNITE-3435
 URL: https://issues.apache.org/jira/browse/IGNITE-3435
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7


Instead of -1, 0 and some number - show dropdown with items: Disabled, 
Unlimited, Limited.
And when Limited selected - show input for numgber of bytes



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

[jira] [Created] (IGNITE-3434) Improve usability of Ignite Web Console

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3434:


 Summary: Improve usability of Ignite Web Console
 Key: IGNITE-3434
 URL: https://issues.apache.org/jira/browse/IGNITE-3434
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.7


This a parent ticket for usability of Ignite Web Console.

Main idea - all should be obvious as much as possible.
All tooltips should contains information as much as possible, with examples.



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

[jira] [Closed] (IGNITE-3418) TcpDiscoverySpi: lots of duplicated node failed messages

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-3418.

Assignee: (was: Semen Boikov)

> TcpDiscoverySpi: lots of duplicated node failed messages
> 
>
> Key: IGNITE-3418
> URL: https://issues.apache.org/jira/browse/IGNITE-3418
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
>Reporter: Semen Boikov
>Priority: Critical
> Fix For: 1.7
>
>
> Currently in TcpDiscoverySpi there is safety check called when discovery 
> worker thread is idle: if node from 'failed list' still in ring then send 
> 'node failed' message for such node ('ServerImpl.checkFailedNodesList'). This 
> can lead to lots of duplicated unnecessary messages. 
> This check should be changed: need send event only once and only in case when 
> node which marked node as failed left cluster.



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

[jira] [Closed] (IGNITE-3428) TcpCommunicationSpi: potential message lost during reconnect

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-3428.

Assignee: (was: Semen Boikov)

> TcpCommunicationSpi: potential message lost during reconnect
> 
>
> Key: IGNITE-3428
> URL: https://issues.apache.org/jira/browse/IGNITE-3428
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Semen Boikov
>Priority: Critical
>
> Added test reproducing lost message during reconnect: 
> IgniteCacheMessageRecoveryIdleConnection. 
> It is possible that method 'send' finished, then connection closed, there are 
> unacknowledged messages, but communication does not try to reconnect (if 
> there are no others messages to be sent to this node).
> Looks like there are at least 2 issues:
> - 'onDisconnected' checks result of 'clients.remove(id, rmv)' to trigger 
> reconnect. this is not saf (e.g. client is removed when session is closed on 
> idle timeout)
> - 'onDisconnected' checks that messagesFutures() collection is not empty, but 
> 'onDisconnected' is erroneously called before all futures are polled from 
> closing session (GridNioService.AbstractNioClientWorker.close)



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

[jira] [Resolved] (IGNITE-3428) TcpCommunicationSpi: potential message lost during reconnect

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-3428.
--
Resolution: Fixed

Fixed in master (commit #e9a508e).

> TcpCommunicationSpi: potential message lost during reconnect
> 
>
> Key: IGNITE-3428
> URL: https://issues.apache.org/jira/browse/IGNITE-3428
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
>
> Added test reproducing lost message during reconnect: 
> IgniteCacheMessageRecoveryIdleConnection. 
> It is possible that method 'send' finished, then connection closed, there are 
> unacknowledged messages, but communication does not try to reconnect (if 
> there are no others messages to be sent to this node).
> Looks like there are at least 2 issues:
> - 'onDisconnected' checks result of 'clients.remove(id, rmv)' to trigger 
> reconnect. this is not saf (e.g. client is removed when session is closed on 
> idle timeout)
> - 'onDisconnected' checks that messagesFutures() collection is not empty, but 
> 'onDisconnected' is erroneously called before all futures are polled from 
> closing session (GridNioService.AbstractNioClientWorker.close)



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

[jira] [Resolved] (IGNITE-3418) TcpDiscoverySpi: lots of duplicated node failed messages

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-3418.
--
Resolution: Fixed

Fixed in master (commit #2e65beb).

> TcpDiscoverySpi: lots of duplicated node failed messages
> 
>
> Key: IGNITE-3418
> URL: https://issues.apache.org/jira/browse/IGNITE-3418
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.7
>
>
> Currently in TcpDiscoverySpi there is safety check called when discovery 
> worker thread is idle: if node from 'failed list' still in ring then send 
> 'node failed' message for such node ('ServerImpl.checkFailedNodesList'). This 
> can lead to lots of duplicated unnecessary messages. 
> This check should be changed: need send event only once and only in case when 
> node which marked node as failed left cluster.



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

[jira] [Commented] (IGNITE-3426) Compute Engine: job ID is generated in a non unique way

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-3426:
-

Merged and closed.

> Compute Engine: job ID is generated in a non unique way
> ---
>
> Key: IGNITE-3426
> URL: https://issues.apache.org/jira/browse/IGNITE-3426
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Magda
>Assignee: Denis Magda
>
> Presently seems like new job IDs are generated in a way that is not 
> guaranteed to be unique.
> Specifically, job IDs are generated in: 
> {code}
> IgniteUuid jobId = IgniteUuid.fromUuid(node.id());
> org/apache/ignite/internal/processors/task/GridTaskWorker.java:564)
> {code}
> fromUuid generates the new job ID using UUID passed to it + an AtomicInteger 
> (who is always incremented). Since the UUID passed to it is the *destination 
> node* and not the local node, in environments where the job submission is 
> relatively even, the generated job ID might not be unique.
> Think that the UUID used there is supposed to be the local node UUID.
> Otherwise this can be a reason of the following exception
> {noformat}
>  "Jobs map already contains mapping for key" 
> {noformat}



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

[jira] [Closed] (IGNITE-3426) Compute Engine: job ID is generated in a non unique way

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-3426.
---

> Compute Engine: job ID is generated in a non unique way
> ---
>
> Key: IGNITE-3426
> URL: https://issues.apache.org/jira/browse/IGNITE-3426
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Magda
>Assignee: Denis Magda
>
> Presently seems like new job IDs are generated in a way that is not 
> guaranteed to be unique.
> Specifically, job IDs are generated in: 
> {code}
> IgniteUuid jobId = IgniteUuid.fromUuid(node.id());
> org/apache/ignite/internal/processors/task/GridTaskWorker.java:564)
> {code}
> fromUuid generates the new job ID using UUID passed to it + an AtomicInteger 
> (who is always incremented). Since the UUID passed to it is the *destination 
> node* and not the local node, in environments where the job submission is 
> relatively even, the generated job ID might not be unique.
> Think that the UUID used there is supposed to be the local node UUID.
> Otherwise this can be a reason of the following exception
> {noformat}
>  "Jobs map already contains mapping for key" 
> {noformat}



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

[jira] [Updated] (IGNITE-3433) Uninformative error message for affinity function

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov updated IGNITE-3433:
-
Attachment: SimpleTest.patch

> Uninformative error message for affinity function
> -
>
> Key: IGNITE-3433
> URL: https://issues.apache.org/jira/browse/IGNITE-3433
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.6
>Reporter: Nikolay Tikhonov
>Priority: Minor
> Fix For: 1.7
>
> Attachments: SimpleTest.patch
>
>
> Ignite public API allows to get an affinity function for not existing cache. 
> Any method calls lead to NPE and user getting the following error message:
> {noformat}
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$AffinityInfo.access$1800(GridAffinityProcessor.java:538)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$CacheAffinityProxy.allPartitions(GridAffinityProcessor.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityApiSelfTest.testAllPartitionsException(GridCacheAffinityApiSelfTest.java:241)
>   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:1724)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1662)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Need to change the message and make it more clear..



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

[jira] [Created] (IGNITE-3433) Uninformative error message for affinity function

[Nikolay Tikhonov (JIRA)]

Nikolay Tikhonov created IGNITE-3433:


 Summary: Uninformative error message for affinity function
 Key: IGNITE-3433
 URL: https://issues.apache.org/jira/browse/IGNITE-3433
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 1.6
Reporter: Nikolay Tikhonov
Priority: Minor
 Fix For: 1.7


Ignite public API allows to get an affinity function for not existing cache. 
Any method calls lead to NPE and user getting the following error message:
{noformat}
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$AffinityInfo.access$1800(GridAffinityProcessor.java:538)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$CacheAffinityProxy.allPartitions(GridAffinityProcessor.java:766)
at 
org.apache.ignite.internal.processors.cache.GridCacheAffinityApiSelfTest.testAllPartitionsException(GridCacheAffinityApiSelfTest.java:241)
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:1724)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1662)
at java.lang.Thread.run(Thread.java:745)
{noformat}

Need to change the message and make it more clear..



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

[jira] [Created] (IGNITE-3432) Multiple IGFS on the same caches.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3432:
-

 Summary: Multiple IGFS on the same caches.
 Key: IGNITE-3432
 URL: https://issues.apache.org/jira/browse/IGNITE-3432
 Project: Ignite
  Issue Type: Bug
  Components: IGFS
Affects Versions: 1.7
Reporter: Vasiliy Sisko


# Configure grid with two IGFSs which use the same caches.
# Run two server nodes. 
#* Topology is runned. Written data marked in both IGFSs.
# Run client node.
#* On node start showed validation message that two IGFSs cannot use the same 
caches.



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

[jira] [Updated] (IGNITE-3432) Multiple IGFS on the same caches.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3432:

Fix Version/s: 1.7

> Multiple IGFS on the same caches.
> -
>
> Key: IGNITE-3432
> URL: https://issues.apache.org/jira/browse/IGNITE-3432
> Project: Ignite
>  Issue Type: Bug
>  Components: IGFS
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
> Fix For: 1.7
>
>
> # Configure grid with two IGFSs which use the same caches.
> # Run two server nodes. 
> #* Topology is runned. Written data marked in both IGFSs.
> # Run client node.
> #* On node start showed validation message that two IGFSs cannot use the same 
> caches.



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

[jira] [Commented] (IGNITE-3363) Forward Java output to the .NET console

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3363:


Replaced single ConsoleWriteHandler with a vector. Now the first domain 
receives all the output. Multidomain test added.

> Forward Java output to the .NET console
> ---
>
> Key: IGNITE-3363
> URL: https://issues.apache.org/jira/browse/IGNITE-3363
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.7
>
>
> Java console output is not visible in .NET tools (unit test runners, linqpad, 
> etc).
> On JVM start we should redirect all output via 
> java.lang.System.setOut()
> java.lang.System.setErr()



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

[jira] [Closed] (IGNITE-3393) Mvn build warning

[Roman Shtykh (JIRA)]

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

Roman Shtykh closed IGNITE-3393.


> Mvn build warning
> -
>
> Key: IGNITE-3393
> URL: https://issues.apache.org/jira/browse/IGNITE-3393
> Project: Ignite
>  Issue Type: Bug
> Environment: mac os
>Reporter: lukasz gintowt
>Assignee: Roman Shtykh
>
> command `mvn build`
> yeilds:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.ignite:ignite-spring:jar:1.7.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.h2database:h2:jar -> duplicate declaration of version 
> ${h2.version} @ line 121, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [INFO] 
> 
> {code}



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

[jira] [Commented] (IGNITE-3431) Error message have wrong position when message is longer than 1 row.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-3431:
---

Fixed location of popover message when message is longer than 1 row.

> Error message have wrong position when message is longer than 1 row.
> 
>
> Key: IGNITE-3431
> URL: https://issues.apache.org/jira/browse/IGNITE-3431
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 1.7
>
> Attachments: Wrong message position.png
>
>




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

[jira] [Updated] (IGNITE-3431) Error message have wrong position when message is longer than 1 row.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-3431:
--
Attachment: Wrong message position.png

> Error message have wrong position when message is longer than 1 row.
> 
>
> Key: IGNITE-3431
> URL: https://issues.apache.org/jira/browse/IGNITE-3431
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.7
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 1.7
>
> Attachments: Wrong message position.png
>
>




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

[jira] [Created] (IGNITE-3431) Error message have wrong position when message is longer than 1 row.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3431:
-

 Summary: Error message have wrong position when message is longer 
than 1 row.
 Key: IGNITE-3431
 URL: https://issues.apache.org/jira/browse/IGNITE-3431
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.7
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko






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

[jira] [Issue Comment Deleted] (IGNITE-2310) Lock cache partition for affinityRun/affinityCall execution

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-2310:
-
Comment: was deleted

(was: I think test with failed unmarshaling of a job's results doesn't make 
sense. Because job's results unmarshaling is executed on the master node but 
partitions are reserved on the job node. May be test with job results 
marshaling failure make sense?
)

> Lock cache partition for affinityRun/affinityCall execution
> ---
>
> Key: IGNITE-2310
> URL: https://issues.apache.org/jira/browse/IGNITE-2310
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Taras Ledkov
>Priority: Critical
>  Labels: community
> Fix For: 1.7
>
>
> Partition of a key passed to {{affinityRun}} must be located on the affinity 
> node when a compute job is being sent to the node. The partition has to be 
> locked on the cache until the compute job is being executed. This will let to 
> execute queries safely (Scan or local SQL) over the data that is located 
> locally in the locked partition.
> In addition Ignite Compute API has to be extended by adding {{affinityCall}} 
> and {{affinityRun}} methods that accept list of caches which partitions have 
> to be locked at the time a compute task is being executed.
> Test cases to validate the functionality:
> 1) local SQL query over data located in a concrete partition in multple 
> caches.
> - create cache Organisation cache and create Persons cache.
> - collocate Persons by 'organisationID';
> - send {{affinityRun}} using 'organisationID' as an affinity key and passing 
> Organisation and Persons caches' names to the method to be sure that the 
> partition will be locked on caches;
> - execute local SQL query "SELECT * FROM Persons as p, Organisation as o 
> WHERE p.orgId=o.id' on a changing topology. The result set must be complete, 
> the partition over which the query will be executed mustn't be moved to the 
> other node. Due to affinity collocation the partition number will be the same 
> for all Persons that belong to particular 'organisationID'
> 2) Scan Query over particular partition that is locked when {{affinityCall}} 
> is executed.  
> UPD (YZ May, 31)
> # If closure arrives to node but partition is not there it should be silently 
> failed over to current owner.
> # I don't think user should provide list of caches. How about reserving only 
> one partition, but evict partitions after all partitions in all caches (with 
> same affinity function) on this node are locked for eviction. [~sboikov], can 
> you please comment? It seems this should work faster for closures and will 
> hardly affect rebalancing stuff.
> # I would add method {{affinityCall(int partId, String cacheName, 
> IgniteCallable)}} and same for Runnable. This will allow me not to mess with 
> affinity key in case I know partition before.
> UPD (SB, June, 01)
> Yakov, I think it is possible to implement this 'locking for evictions' 
> approach, but personally I better like partitions reservation:
> - approach with reservation already implemented and works fine in sql queries
> - partition reservation is just CAS operation, if we need do ~10 reservation 
> I think this will be negligible comparing to  job execution time
> - now caches are rebalanced completely independently and changing this be 
> complicated refactoring
> - I see some difficulties how to understand that caches have same affinity. 
> If user uses custom function should he implement 'equals'? For standard 
> affinity functions user can set backup filter, what do in this case? should 
> user implement 'equals' for filter? Even if affinity functions are the same 
> cache configuration can have node filter, so affinity mapping will be 
> different. 



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

[jira] [Commented] (IGNITE-3393) Mvn build warning

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3393:


GitHub user shroman opened a pull request:

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

IGNITE-3393: Maven build warning on duplicate dependency declaration



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

$ git pull https://github.com/shroman/ignite master

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

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


commit 34b62610bd4e3be34946b8df943fb26111c8805a
Author: shtykh_roman 
Date:   2016-07-06T07:25:19Z

IGNITE-3393: Maven build warning on duplicate dependency declaration




> Mvn build warning
> -
>
> Key: IGNITE-3393
> URL: https://issues.apache.org/jira/browse/IGNITE-3393
> Project: Ignite
>  Issue Type: Bug
> Environment: mac os
>Reporter: lukasz gintowt
>Assignee: Roman Shtykh
>
> command `mvn build`
> yeilds:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.ignite:ignite-spring:jar:1.7.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.h2database:h2:jar -> duplicate declaration of version 
> ${h2.version} @ line 121, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [INFO] 
> 
> {code}



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

[jira] [Assigned] (IGNITE-3393) Mvn build warning

[Roman Shtykh (JIRA)]

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

Roman Shtykh reassigned IGNITE-3393:


Assignee: Roman Shtykh

> Mvn build warning
> -
>
> Key: IGNITE-3393
> URL: https://issues.apache.org/jira/browse/IGNITE-3393
> Project: Ignite
>  Issue Type: Bug
> Environment: mac os
>Reporter: lukasz gintowt
>Assignee: Roman Shtykh
>
> command `mvn build`
> yeilds:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.ignite:ignite-spring:jar:1.7.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.h2database:h2:jar -> duplicate declaration of version 
> ${h2.version} @ line 121, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> [INFO] 
> 
> {code}



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

[jira] [Updated] (IGNITE-3102) .NET: Call user-defined constructor for IBinarizable objects

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3102:
---
Description: 
Currently we create user objects with FormatterServices.GetUninitializedObject 
and then call user-defined IBinarizable.ReadBinary method.

This is not convenient both for us and the user:
* FormatterServices.GetUninitializedObject is not a clean way of constructing 
objects
* User-defined constructor does not get called
* User types can't have readonly fields

For example, ISerializable mechanism does not have Read method; it calls 
user-defined constructor instead. We should provide similar mechanism.

* To maintain compatibility, we may have to introduce a new interface with a 
single Write method, and call user-defined ctor on read.
* Another option is to introduce a [BinarizableInit] attribute. User can place 
it on a constructor, and Ignite will call it, injecting Reader and Ignite 
instances to parameters (if there are any).

  was:
Currently we create user objects with FormatterServices.GetUninitializedObject 
and then call user-defined IBinarizable.ReadBinary method.

This is not convenient both for us and the user:
* FormatterServices.GetUninitializedObject is not a clean way of constructing 
objects
* User-defined constructor does not get called
* User types can't have readonly fields

For example, ISerializable mechanism does not have Read method; it calls 
user-defined constructor instead. We should provide similar mechanism.

To maintain compatibility, we may have to introduce a new interface with a 
single Write method, and call user-defined ctor on read.


> .NET: Call user-defined constructor for IBinarizable objects
> 
>
> Key: IGNITE-3102
> URL: https://issues.apache.org/jira/browse/IGNITE-3102
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.7
>
>
> Currently we create user objects with 
> FormatterServices.GetUninitializedObject and then call user-defined 
> IBinarizable.ReadBinary method.
> This is not convenient both for us and the user:
> * FormatterServices.GetUninitializedObject is not a clean way of constructing 
> objects
> * User-defined constructor does not get called
> * User types can't have readonly fields
> For example, ISerializable mechanism does not have Read method; it calls 
> user-defined constructor instead. We should provide similar mechanism.
> * To maintain compatibility, we may have to introduce a new interface with a 
> single Write method, and call user-defined ctor on read.
> * Another option is to introduce a [BinarizableInit] attribute. User can 
> place it on a constructor, and Ignite will call it, injecting Reader and 
> Ignite instances to parameters (if there are any).



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

[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-2079:
--

Alexey, 
We print the whole stack trace now.
+ 1 for EVT_UNHANDLED_EXCEPTION.

> GridCacheIoManager eats exception trail if it falls into the directed case
> --
>
> Key: IGNITE-2079
> URL: https://issues.apache.org/jira/browse/IGNITE-2079
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Andrey Velichko
>  Labels: important
> Fix For: 1.7
>
> Attachments: IgniteCacheP2pUnmarshallingContinuousQueryErrorTest.java
>
>
> During a recent test I have run into an issue where a storage disabled client 
> of a Fabric that has services deployed for which the client does not have the 
> fabric in the class path failed with the following exception:
> com.company.fabric.HelloWorldTest STANDARD_ERROR
> Nov 08, 2015 6:15:20 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to process message 
> [senderId=30775397-457a-400f-a6c9-077c9e762d61, messageType=class 
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to 
> node. Unsupported direct type [message=GridCacheQueryResponse [finished=true, 
> reqId=5, err=null, fields=false, metadata=null]]
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:546)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:272)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1078)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
>  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:745)
> This unfortunately gives me 0 information to work on to resolve the issue, as 
> the original unmarshalling exception (from the JdkMarshaller) was eaten as 
> this is the code for the default process failed message:
> default:
> throw new IgniteCheckedException("Failed to send response to node. 
> Unsupported direct type [message="
> + msg + "]");
> }
> you should also include the original stack from msg.getError() in the newly 
> thrown IgniteCheckedException



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

[jira] [Created] (IGNITE-3430) .NET: Run Ignite transactions via standard TransactionScope API

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3430:
--

 Summary: .NET: Run Ignite transactions via standard 
TransactionScope API
 Key: IGNITE-3430
 URL: https://issues.apache.org/jira/browse/IGNITE-3430
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
 Fix For: 1.7


Automatically enlist Ignite operations in current transaction scope when 
applicable (when cache is transactional).

https://msdn.microsoft.com/en-us/library/system.transactions.transactionscope(v=vs.110).aspx



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

[jira] [Updated] (IGNITE-3429) org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-3429:

Priority: Critical  (was: Major)

> org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
> -
>
> Key: IGNITE-3429
> URL: https://issues.apache.org/jira/browse/IGNITE-3429
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.7
>
>
> {{org.hibernate.cache.spi.CacheKey}} is a class used as a key for all entries 
> in the Hibernate L2 cache. This class contains {{type}} field and custom 
> {{equals}} logic where the type is used as a helper and does not participate 
> in comparison. Instances of the same type are producing different hash codes 
> in different JVMs, which actually breaks comparison when binary format is 
> used, where byte arrays are compared.
> The issue is described in more detail here: 
> http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities



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