[jira] [Commented] (IGNITE-529) Implement IgniteFlumeStreamer to stream data from Apache Flume

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-529:
-

Roman, 

R> Ok. So a cache is created based on what is in Ignite configurations xml, 
right?
A> Cache name should be provided via param (simmilar to current solution). The 
only one reason for using ignite.cache(cacheName) (not allowing 
getOrCreateCache()) is that we need guarantee that no redundant cache will be 
created because of wrong Sink configuration.

R> Do you mean the transformer is something more than just converting Flume 
event to key types of the cache? Something that exposes a cache instance 
to the user and the user can choose whether to use put() or putAll() in his/her 
implementation?
R> I wouldn't expose the cache to the user – just let him/her implement data 
conversion interface to specify at configuration (2) in your proposal) and use 
putAll() since this will probably be the most used method considering batching 
is good for large data loads (even if creating maps may introduce memory 
overheads).
R > What do you think?
A> I think initial implementation can use code simillat to following:
  try {
transaction.begin();
event = channel.take();

if (event != null)
cache.putAll(transformer.transform(event))
else
status = Status.BACKOFF;

transaction.commit();
}

But, usage of IgniteDataStreamer can brings more speed in case you'll gain a 
lot of keys while processing event.
Seems that custom transformer can produce huge amount of data. Is it possible 
case?
In this case generation of Map and using putAll will brings memory overhead and 
delays. Transformer which do datastreamder.put() while processing event and 
flush() at it's finish will handle event faster. But i'm still not sure it's 
possible case.

R> What instance to you have in mind? Normally it is sufficient to have a 
channel and a sink, as it is in my tests. Our you can run it as I described in 
README (but that is not for tests).
A> I see you forcing 
channel.put(event); like Flume will.
That seems to be correct test case, But I wonder is it possible to brings mode 
Flume to test, use embedded Flume or something like this ;). Thats just a 
question not proposal.


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



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

[jira] [Commented] (IGNITE-1884) .Net: JNI local ref can't be accessed from another thread

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn commented on IGNITE-1884:
-

1,2) Both of these cases go down to ThrowToJava. It just sets an exception in 
Java, but does not affect C++ program flow. So the handle won't leak.
http://mindprod.com/jgloss/jni.html#EXCEPTIONS

However, in future there may be the case with C++ or some other client where 
exceptions are possible. I'll address this with a wrapper/destructor.

3,4) Creating a wrapper and checking thread id would also introduce an 
overhead. Before doing this, we need to make sure if that is actually faster 
than GlobalRef. Let's do that separately.

> .Net: JNI local ref can't be accessed from another thread
> -
>
> Key: IGNITE-1884
> URL: https://issues.apache.org/jira/browse/IGNITE-1884
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
>Priority: Blocker
> Fix For: 1.5
>
>
> Documentation: 
> https://docs.oracle.com/javase/7/docs/technotes/guides/jni/spec/design.html
> {code}
> Local references are only valid in the thread in which they are created. The 
> native code must not pass local references from one thread to another.
> {code}
> We have two places where we DO pass local JNI reference to another thread:
> * CacheParallelLoadStoreAdapter
> * CacheTestStore.LoadCache
> And, potentially (due to user code):
> * UnmanagedCallbacks.DataStreamerStreamReceiverInvoke
> For some reason it has worked for us before.
> But renamings in IGNITE-1881 have caused test execution order to change, and 
> these store tests cause process crash.
> To reproduce, BinaryBuilderSelfTest (former PortableApiSelfTest) has to be 
> executed before store tests. All other tests can be excluded. 100% repro 
> rate: "FATAL ERROR in native method: Bad global or local ref passed to JNI".



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

[jira] [Assigned] (IGNITE-1681) loadAll threshold is not configurable for CacheStoreBalancingWrapper

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-1681:
---

Assignee: Denis Magda  (was: Michael Griggs)

> loadAll threshold is not configurable for CacheStoreBalancingWrapper
> 
>
> Key: IGNITE-1681
> URL: https://issues.apache.org/jira/browse/IGNITE-1681
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Denis Magda
> Fix For: 1.5
>
> Attachments: master_6844370_ignite-1681.patch
>
>
> CacheStoreBalancingWrapper is created in cache store manager using default 
> constructor. There is no way to override a default value for loadAllThreshold.
> We can add a cache configuration parameter named 
> storeConcurrentLoadAllThreshold to control this:
> {code}
> CacheConfiguration {
> ...
> public int getStoreConcurrentLoadAllThreshold() {...}
> public void setStoreConcurrentLoadAllThreshold(int 
> storeConcurrentLoadAllThreshold) {...}
> ...
> }
> {code}



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

[jira] [Commented] (IGNITE-1845) .Net: Adopt portable API changes.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn commented on IGNITE-1845:
-

Please make sure you check PR#212. It certainly has these changes: 
https://github.com/apache/ignite/pull/212/files

> .Net: Adopt portable API changes.
> -
>
> Key: IGNITE-1845
> URL: https://issues.apache.org/jira/browse/IGNITE-1845
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Blocker
> Fix For: 1.5
>
>
> Important API changes will be introduced as a part of IGNITE-950. 
> Once these changes are in place, we need to port them to .Net.



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

[jira] [Closed] (IGNITE-1845) .Net: Adopt portable API changes.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-1845.
---

> .Net: Adopt portable API changes.
> -
>
> Key: IGNITE-1845
> URL: https://issues.apache.org/jira/browse/IGNITE-1845
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Important API changes will be introduced as a part of IGNITE-950. 
> Once these changes are in place, we need to port them to .Net.



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

[jira] [Assigned] (IGNITE-1639) IGFS: IgfsMetaManager contains duplicated "delete" method.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky reassigned IGNITE-1639:
---

Assignee: Ivan Veselovsky

> IGFS: IgfsMetaManager contains duplicated "delete" method.
> --
>
> Key: IGNITE-1639
> URL: https://issues.apache.org/jira/browse/IGNITE-1639
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Ivan Veselovsky
> Fix For: 1.6
>
>
> Our metamanager has two "delete" methods which do roughly the same thing: 
> delete leafs and update parent listing. But one method remove collection of 
> leafs, while another remove only single leaf.
> Do we really need to have them as separate methods? Looks like them can be 
> merged into one.



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

[jira] [Commented] (IGNITE-1788) Duplicate check of IGFS configuration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1788:


GitHub user iveselovskiy opened a pull request:

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

IGNITE-1788: duplicate checking is removed.



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

$ git pull https://github.com/iveselovskiy/ignite ignite-1788

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

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


commit ab8bd09f6b74a9b8267e65d9a459a6b1dc7ca498
Author: iveselovskiy 
Date:   2015-11-11T17:35:57Z

IGNITE-1788: duplicate checking is removed.




> Duplicate check of IGFS configuration
> -
>
> Key: IGNITE-1788
> URL: https://issues.apache.org/jira/browse/IGNITE-1788
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
>Assignee: Ivan Veselovsky
>Priority: Minor
> Fix For: 1.5
>
>
> In class org.apache.ignite.internal.processors.igfs.IgfsProcessor exist 
> duplicate check:
> {code}
> if (GridQueryProcessor.isEnabled(metaCacheCfg))
> throw new IgniteCheckedException("IGFS metadata cache cannot start with 
> enabled query indexing.");
> {code}



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

[jira] [Assigned] (IGNITE-1788) Duplicate check of IGFS configuration

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky reassigned IGNITE-1788:
---

Assignee: Ivan Veselovsky

> Duplicate check of IGFS configuration
> -
>
> Key: IGNITE-1788
> URL: https://issues.apache.org/jira/browse/IGNITE-1788
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
>Assignee: Ivan Veselovsky
>Priority: Minor
> Fix For: 1.5
>
>
> In class org.apache.ignite.internal.processors.igfs.IgfsProcessor exist 
> duplicate check:
> {code}
> if (GridQueryProcessor.isEnabled(metaCacheCfg))
> throw new IgniteCheckedException("IGFS metadata cache cannot start with 
> enabled query indexing.");
> {code}



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

[jira] [Commented] (IGNITE-1694) .Net: More efficient way to call native methods.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn commented on IGNITE-1694:
-

* [DllImport] works fine after LoadLibrary call, no additional changes required.
* PutBenchmark ~2% faster.
* TC ok.

> .Net: More efficient way to call native methods.
> 
>
> Key: IGNITE-1694
> URL: https://issues.apache.org/jira/browse/IGNITE-1694
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: 1.6
>
>
> Currently we invoke native platform using 
> "Marshal.GetDelegateForFunctionPointer". 
> This is the least efficient way to call external code. What can be done to 
> improve it:
> 1) Add [SuppressUnmanagedCodeSecurity] attribute.
> 2) Use P/Invoke instead. We do not use it now because we unpack native 
> library in runtime into some temp folder, while PInvoke searches for 
> libraries in predefined file system places. Need to evaluate whether we can 
> switch back to P/Invoke somehow.
> See 
> http://ybeernet.blogspot.ru/2011/03/techniques-of-calling-unmanaged-code.html 
> for more info.



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

[jira] [Resolved] (IGNITE-770) Revise IgniteHadoopFileSystem#close() implementation

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky resolved IGNITE-770.

Resolution: Fixed

This request is not relevant any more: this code was refactored some time ago  
as a result of other fixes.

> Revise IgniteHadoopFileSystem#close() implementation 
> -
>
> Key: IGNITE-770
> URL: https://issues.apache.org/jira/browse/IGNITE-770
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: sprint-4
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
> Fix For: 1.5
>
>
> Current code of this method is:
> {code}
> @Override public void close() throws IOException {
> if (cacheEnabled && get(getUri(), getConf()) == this)
> return;
> close0();
> }
> {code}
> This code sometimes creates a new instance of the IgniteHadoopFileSystem in 
> the #get(2) call. This creation is expensive. Looks like this is not quite 
> the behavior what was expected by the author of code. 
> Need to investigate why that happens and possibly modify the code accordingly.



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

[jira] [Assigned] (IGNITE-1637) IGFS: Consistent properties propagation.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky reassigned IGNITE-1637:
---

Assignee: Ivan Veselovsky

> IGFS: Consistent properties propagation.
> 
>
> Key: IGNITE-1637
> URL: https://issues.apache.org/jira/browse/IGNITE-1637
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Ivan Veselovsky
>Priority: Critical
> Fix For: 1.5
>
>
> IGFS has methods accepting properties map. E.g., create, append, mkdirs. 
> How we should apply these properties? Two strategies are possible:
> 1) Apply there properties only to leaf node, and set defaults to parent nodes.
> 2) Apply there properties to all created nodes.
> Lets take HDFS as a reference for this. 



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

[jira] [Updated] (IGNITE-578) Java examples need to update javadoc

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-578:
--
Fix Version/s: 1.6

> Java examples need to update javadoc
> 
>
> Key: IGNITE-578
> URL: https://issues.apache.org/jira/browse/IGNITE-578
> Project: Ignite
>  Issue Type: Bug
> Environment: Ubuntu 14.04, Upload Ignite Staging build #102 for 
> sprint-2 (ver. 1.0.0#20150325-sha1:3462d744)
>Reporter: Vasilisa  Sidorova
>Assignee: Semen Boikov
>Priority: Minor
> Fix For: 1.6
>
>
> In the current version these examples:
> * CacheStarSchemaExample
> * CacheDummyStoreExample
> * CacheHibernateStoreExample
> * CacheJdbcStoreExample
> could be started with ExampleNodeStartup only. So javadoc should be updated 
> like for CacheQueryExample, ServicesExample, streaming examples, 
> ScalaCacheQueryExample and ScalaSnowflakeSchemaExample. The text:
> {noformat}
> Remote nodes should always be started with special configuration file which 
> enables P2P class loading: {@code 'ignite.{sh|bat} 
> examples/config/example-ignite.xml'}. 
> Alternatively you can run {@link ExampleNodeStartup} in another JVM which 
> will start node with {@code examples/config/example-ignite.xml} configuration.
> {noformat}
> should be replaced by text:
> "
> Remote nodes should be started using `ExampleNodeStartup` which will  start 
> node with `examples/config/example-ignite.xml` configuration.
> "



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

[jira] [Commented] (IGNITE-1681) loadAll threshold is not configurable for CacheStoreBalancingWrapper

[Michael Griggs (JIRA)]

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

Michael Griggs commented on IGNITE-1681:


Denis, please accept my apologies for having caused you extra work, and thank 
you for cleaning up after me on this occasion.  I will review the two patches 
and make sure that my next submissions are cleaner and in line with coding 
standards, javadoc, naming conventions, etc. Thanks again!

> loadAll threshold is not configurable for CacheStoreBalancingWrapper
> 
>
> Key: IGNITE-1681
> URL: https://issues.apache.org/jira/browse/IGNITE-1681
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Denis Magda
> Fix For: 1.5
>
> Attachments: ignite-1681-final.patch
>
>
> CacheStoreBalancingWrapper is created in cache store manager using default 
> constructor. There is no way to override a default value for loadAllThreshold.
> We can add a cache configuration parameter named 
> storeConcurrentLoadAllThreshold to control this:
> {code}
> CacheConfiguration {
> ...
> public int getStoreConcurrentLoadAllThreshold() {...}
> public void setStoreConcurrentLoadAllThreshold(int 
> storeConcurrentLoadAllThreshold) {...}
> ...
> }
> {code}



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

[jira] [Resolved] (IGNITE-1620) [Test failed] IGFS:Directory creation in DUAL mode failed

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky resolved IGNITE-1620.
-
Resolution: Fixed

This seems to be not reproducible, the test is not muted any more.

> [Test failed] IGFS:Directory creation in DUAL mode failed
> -
>
> Key: IGNITE-1620
> URL: https://issues.apache.org/jira/browse/IGNITE-1620
> Project: Ignite
>  Issue Type: Test
>Reporter: Andrey Gura
>Assignee: Ivan Veselovsky
>Priority: Blocker
>  Labels: Muted_test
> Fix For: 1.5
>
>
> {{Hadoop1OverIgfsDualAsyncTest.testMkdirs}} and {{ 
> Hadoop1OverIgfsDualSyncTest.testMkdirs}} test are failed.
> {noformat}
> [10:33:24,212][ERROR][test-runner][IgfsMetaManager] Directory creation in 
> DUAL mode failed [path=/d/f, properties={permission=0777}]
> class org.apache.ignite.IgniteException: Failed to make directories 
> [path=/d/f, props={permission=0777}]
> at 
> org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.mkdirs(IgniteHadoopIgfsSecondaryFileSystem.java:303)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onSuccess(IgfsMetaManager.java:2483)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onSuccess(IgfsMetaManager.java:2481)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3051)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.mkdirsDual(IgfsMetaManager.java:2526)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:782)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2014)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.mkdirs(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testMkdirs(IgfsAbstractSelfTest.java:766)
> 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:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> [10:33:24,214][ERROR][main][root] Test failed.
> class org.apache.ignite.igfs.IgfsException: Generic IGFS error occurred.
> at 
> org.apache.ignite.internal.processors.igfs.IgfsUtils.toIgfsException(IgfsUtils.java:76)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2017)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.mkdirs(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testMkdirs(IgfsAbstractSelfTest.java:766)
> 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:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
> the path due to secondary file system exception: /d/f
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onFailure(IgfsMetaManager.java:2520)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onFailure(IgfsMetaManager.java:2481)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3054)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.mkdirsDual(IgfsMetaManager.java:2526)
> at 
> 

[jira] [Closed] (IGNITE-1620) [Test failed] IGFS:Directory creation in DUAL mode failed

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky closed IGNITE-1620.
---

> [Test failed] IGFS:Directory creation in DUAL mode failed
> -
>
> Key: IGNITE-1620
> URL: https://issues.apache.org/jira/browse/IGNITE-1620
> Project: Ignite
>  Issue Type: Test
>Reporter: Andrey Gura
>Assignee: Ivan Veselovsky
>Priority: Blocker
>  Labels: Muted_test
> Fix For: 1.5
>
>
> {{Hadoop1OverIgfsDualAsyncTest.testMkdirs}} and {{ 
> Hadoop1OverIgfsDualSyncTest.testMkdirs}} test are failed.
> {noformat}
> [10:33:24,212][ERROR][test-runner][IgfsMetaManager] Directory creation in 
> DUAL mode failed [path=/d/f, properties={permission=0777}]
> class org.apache.ignite.IgniteException: Failed to make directories 
> [path=/d/f, props={permission=0777}]
> at 
> org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.mkdirs(IgniteHadoopIgfsSecondaryFileSystem.java:303)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onSuccess(IgfsMetaManager.java:2483)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onSuccess(IgfsMetaManager.java:2481)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3051)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.mkdirsDual(IgfsMetaManager.java:2526)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:782)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2014)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.mkdirs(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testMkdirs(IgfsAbstractSelfTest.java:766)
> 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:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> [10:33:24,214][ERROR][main][root] Test failed.
> class org.apache.ignite.igfs.IgfsException: Generic IGFS error occurred.
> at 
> org.apache.ignite.internal.processors.igfs.IgfsUtils.toIgfsException(IgfsUtils.java:76)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2017)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.mkdirs(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testMkdirs(IgfsAbstractSelfTest.java:766)
> 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:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
> the path due to secondary file system exception: /d/f
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onFailure(IgfsMetaManager.java:2520)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onFailure(IgfsMetaManager.java:2481)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3054)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.mkdirsDual(IgfsMetaManager.java:2526)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:782)
> at 
> 

[jira] [Resolved] (IGNITE-686) HadoopClientProtocolEmbeddedSelfTest.testJobCounters failed.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky resolved IGNITE-686.

Resolution: Fixed

This seems to be not reproducible any more.

> HadoopClientProtocolEmbeddedSelfTest.testJobCounters failed.
> 
>
> Key: IGNITE-686
> URL: https://issues.apache.org/jira/browse/IGNITE-686
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>Assignee: Ivan Veselovsky
> Fix For: 1.5
>
>
> java.io.IOException: Failed to get new job ID.
> at 
> org.apache.ignite.internal.processors.hadoop.proto.HadoopClientProtocol.getNewJobID(HadoopClientProtocol.java:90)
> at 
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:357)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1285)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1282)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1282)
> at 
> org.apache.ignite.client.hadoop.HadoopClientProtocolSelfTest.testJobCounters(HadoopClientProtocolSelfTest.java:189)
> 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:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1346)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:67)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$2.run(GridAbstractTest.java:1289)
> Caused by: org.apache.ignite.internal.client.GridClientDisconnectedException: 
> Latest topology update failed.
> at 
> org.apache.ignite.internal.client.impl.connection.GridClientTopology.nodes(GridClientTopology.java:318)
> at 
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.projectionNodes(GridClientAbstractProjection.java:299)
> at 
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.balancedNode(GridClientAbstractProjection.java:339)
> at 
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.withReconnectHandling(GridClientAbstractProjection.java:96)
> at 
> org.apache.ignite.internal.client.impl.GridClientComputeImpl.executeAsync(GridClientComputeImpl.java:124)
> at 
> org.apache.ignite.internal.client.impl.GridClientComputeImpl.execute(GridClientComputeImpl.java:113)
> at 
> org.apache.ignite.internal.processors.hadoop.proto.HadoopClientProtocol.getNewJobID(HadoopClientProtocol.java:83)
> at 
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:357)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1285)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1282)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1282)
> at 
> org.apache.ignite.client.hadoop.HadoopClientProtocolSelfTest.testJobCounters(HadoopClientProtocolSelfTest.java:189)
> 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:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1346)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:67)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$2.run(GridAbstractTest.java:1289)
> Caused by: org.apache.ignite.internal.client.GridServerUnreachableException: 
> Failed to connect to any of the servers in list: [/127.0.0.1:11212]
> at 
> org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:387)
> at 
> 

[jira] [Closed] (IGNITE-686) HadoopClientProtocolEmbeddedSelfTest.testJobCounters failed.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky closed IGNITE-686.
--

> HadoopClientProtocolEmbeddedSelfTest.testJobCounters failed.
> 
>
> Key: IGNITE-686
> URL: https://issues.apache.org/jira/browse/IGNITE-686
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>Assignee: Ivan Veselovsky
> Fix For: 1.5
>
>
> java.io.IOException: Failed to get new job ID.
> at 
> org.apache.ignite.internal.processors.hadoop.proto.HadoopClientProtocol.getNewJobID(HadoopClientProtocol.java:90)
> at 
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:357)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1285)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1282)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1282)
> at 
> org.apache.ignite.client.hadoop.HadoopClientProtocolSelfTest.testJobCounters(HadoopClientProtocolSelfTest.java:189)
> 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:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1346)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:67)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$2.run(GridAbstractTest.java:1289)
> Caused by: org.apache.ignite.internal.client.GridClientDisconnectedException: 
> Latest topology update failed.
> at 
> org.apache.ignite.internal.client.impl.connection.GridClientTopology.nodes(GridClientTopology.java:318)
> at 
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.projectionNodes(GridClientAbstractProjection.java:299)
> at 
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.balancedNode(GridClientAbstractProjection.java:339)
> at 
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.withReconnectHandling(GridClientAbstractProjection.java:96)
> at 
> org.apache.ignite.internal.client.impl.GridClientComputeImpl.executeAsync(GridClientComputeImpl.java:124)
> at 
> org.apache.ignite.internal.client.impl.GridClientComputeImpl.execute(GridClientComputeImpl.java:113)
> at 
> org.apache.ignite.internal.processors.hadoop.proto.HadoopClientProtocol.getNewJobID(HadoopClientProtocol.java:83)
> at 
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:357)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1285)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1282)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1282)
> at 
> org.apache.ignite.client.hadoop.HadoopClientProtocolSelfTest.testJobCounters(HadoopClientProtocolSelfTest.java:189)
> 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:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1346)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:67)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$2.run(GridAbstractTest.java:1289)
> Caused by: org.apache.ignite.internal.client.GridServerUnreachableException: 
> Failed to connect to any of the servers in list: [/127.0.0.1:11212]
> at 
> org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:387)
> at 
> org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.init(GridClientConnectionManagerAdapter.java:199)
> at 
> 

[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-1369:
---
Fix Version/s: (was: 1.5)
   1.6

> CacheClientPortableQueryExample fails when remote node is started without 
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 1.6
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
>   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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class 
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And 
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. 
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
> which will
>  * start node with {@code 
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description



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

[jira] [Updated] (IGNITE-1566) Hadoop: In case if IGFS name is missing in the URI, the connection failure message should be more informative.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky updated IGNITE-1566:

Assignee: Vladimir Ozerov  (was: Ivan Veselovsky)

> Hadoop: In case if IGFS name is missing in the URI, the connection failure 
> message should be more informative.
> --
>
> Key: IGNITE-1566
> URL: https://issues.apache.org/jira/browse/IGNITE-1566
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
>Assignee: Vladimir Ozerov
>
> User has IGFS "igfs" configured in Ignite node.
> After that he tries to connect to it with hadoop client using command
> {code}
> $ hadoop fs -ls igfs://127.0.0.1:10500/
> {code}
> And gets the following error message:
> {code}ls: Failed to communicate with IGFS.{code} .
> The problem is that IGFS name is missing in the URI. But the error message 
> does not give any hint about that.



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

[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-1369:
---
Fix Version/s: 1.5

> CacheClientPortableQueryExample fails when remote node is started without 
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 1.5
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
>   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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class 
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And 
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. 
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
> which will
>  * start node with {@code 
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description



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

[jira] [Commented] (IGNITE-1694) .Net: More efficient way to call native methods.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1694:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1694 .Net: More efficient way to call native methods.



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

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

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

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


commit 7966a36aa604adc0df0afa310856295a06e9de1c
Author: Pavel Tupitsyn 
Date:   2015-11-11T13:22:57Z

first draft

commit e4290506e38a0e47077fb6aa7af6a0744340ec5c
Author: Pavel Tupitsyn 
Date:   2015-11-11T14:49:10Z

wip

commit 5aa5fcb5767aa6118fcbdc03c0352af05955d7b7
Author: Pavel Tupitsyn 
Date:   2015-11-11T15:01:30Z

Delegates done

commit d63261a79eea6999849024e369b68cb15d35f4ab
Author: Pavel Tupitsyn 
Date:   2015-11-11T15:02:34Z

SuppressUnmanagedCodeSecurity

commit 6ad92dfe76903e4ddd62ef7d5b4e489a3dd00c7d
Author: Pavel Tupitsyn 
Date:   2015-11-11T15:09:18Z

Reformatting

commit 4348b334760fce4c7998ed098df1cda5d77ff9fd
Author: Pavel Tupitsyn 
Date:   2015-11-11T15:14:21Z

Extract to a separate class

commit 97cfccc0906ba2c2ddf40f1f0ea66de4d9baba26
Author: Pavel Tupitsyn 
Date:   2015-11-11T15:15:53Z

wip

commit 8a6f448ced8b28aafc7d543cfb215f0d8e94ba83
Author: Pavel Tupitsyn 
Date:   2015-11-11T15:26:06Z

Fix naming style




> .Net: More efficient way to call native methods.
> 
>
> Key: IGNITE-1694
> URL: https://issues.apache.org/jira/browse/IGNITE-1694
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: 1.6
>
>
> Currently we invoke native platform using 
> "Marshal.GetDelegateForFunctionPointer". 
> This is the least efficient way to call external code. What can be done to 
> improve it:
> 1) Add [SuppressUnmanagedCodeSecurity] attribute.
> 2) Use P/Invoke instead. We do not use it now because we unpack native 
> library in runtime into some temp folder, while PInvoke searches for 
> libraries in predefined file system places. Need to evaluate whether we can 
> switch back to P/Invoke somehow.
> See 
> http://ybeernet.blogspot.ru/2011/03/techniques-of-calling-unmanaged-code.html 
> for more info.



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

[jira] [Commented] (IGNITE-1681) loadAll threshold is not configurable for CacheStoreBalancingWrapper

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-1681:
-

Michael, no worries, I just wanted to show you on your own code how to follow 
the guidelines and the rest of the stuff ;) 

Thanks!

> loadAll threshold is not configurable for CacheStoreBalancingWrapper
> 
>
> Key: IGNITE-1681
> URL: https://issues.apache.org/jira/browse/IGNITE-1681
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Denis Magda
> Fix For: 1.5
>
> Attachments: ignite-1681-final.patch
>
>
> CacheStoreBalancingWrapper is created in cache store manager using default 
> constructor. There is no way to override a default value for loadAllThreshold.
> We can add a cache configuration parameter named 
> storeConcurrentLoadAllThreshold to control this:
> {code}
> CacheConfiguration {
> ...
> public int getStoreConcurrentLoadAllThreshold() {...}
> public void setStoreConcurrentLoadAllThreshold(int 
> storeConcurrentLoadAllThreshold) {...}
> ...
> }
> {code}



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

[jira] [Closed] (IGNITE-770) Revise IgniteHadoopFileSystem#close() implementation

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky closed IGNITE-770.
--

> Revise IgniteHadoopFileSystem#close() implementation 
> -
>
> Key: IGNITE-770
> URL: https://issues.apache.org/jira/browse/IGNITE-770
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: sprint-4
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
> Fix For: 1.5
>
>
> Current code of this method is:
> {code}
> @Override public void close() throws IOException {
> if (cacheEnabled && get(getUri(), getConf()) == this)
> return;
> close0();
> }
> {code}
> This code sometimes creates a new instance of the IgniteHadoopFileSystem in 
> the #get(2) call. This creation is expensive. Looks like this is not quite 
> the behavior what was expected by the author of code. 
> Need to investigate why that happens and possibly modify the code accordingly.



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

[jira] [Comment Edited] (IGNITE-1566) Hadoop: In case if IGFS name is missing in the URI, the connection failure message should be more informative.

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky edited comment on IGNITE-1566 at 11/11/15 3:50 PM:
---

Relaxed slightly the logic of authority checking: if the URI authority does not 
containg IGFS name or Grid name, external (not embedded) connection is 
successful -- the IGFS owning this port is connected to. This is possible and 
is not contradictory because only one IGFS instance can be bound to a certain 
port.


was (Author: iveselovskiy):
Relaxed slightly the logic of authority checking: if the URI authority does not 
containg IGFS name or Grid name, connection is successful. This is possible and 
is not contradictory because only one IGFS instance can be bound to a certain 
port.

> Hadoop: In case if IGFS name is missing in the URI, the connection failure 
> message should be more informative.
> --
>
> Key: IGNITE-1566
> URL: https://issues.apache.org/jira/browse/IGNITE-1566
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
>Assignee: Vladimir Ozerov
>
> User has IGFS "igfs" configured in Ignite node.
> After that he tries to connect to it with hadoop client using command
> {code}
> $ hadoop fs -ls igfs://127.0.0.1:10500/
> {code}
> And gets the following error message:
> {code}ls: Failed to communicate with IGFS.{code} .
> The problem is that IGFS name is missing in the URI. But the error message 
> does not give any hint about that.



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

[jira] [Assigned] (IGNITE-1700) IgniteQueueExample fails with "org.apache.ignite.internal.portable.PortableObjectImpl incompatible with org.apache.ignite.internal.processors.datastructures.GridCacheQu

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova reassigned IGNITE-1700:
--

Assignee: Vasilisa  Sidorova  (was: Alexey Goncharuk)

Ok. I'll verify

> IgniteQueueExample fails with 
> "org.apache.ignite.internal.portable.PortableObjectImpl incompatible with 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueHeader" 
> exception when it's running with portableMarshaller
> --
>
> Key: IGNITE-1700
> URL: https://issues.apache.org/jira/browse/IGNITE-1700
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: Ubuntu 14.04, community 1.5.0 build #319
>Reporter: Vasilisa  Sidorova
>Assignee: Vasilisa  Sidorova
> Fix For: 1.5
>
>
> -
> DESCRIPTION
> -
> When default optimizedMarshaller is changed into portableMarshaller in 
> example-ignite.xml then IgniteQueueExample is failed with this config 
> -
> STEPS FOR REPRODUCE
> -
> 1. Build examples project in IDE
> 2.In the example-ignite.xml change property from:
> 
>  class="org.apache.ignite.marshaller.optimized.OptimizedMarshaller"> -->
> 
>  ACTUAL RESULT
> -
> Example is failed with exception:
> {noformat}
> Exception in thread "main" javax.cache.processor.EntryProcessorException: 
> java.lang.ClassCastException: 
> org.apache.ignite.internal.portable.PortableObjectImpl incompatible with 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueHeader
>   at 
> org.apache.ignite.internal.processors.cache.CacheInvokeResult.get(CacheInvokeResult.java:88)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridAtomicCacheQueueImpl.transformHeader(GridAtomicCacheQueueImpl.java:246)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridAtomicCacheQueueImpl.offer(GridAtomicCacheQueueImpl.java:52)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueAdapter.put(GridCacheQueueAdapter.java:226)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueProxy.put(GridCacheQueueProxy.java:598)
>   at 
> org.apache.ignite.examples.datastructures.IgniteQueueExample.initializeQueue(IgniteQueueExample.java:93)
>   at 
> org.apache.ignite.examples.datastructures.IgniteQueueExample.main(IgniteQueueExample.java:62)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
>   at java.lang.reflect.Method.invoke(Method.java:620)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: java.lang.ClassCastException: 
> org.apache.ignite.internal.portable.PortableObjectImpl incompatible with 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueHeader
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:86)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:58)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:542)
>   at 
> org.apache.ignite.internal.portable.PortableClassDescriptor.newInstance(PortableClassDescriptor.java:686)
>   at 
> org.apache.ignite.internal.portable.PortableClassDescriptor.read(PortableClassDescriptor.java:609)
>   at 
> org.apache.ignite.internal.portable.PortableReaderExImpl.deserialize(PortableReaderExImpl.java:2160)
>   at 
> org.apache.ignite.internal.portable.GridPortableMarshaller.deserialize(GridPortableMarshaller.java:274)
>   at 
> org.apache.ignite.internal.portable.api.PortableMarshaller.unmarshal(PortableMarshaller.java:328)
>   at 
> org.apache.ignite.internal.processors.cache.CacheInvokeDirectResult.finishUnmarshal(CacheInvokeDirectResult.java:123)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheReturn.finishUnmarshal(GridCacheReturn.java:321)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.finishUnmarshal(GridNearAtomicUpdateResponse.java:427)
>   at 
> 

[jira] [Updated] (IGNITE-1700) IgniteQueueExample fails with "org.apache.ignite.internal.portable.PortableObjectImpl incompatible with org.apache.ignite.internal.processors.datastructures.GridCacheQue

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-1700:
---
Fix Version/s: (was: 1.6)
   1.5

> IgniteQueueExample fails with 
> "org.apache.ignite.internal.portable.PortableObjectImpl incompatible with 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueHeader" 
> exception when it's running with portableMarshaller
> --
>
> Key: IGNITE-1700
> URL: https://issues.apache.org/jira/browse/IGNITE-1700
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: Ubuntu 14.04, community 1.5.0 build #319
>Reporter: Vasilisa  Sidorova
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> -
> DESCRIPTION
> -
> When default optimizedMarshaller is changed into portableMarshaller in 
> example-ignite.xml then IgniteQueueExample is failed with this config 
> -
> STEPS FOR REPRODUCE
> -
> 1. Build examples project in IDE
> 2.In the example-ignite.xml change property from:
> 
>  class="org.apache.ignite.marshaller.optimized.OptimizedMarshaller"> -->
> 
>  ACTUAL RESULT
> -
> Example is failed with exception:
> {noformat}
> Exception in thread "main" javax.cache.processor.EntryProcessorException: 
> java.lang.ClassCastException: 
> org.apache.ignite.internal.portable.PortableObjectImpl incompatible with 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueHeader
>   at 
> org.apache.ignite.internal.processors.cache.CacheInvokeResult.get(CacheInvokeResult.java:88)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridAtomicCacheQueueImpl.transformHeader(GridAtomicCacheQueueImpl.java:246)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridAtomicCacheQueueImpl.offer(GridAtomicCacheQueueImpl.java:52)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueAdapter.put(GridCacheQueueAdapter.java:226)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueProxy.put(GridCacheQueueProxy.java:598)
>   at 
> org.apache.ignite.examples.datastructures.IgniteQueueExample.initializeQueue(IgniteQueueExample.java:93)
>   at 
> org.apache.ignite.examples.datastructures.IgniteQueueExample.main(IgniteQueueExample.java:62)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
>   at java.lang.reflect.Method.invoke(Method.java:620)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: java.lang.ClassCastException: 
> org.apache.ignite.internal.portable.PortableObjectImpl incompatible with 
> org.apache.ignite.internal.processors.datastructures.GridCacheQueueHeader
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:86)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:58)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:542)
>   at 
> org.apache.ignite.internal.portable.PortableClassDescriptor.newInstance(PortableClassDescriptor.java:686)
>   at 
> org.apache.ignite.internal.portable.PortableClassDescriptor.read(PortableClassDescriptor.java:609)
>   at 
> org.apache.ignite.internal.portable.PortableReaderExImpl.deserialize(PortableReaderExImpl.java:2160)
>   at 
> org.apache.ignite.internal.portable.GridPortableMarshaller.deserialize(GridPortableMarshaller.java:274)
>   at 
> org.apache.ignite.internal.portable.api.PortableMarshaller.unmarshal(PortableMarshaller.java:328)
>   at 
> org.apache.ignite.internal.processors.cache.CacheInvokeDirectResult.finishUnmarshal(CacheInvokeDirectResult.java:123)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheReturn.finishUnmarshal(GridCacheReturn.java:321)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.finishUnmarshal(GridNearAtomicUpdateResponse.java:427)
>   at 
> 

[jira] [Updated] (IGNITE-1268) CacheAPIExample should have non-empty result

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-1268:
---
Fix Version/s: 1.6

> CacheAPIExample should have non-empty result 
> -
>
> Key: IGNITE-1268
> URL: https://issues.apache.org/jira/browse/IGNITE-1268
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
> Environment: Ubuntu 14.04, apache-ignite-1.3.0-incubating
>Reporter: Vasilisa  Sidorova
>Priority: Minor
> Fix For: 1.6
>
>
> -
> DESCRIPTION
> -
> CacheAPIExample have empty result. It's non informational and non 
> user-friendly.
> -
> STEPS FOR REPRODUCE
> -
> 1. Download apache-ignite-1.3.0-incubating from ignite.apache.org
> 2. Build examples in the IDE
> 3. Run CacheAPIExample
> -
> ACTUAL RESULT
> -
> CacheAPIExample have empty result:
> {noformat}
> >>> Cache API example started.
> >>> Cache atomic map operation examples.
> {noformat}
> -
> EXPECTED RESULT
> -
> CacheAPIExample have informational result. It could be, for example, the 
> information about cache contents before and after put operations



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

[jira] [Updated] (IGNITE-1695) PortableMarshaller get "Can not set final java.util.Queue field org.apache.ignite.examples.computegrid" exception when ComputeContinuousMapperExample is running

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova updated IGNITE-1695:
---
Fix Version/s: (was: 1.5)
   1.6

> PortableMarshaller get "Can not set final java.util.Queue field 
> org.apache.ignite.examples.computegrid" exception when 
> ComputeContinuousMapperExample is running
> 
>
> Key: IGNITE-1695
> URL: https://issues.apache.org/jira/browse/IGNITE-1695
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: Ubuntu 14.04, community 1.5.0 build #319
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
> Fix For: 1.6
>
>
> -
> DESCRIPTION
> -
> When default optimizedMarshaller is changed into portableMarshaller in  
> example-ignite.xml then ComputeContinuousMapperExample is failed with this 
> config due to incorrect work of portableMarshaller
> -
> STEPS FOR REPRODUCE
> -
> 1. Build examples project in IDE
> 2.In the example-ignite.xml change property from:
> {noformat}
> 
>  class="org.apache.ignite.marshaller.optimized.OptimizedMarshaller"> -->
> 
>  ACTUAL RESULT
> -
> Example is failed with exception:
> {noformat}
> [16:55:22,620][ERROR][ignite-#28%sys-null%][GridTaskWorker] Failed to obtain 
> remote job result policy for result from ComputeTask.result(..) method (will 
> fail the whole task): GridJobResultImpl 
> [job=o.a.i.examples.computegrid.ComputeContinuousMapperExample$ContinuousMapperTask$1@95be237c,
>  sib=GridJobSiblingImpl 
> [sesId=b5798cb6051-006ac327-4ba6-44fe-9688-469189c8cb18, 
> jobId=46798cb6051-fca6518a-6843-4b3a-97cd-d5010a71e5c6, 
> nodeId=fca6518a-6843-4b3a-97cd-d5010a71e5c6, isJobDone=false], 
> jobCtx=GridJobContextImpl 
> [jobId=46798cb6051-fca6518a-6843-4b3a-97cd-d5010a71e5c6, timeoutObj=null, 
> attrs={}], node=TcpDiscoveryNode [id=fca6518a-6843-4b3a-97cd-d5010a71e5c6, 
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, 
> intOrder=1, lastExchangeTime=1444917320434, loc=false, 
> ver=1.5.0#20151012-sha1:6844370d, isClient=false], ex=class 
> o.a.i.compute.ComputeUserUndeclaredException: Failed to execute job due to 
> unexpected runtime exception 
> [jobId=46798cb6051-fca6518a-6843-4b3a-97cd-d5010a71e5c6, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.examples.computegrid.ComputeContinuousMapperExample$ContinuousMapperTask,
>  dep=GridDeployment [ts=1444917321187, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@9f78b40f, 
> clsLdrId=12958cb6051-fca6518a-6843-4b3a-97cd-d5010a71e5c6, userVer=0, 
> loc=true, 
> sampleClsName=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionMap,
>  pendingUndeploy=false, undeployed=false, usage=1], 
> taskClsName=o.a.i.examples.computegrid.ComputeContinuousMapperExample$ContinuousMapperTask,
>  sesId=b5798cb6051-006ac327-4ba6-44fe-9688-469189c8cb18, 
> startTime=1444917321444, endTime=9223372036854775807, 
> taskNodeId=006ac327-4ba6-44fe-9688-469189c8cb18, 
> clsLdr=sun.misc.Launcher$AppClassLoader@9f78b40f, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, 
> subjId=006ac327-4ba6-44fe-9688-469189c8cb18, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1444917322581, 
> endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]], 
> jobId=46798cb6051-fca6518a-6843-4b3a-97cd-d5010a71e5c6]], hasRes=true, 
> isCancelled=false, isOccupied=true]
> class org.apache.ignite.IgniteException: Remote job threw user exception 
> (override or implement ComputeTask.result(..) method if you would like to 
> have automatic failover for this exception).
>   at 
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
>   at 
> org.apache.ignite.examples.computegrid.ComputeContinuousMapperExample$ContinuousMapperTask.result(ComputeContinuousMapperExample.java:121)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:903)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:896)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6403)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:896)
>   at 
> 

[jira] [Created] (IGNITE-1890) ignitevisorcmd: description for "-dl" key for "log" command should be updated

[Vasilisa Sidorova (JIRA)]

Vasilisa  Sidorova created IGNITE-1890:
--

 Summary: ignitevisorcmd: description for "-dl" key for "log" 
command should be updated
 Key: IGNITE-1890
 URL: https://issues.apache.org/jira/browse/IGNITE-1890
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
Reporter: Vasilisa  Sidorova
Priority: Trivial
 Fix For: 1.6


-
DESCRIPTION
-
Description for "-dl" key for "log" command is obsoleted
-
STEPS FOR REPRODUCE
-
# Run ignitevisorcmd from IGNITE_HOME/bin
# Type "help log"
-
ACTUAL RESULT
-
The description of "-dl" is:
{noformat}
"-dl
Disables collecting of job and task fail events, licence violation 
events, cache rebalance events from remote nodes."
{noformat}
-
EXPECTED RESULT
-
The description of "-dl" is:
{noformat}
"-dl
Disables collecting of job and task fail events, cache rebalance events 
from remote nodes."
{noformat}



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

[jira] [Assigned] (IGNITE-1620) [Test failed] IGFS:Directory creation in DUAL mode failed

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky reassigned IGNITE-1620:
---

Assignee: Ivan Veselovsky

> [Test failed] IGFS:Directory creation in DUAL mode failed
> -
>
> Key: IGNITE-1620
> URL: https://issues.apache.org/jira/browse/IGNITE-1620
> Project: Ignite
>  Issue Type: Test
>Reporter: Andrey Gura
>Assignee: Ivan Veselovsky
>Priority: Blocker
>  Labels: Muted_test
> Fix For: 1.5
>
>
> {{Hadoop1OverIgfsDualAsyncTest.testMkdirs}} and {{ 
> Hadoop1OverIgfsDualSyncTest.testMkdirs}} test are failed.
> {noformat}
> [10:33:24,212][ERROR][test-runner][IgfsMetaManager] Directory creation in 
> DUAL mode failed [path=/d/f, properties={permission=0777}]
> class org.apache.ignite.IgniteException: Failed to make directories 
> [path=/d/f, props={permission=0777}]
> at 
> org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.mkdirs(IgniteHadoopIgfsSecondaryFileSystem.java:303)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onSuccess(IgfsMetaManager.java:2483)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onSuccess(IgfsMetaManager.java:2481)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3051)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.mkdirsDual(IgfsMetaManager.java:2526)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:782)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2014)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.mkdirs(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testMkdirs(IgfsAbstractSelfTest.java:766)
> 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:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> [10:33:24,214][ERROR][main][root] Test failed.
> class org.apache.ignite.igfs.IgfsException: Generic IGFS error occurred.
> at 
> org.apache.ignite.internal.processors.igfs.IgfsUtils.toIgfsException(IgfsUtils.java:76)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.safeOp(IgfsImpl.java:2017)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl.mkdirs(IgfsImpl.java:766)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsAbstractSelfTest.testMkdirs(IgfsAbstractSelfTest.java:766)
> 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:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
> the path due to secondary file system exception: /d/f
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onFailure(IgfsMetaManager.java:2520)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager$9.onFailure(IgfsMetaManager.java:2481)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:3054)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.synchronizeAndExecute(IgfsMetaManager.java:2860)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsMetaManager.mkdirsDual(IgfsMetaManager.java:2526)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsImpl$11.call(IgfsImpl.java:782)
> at 
> 

[jira] [Assigned] (IGNITE-1694) .Net: More efficient way to call native methods.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn reassigned IGNITE-1694:
---

Assignee: Pavel  Tupitsyn

> .Net: More efficient way to call native methods.
> 
>
> Key: IGNITE-1694
> URL: https://issues.apache.org/jira/browse/IGNITE-1694
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: 1.6
>
>
> Currently we invoke native platform using 
> "Marshal.GetDelegateForFunctionPointer". 
> This is the least efficient way to call external code. What can be done to 
> improve it:
> 1) Add [SuppressUnmanagedCodeSecurity] attribute.
> 2) Use P/Invoke instead. We do not use it now because we unpack native 
> library in runtime into some temp folder, while PInvoke searches for 
> libraries in predefined file system places. Need to evaluate whether we can 
> switch back to P/Invoke somehow.
> See 
> http://ybeernet.blogspot.ru/2011/03/techniques-of-calling-unmanaged-code.html 
> for more info.



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

[jira] [Assigned] (IGNITE-1886) NPE in H2 when running query with subselects

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin reassigned IGNITE-1886:
--

Assignee: Sergi Vladykin

> NPE in H2 when running query with subselects
> 
>
> Key: IGNITE-1886
> URL: https://issues.apache.org/jira/browse/IGNITE-1886
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Sergi Vladykin
>Priority: Critical
> Fix For: 1.5
>
>
> Test reproducing the issue is attached. NPE is thrown as a result (see below).
> Corresponding user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/Does-Ignite-support-nested-SQL-Queries-td1714.html
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Failed to parse query: SELECT a.* FROM 
> (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:636)
>   at 
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:70)
>   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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Failed to parse query: 
> SELECT a.* FROM (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:641)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:627)
>   ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> query: SELECT a.* FROM (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END 
> id FROM "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT 
> CASE WHEN og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1510)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:634)
>   ... 7 more
> Caused by: javax.cache.CacheException: Failed to parse query: SELECT a.* FROM 
> (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM 
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN 
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug, 
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:938)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:636)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:634)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
>   ... 8 more
> Caused by: org.h2.jdbc.JdbcSQLException: General error: 
> "java.lang.NullPointerException" [5-175]
>   at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
>   at org.h2.message.DbException.get(DbException.java:161)
>   at org.h2.message.DbException.convert(DbException.java:284)
>   at org.h2.message.DbException.toSQLException(DbException.java:257)
>   at org.h2.message.TraceObject.logAndConvert(TraceObject.java:368)
>   at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:270)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:935)
>   ... 12 more
> Caused by: java.lang.NullPointerException
>   at org.h2.expression.Function.getCost(Function.java:2391)
>   at 

[jira] [Commented] (IGNITE-1866) .Net: turn SerializableObjectHolder & DateTimeHolder into structs

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn commented on IGNITE-1866:
-

Implementation shows no performance increase in reader benchmarks.
And there is a drop in writer benchmarks due to boxing in 
IBinarySerializer.WriteBinary call.

Not efficient, closing.

> .Net: turn SerializableObjectHolder & DateTimeHolder into structs
> -
>
> Key: IGNITE-1866
> URL: https://issues.apache.org/jira/browse/IGNITE-1866
> Project: Ignite
>  Issue Type: Improvement
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Reduce allocations on read and write



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

[jira] [Resolved] (IGNITE-1866) .Net: turn SerializableObjectHolder & DateTimeHolder into structs

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn resolved IGNITE-1866.
-
Resolution: Won't Fix

> .Net: turn SerializableObjectHolder & DateTimeHolder into structs
> -
>
> Key: IGNITE-1866
> URL: https://issues.apache.org/jira/browse/IGNITE-1866
> Project: Ignite
>  Issue Type: Improvement
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Reduce allocations on read and write



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

[jira] [Updated] (IGNITE-1544) Make sure objects number stored in a cache can be bigger than Integer.MAX_INT

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-1544:

Description: 
Make sure that a cache (partitioned) can actually hold number of objects bigger 
than {{Integer.MAX_VALUE}}. Because {{Integer.MAX_VALUE}} is not enough for 
some life use cases and business domains.

At least the following should be done:
- IgniteCache must return cache size as a {{long}} value;
- Make sure (make a test) that a partitioned cache can store number of objects 
much bigger than {{Integer.MAX_VALUE}};
- find and edit info regarding this limitation.

  was:
Make sure that a cache (partitioned) can actually hold number of objects bigger 
than Integer.MAX_INT. Because Integer.MAX_INT is not enough for some life use 
cases and business domains.

At least the following should be done:
- IgniteCache must return cache size as a {{long}} value;
- Make sure (make a test) that a partitioned cache can store number of objects 
much bigger than Integer.MAX_INT;
- find and edit info regarding this limitation.


> Make sure objects number stored in a cache can be bigger than Integer.MAX_INT
> -
>
> Key: IGNITE-1544
> URL: https://issues.apache.org/jira/browse/IGNITE-1544
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 1.5
>
>
> Make sure that a cache (partitioned) can actually hold number of objects 
> bigger than {{Integer.MAX_VALUE}}. Because {{Integer.MAX_VALUE}} is not 
> enough for some life use cases and business domains.
> At least the following should be done:
> - IgniteCache must return cache size as a {{long}} value;
> - Make sure (make a test) that a partitioned cache can store number of 
> objects much bigger than {{Integer.MAX_VALUE}};
> - find and edit info regarding this limitation.



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

[jira] [Updated] (IGNITE-1829) We must use short name for packages in metadata dropdown list

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-1829:
--
Fix Version/s: (was: 1.5)
   1.6

> We must use short name for packages in metadata dropdown list
> -
>
> Key: IGNITE-1829
> URL: https://issues.apache.org/jira/browse/IGNITE-1829
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: ig-1829.png
>
>
> Current view is uncomfortable because user don't see class name.
> Please see attachment.



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

[jira] [Commented] (IGNITE-1829) We must use short name for packages in metadata dropdown list

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-1829:
---

Implemented showing of tooltip for long values in dropdown.

> We must use short name for packages in metadata dropdown list
> -
>
> Key: IGNITE-1829
> URL: https://issues.apache.org/jira/browse/IGNITE-1829
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Critical
> Fix For: 1.5
>
> Attachments: ig-1829.png
>
>
> Current view is uncomfortable because user don't see class name.
> Please see attachment.



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

[jira] [Updated] (IGNITE-1829) We must use short name for packages in metadata dropdown list

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-1829:
--
Fix Version/s: (was: 1.6)
   1.5

> We must use short name for packages in metadata dropdown list
> -
>
> Key: IGNITE-1829
> URL: https://issues.apache.org/jira/browse/IGNITE-1829
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Critical
> Fix For: 1.5
>
> Attachments: ig-1829.png
>
>
> Current view is uncomfortable because user don't see class name.
> Please see attachment.



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

[jira] [Closed] (IGNITE-1868) Javadoc warnings for build

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-1868.
-
Assignee: Sergey Kozlov  (was: Anton Vinogradov)

Fixed

> Javadoc warnings for build
> --
>
> Key: IGNITE-1868
> URL: https://issues.apache.org/jira/browse/IGNITE-1868
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Minor
> Fix For: 1.5
>
>
> Build of Apache Ignite shows javadoc warnings:
> {noformat}
> [17:57:28] :   [exec] 4 warnings
> [17:57:28] :   [exec] [WARNING] 
> Javadoc Warnings
> [17:57:28] :   [exec] [WARNING] 
> /usr/local/BuildAgent/work/4b78de95608af2b1/apache-ignite/modules/core/src/main/java/org/apache/ignite/stream/StreamAdapter.java:39:
>  warning - Tag @link:illegal character: "60" in "Map"
> [17:57:28] :   [exec] [WARNING] 
> /usr/local/BuildAgent/work/4b78de95608af2b1/apache-ignite/modules/core/src/main/java/org/apache/ignite/stream/StreamAdapter.java:39:
>  warning - Tag @link: malformed: "Map"
> [17:57:28] :   [exec] [WARNING] 
> /usr/local/BuildAgent/work/4b78de95608af2b1/apache-ignite/modules/core/src/main/java/org/apache/ignite/stream/StreamAdapter.java:39:
>  warning - Tag @link: reference not found: Map
> [17:57:28] :   [exec] [WARNING] 
> /usr/local/BuildAgent/work/4b78de95608af2b1/apache-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/igfs/IgfsMetaManager.java:995:
>  warning - @return tag has no arguments.
> {noformat}



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

[jira] [Assigned] (IGNITE-1248) Add a method to retrieve Spring application context

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-1248:
--

Assignee: kcheng.mvp

> Add a method to retrieve Spring application context
> ---
>
> Key: IGNITE-1248
> URL: https://issues.apache.org/jira/browse/IGNITE-1248
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: kcheng.mvp
>
> Currently there is a way to inject application context instance into task, 
> closure, cache store using {{@SpringApplicationContextResource}} annotation. 
> But there is no way to get context associated with an {{Ignite}} instance 
> from user code.



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

[jira] [Resolved] (IGNITE-1829) We must use short name for packages in metadata dropdown list

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-1829.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> We must use short name for packages in metadata dropdown list
> -
>
> Key: IGNITE-1829
> URL: https://issues.apache.org/jira/browse/IGNITE-1829
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.5
>
> Attachments: ig-1829.png
>
>
> Current view is uncomfortable because user don't see class name.
> Please see attachment.



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

[jira] [Commented] (IGNITE-1859) Insufficient width for POJO dropdown on Summary page

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-1859:
---

# Increased width of pojo select dropdown. 
# Added showing of tooltips for long values in dropdowns.

> Insufficient width for POJO  dropdown on Summary page
> -
>
> Key: IGNITE-1859
> URL: https://issues.apache.org/jira/browse/IGNITE-1859
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 1.5
>
> Attachments: ig-1859.png
>
>
> Please see screen shot



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

[jira] [Updated] (IGNITE-1867) Fix java class names and package declaration

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-1867:
---
Assignee: Vasiliy Sisko  (was: Andrey Novikov)

> Fix java class names and package declaration
> 
>
> Key: IGNITE-1867
> URL: https://issues.apache.org/jira/browse/IGNITE-1867
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Prachi Garg
>Assignee: Vasiliy Sisko
> Fix For: 1.5
>
>
> I noticed a few issues when I imported my project, created using the web 
> console, in IDEA -
> 1. ServerConfigurationFactory class name is create in the file called 
> “ConfigurationFactory.java”. Class name and file name should be the same.
> 2. The package declaration for ClientConfigurationFactory and 
> SeverConfigurationFactory classes is missing.
> 3. There should be simple 'nodeStartup' class for starting a node, in the 
> IDE, using the XML configuration file.
> 4. Missing near configuration for client in java code.



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

[jira] [Resolved] (IGNITE-1859) Insufficient width for POJO dropdown on Summary page

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-1859.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Insufficient width for POJO  dropdown on Summary page
> -
>
> Key: IGNITE-1859
> URL: https://issues.apache.org/jira/browse/IGNITE-1859
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
> Attachments: ig-1859.png
>
>
> Please see screen shot



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

[jira] [Created] (IGNITE-1891) SSL on Windows

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-1891:
-

 Summary: SSL on Windows
 Key: IGNITE-1891
 URL: https://issues.apache.org/jira/browse/IGNITE-1891
 Project: Ignite
  Issue Type: Bug
Affects Versions: ignite-1.4, 1.5
 Environment: Windows 8, Windows 10,
Oracle JDK 1.7.0_80 64bit
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
Priority: Critical
 Fix For: 1.5


1. Copy examples/config/example-ignite.xml in 
examples/config/example-ignite-ssl.xml
2. Put SSL section:
{code:title=example-ignite-ssl.xml|borderStyle=solid}


http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xmlns:util="http://www.springframework.org/schema/util;
   xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd;>























































127.0.0.1:47500..47509








{code}
3. Start two nodes with the config above. Second node failed:
{noformat}
21:43:59,345][SEVERE][exchange-worker-#48%null%][GridDhtPartitionsExchangeFuture]
 Failed to send local partitions to oldest node (will retry after timeout) 
[oldestNodeId=37a2346c-3a07-4a96-a6da-c375cba47b41, 
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
minorTopVer=0], nodeId=de92d445, evt=NODE_JOINED]]
class org.apache.ignite.IgniteCheckedException: Failed to send message (node 
may have left the grid or TCP connection cannot be established due to firewall 
issues) [node=TcpDiscoveryNode [id=37a2346c-3a07-4a96-a6da-c375cba47b41, 
addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 192.168.100.9, 
2001:0:9d38:6ab8:2099:222b:4db9:9941], 
sockAddrs=[ksm-homepc/192.168.100.9:47500, 
0:0:0:0:0:0:0:1/0:0:0:0:0:0:0:1:47500, ksm-homepc/192.168.100.9:47500, 
/127.0.0.1:47500, /192.168.100.9:47500, 
/2001:0:9d38:6ab8:2099:222b:4db9:9941:47500], discPort=47500, order=1, 
intOrder=1, lastExchangeTime=1447267436638, loc=false, 
ver=1.5.0#2015-sha1:388a8921, isClient=false], topic=TOPIC_CACHE, 
msg=GridDhtPartitionsSingleMessage [parts={-2100569601=GridDhtPartitionMap 
[nodeId=de92d445-9162-43b1-ae84-fb8601a5e35c, updateSeq=2, moving=100, 
size=100], 689859866=GridDhtPartitionMap 
[nodeId=de92d445-9162-43b1-ae84-fb8601a5e35c, updateSeq=2, moving=511, 
size=511], 1325947219=GridDhtPartitionMap 
[nodeId=de92d445-9162-43b1-ae84-fb8601a5e35c, updateSeq=2, moving=20, 
size=20]}, client=false, super=GridDhtPartitionsAbstractMessage 
[exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
minorTopVer=0], nodeId=de92d445, evt=NODE_JOINED], lastVer=GridCacheVersion 
[topVer=0, nodeOrderDrId=0, globalTime=0, order=1447267431316], 
super=GridCacheMessage [msgId=1, depInfo=null, err=null, skipPrepare=false]]], 
policy=2]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1071)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1214)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:612)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:972)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1013)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:879)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1230)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(G

[jira] [Updated] (IGNITE-1889) FIFO eviction for atomic cache after removeAll

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-1889:
--
Description: 
1. Start 2 data nodes with following config
{code:title=config.xml|borderStyle=solid}













{code}
2. Start client and make following operations for cache_0001
2.1. put 100 entries
2.2. removeAll 
2.3. put 60 entries
2.4. get 60 entries (same keys from previous step)
2.5. got 40 entries only


  was:
1. Start data nodes with following config
{code:title=config.xml|borderStyle=solid}













{code}
2. Start client and make following operations for cache_0001
2.1. put 100 entries
2.2. removeAll 
2.3. put 60 entries
2.4. get 60 entries (same keys from previous step)
2.5. got 40 entries only



> FIFO eviction for atomic cache after removeAll
> --
>
> Key: IGNITE-1889
> URL: https://issues.apache.org/jira/browse/IGNITE-1889
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.6
>
>
> 1. Start 2 data nodes with following config
> {code:title=config.xml|borderStyle=solid}
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy">
> 
> 
> 
> 
> 
> 
> {code}
> 2. Start client and make following operations for cache_0001
> 2.1. put 100 entries
> 2.2. removeAll 
> 2.3. put 60 entries
> 2.4. get 60 entries (same keys from previous step)
> 2.5. got 40 entries only



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

[jira] [Commented] (IGNITE-1678) IgniteAtomicSequence: make following reservations in advance

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-1678:
--

Fixed some bugs in implementation. Now all tests pass.

Benchmarking status
- I benchmarked old and new implementation only on local machine (3 clients, 2 
servers)
- Current benchmark results show direct dependency between 
atomicSequenceReserveSize and op/sec. Look like only number of transactions 
cache op-s have meaning. Need to check it with many phisicale machines
- Need to solve with default percentage value.

Left:
- Add tests on new reserevePercetage paramether
- Create runners of GridCachePartitionedAtomicSequenceMultiThreadedTest in 
another modes: replicated, transactional
- Benchmark with many phisicale machines

> IgniteAtomicSequence: make following reservations in advance
> 
>
> Key: IGNITE-1678
> URL: https://issues.apache.org/jira/browse/IGNITE-1678
> Project: Ignite
>  Issue Type: Improvement
>  Components: data structures
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Artem Shutak
> Fix For: 1.6
>
>
> In current implementation a new reservation is made when the current local 
> sequence boundary is exceeded.
> In cases when there are many nodes that use the same atomic sequence there 
> can be a situation when all the nodes start doing a new reservation at the 
> same time. This can lead to performance drops.
> As a performance optimization it makes sense to start reserving new sequence 
> slot in advance (in background), like when around 80% of current reservation 
> has already been used. Probably we should add a special parameter to 
> {{AtomicConfiguration}} that will manage such behavior.



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