[jira] [Assigned] (IGNITE-5357) Replicated cache reads load balancing.
[ https://issues.apache.org/jira/browse/IGNITE-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Do reassigned IGNITE-5357: -- Assignee: (was: William Do) > Replicated cache reads load balancing. > -- > > Key: IGNITE-5357 > URL: https://issues.apache.org/jira/browse/IGNITE-5357 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6 >Reporter: Alexei Scherbakov > Labels: newbie > Fix For: 2.3 > > > Currently all read requests from client node to replicated cache will go > through primary node for key. > Need to select random affinity node in topology and send request here (only > if readFromBackups=true) > If where are server nodes collocated on same host with client, must select > target node from them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5444) Collections.singletonList is not properly serialized by binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062129#comment-16062129
]
William Do commented on IGNITE-5444:
I looked at the code again and realised my mistake about serialized form.
[~ezhuravl] can you provide example collection that deserializes back to
ArrayList? I tried LinkedList but that came back deserialized with same
implementation.
> Collections.singletonList is not properly serialized by binary marshaller
> -
>
> Key: IGNITE-5444
> URL: https://issues.apache.org/jira/browse/IGNITE-5444
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: William Do
> Fix For: 2.1
>
> Attachments: BinaryObjectSingletonList.java
>
>
> Test attached. {{Collections.singletonList}} is apparently serialized by
> optimized marshaller, because when deserialized, it doesn't return collection
> of binary objects, but rather collection of deserialized objects.
> Most likely the reason for this is that {{Collections.singletonList}} is not
> recognized by {{BinaryUtils.knownCollection}} method.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5357) Replicated cache reads load balancing.
[ https://issues.apache.org/jira/browse/IGNITE-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Do reassigned IGNITE-5357: -- Assignee: William Do > Replicated cache reads load balancing. > -- > > Key: IGNITE-5357 > URL: https://issues.apache.org/jira/browse/IGNITE-5357 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Assignee: William Do > Labels: newbie > Fix For: 2.2 > > > Currently all read requests from client node to replicated cache will go > through primary node for key. > Need to select random affinity node in topology and send request here (only > if readFromBackups=true) > If where are server nodes collocated on same host with client, must select > target node from them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5444) Collections.singletonList is not properly serialized by binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061579#comment-16061579
]
William Do commented on IGNITE-5444:
I believe the issue is to do with the serialized form, which in this case the
desired outcome is to be stored as a {{SingletonList}} of binary objects.
The same issue also occurs for {{Collections.unmodifiableList}}. I think
ideally we want to add these types to both {{BinaryUtils.knownCollection}} and
{{BinaryUtils.isSpecialCollection}}. The latter is the one being used to
identify serialization of collection types.
However both of these are private static classes within {{Collections}} and I
am not quite sure how to proceed yet.
> Collections.singletonList is not properly serialized by binary marshaller
> -
>
> Key: IGNITE-5444
> URL: https://issues.apache.org/jira/browse/IGNITE-5444
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: William Do
> Fix For: 2.1
>
> Attachments: BinaryObjectSingletonList.java
>
>
> Test attached. {{Collections.singletonList}} is apparently serialized by
> optimized marshaller, because when deserialized, it doesn't return collection
> of binary objects, but rather collection of deserialized objects.
> Most likely the reason for this is that {{Collections.singletonList}} is not
> recognized by {{BinaryUtils.knownCollection}} method.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5444) Collections.singletonList is not properly serialized by binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Do reassigned IGNITE-5444:
--
Assignee: William Do
> Collections.singletonList is not properly serialized by binary marshaller
> -
>
> Key: IGNITE-5444
> URL: https://issues.apache.org/jira/browse/IGNITE-5444
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: William Do
> Fix For: 2.1
>
> Attachments: BinaryObjectSingletonList.java
>
>
> Test attached. {{Collections.singletonList}} is apparently serialized by
> optimized marshaller, because when deserialized, it doesn't return collection
> of binary objects, but rather collection of deserialized objects.
> Most likely the reason for this is that {{Collections.singletonList}} is not
> recognized by {{BinaryUtils.knownCollection}} method.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4324) ScanQuery throws incomprehensible exception when topology does not contain data nodes
[
https://issues.apache.org/jira/browse/IGNITE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045033#comment-16045033
]
William Do commented on IGNITE-4324:
[~ntikhonov], yes it's all good thanks!
> ScanQuery throws incomprehensible exception when topology does not contain
> data nodes
> -
>
> Key: IGNITE-4324
> URL: https://issues.apache.org/jira/browse/IGNITE-4324
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7, 1.8
>Reporter: Nikolay Tikhonov
>Assignee: William Do
> Labels: newbie
> Fix For: 2.1
>
> Attachments: Tests.patch
>
>
> ScanQuery throws incomprehensible exception when topology does not contain
> data nodes (for example with node filter). See attached test.
> {code}
> java.lang.IllegalArgumentException: bound must be positive
> at java.util.Random.nextInt(Random.java:388)
> at org.apache.ignite.internal.util.lang.GridFunc.rand(GridFunc.java:677)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.nodes(GridCacheQueryAdapter.java:582)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:527)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4119)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4094)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.iterator(IgniteCacheProxy.java:1979)
> at
> org.apache.ignite.internal.CacheFilterQueryTest.testScanQuery(CacheFilterQueryTest.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1768)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1706)
> at java.lang.Thread.run(Thread.java:745)
> [
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4324) ScanQuery throws incomprehensible exception when topology does not contain data nodes
[
https://issues.apache.org/jira/browse/IGNITE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Do reassigned IGNITE-4324:
--
Assignee: William Do
> ScanQuery throws incomprehensible exception when topology does not contain
> data nodes
> -
>
> Key: IGNITE-4324
> URL: https://issues.apache.org/jira/browse/IGNITE-4324
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7, 1.8
>Reporter: Nikolay Tikhonov
>Assignee: William Do
> Labels: newbie
> Fix For: 2.1
>
> Attachments: Tests.patch
>
>
> ScanQuery throws incomprehensible exception when topology does not contain
> data nodes (for example with node filter). See attached test.
> {code}
> java.lang.IllegalArgumentException: bound must be positive
> at java.util.Random.nextInt(Random.java:388)
> at org.apache.ignite.internal.util.lang.GridFunc.rand(GridFunc.java:677)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.nodes(GridCacheQueryAdapter.java:582)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.executeScanQuery(GridCacheQueryAdapter.java:527)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4119)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.igniteIterator(GridCacheAdapter.java:4094)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.iterator(IgniteCacheProxy.java:1979)
> at
> org.apache.ignite.internal.CacheFilterQueryTest.testScanQuery(CacheFilterQueryTest.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1768)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1706)
> at java.lang.Thread.run(Thread.java:745)
> [
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-5119) Provide more descriptive errors when calling affinityRun or affinityCall
[
https://issues.apache.org/jira/browse/IGNITE-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999468#comment-15999468
]
William Do edited comment on IGNITE-5119 at 5/6/17 4:30 PM:
The exception is thrown from {{GridAffinityProcessor.partition0}} after null
check on return of {{affinityCache}}.
There is a similar method {{CacheAffinityProxy.cache}} which makes the same
call to {{affinityCache}} but returns a more descriptive message.
{code:java}
private AffinityInfo cache() throws IgniteCheckedException {
AffinityInfo aff = affinityCache(cacheName,
ctx.discovery().topologyVersionEx());
if (aff == null)
throw new IgniteException("Failed to find cache (cache was not started
" +
"yet or cache was already stopped): " + cacheName);
return aff;
}
{code}
I propose using a similar message for this patch:
{noformat}
Failed to get cache affinity (cache was not started yet or cache was already
stopped): cacheName
{noformat}
was (Author: williamdo):
The exception is thrown from {{GridAffinityProcessor.partition0}} after null
check on return of {{affinityCache}}.
There is a similar method {{CacheAffinityProxy.cache}} which makes the same
call to {{affinityCache}} but returns a more descriptive message.
{code:java}
private AffinityInfo cache() throws IgniteCheckedException {
AffinityInfo aff = affinityCache(cacheName,
ctx.discovery().topologyVersionEx());
if (aff == null)
throw new IgniteException("Failed to find cache (cache was not started
" +
"yet or cache was already stopped): " + cacheName);
return aff;
}
{code}
I propose re-using the same message for this patch.
> Provide more descriptive errors when calling affinityRun or affinityCall
>
>
> Key: IGNITE-5119
> URL: https://issues.apache.org/jira/browse/IGNITE-5119
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: William Do
>Assignee: William Do
>Priority: Minor
>
> When calling compute affinityRun or affinityCall using a cache name that
> doesn't exist, an exception is thrown with the message: _Failed to get cache
> affinity_.
> {noformat}
> Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
> get cache affinity.
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
> at
> com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get
> cache affinity.
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
> ... 1 more
> {noformat}
> It would be nice if the message could be more descriptive as to why it was
> unable to determine the affinity (in this case because the cache doesn't
> exist).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-5119) Provide more descriptive errors when calling affinityRun or affinityCall
[
https://issues.apache.org/jira/browse/IGNITE-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999468#comment-15999468
]
William Do commented on IGNITE-5119:
The exception is thrown from {{GridAffinityProcessor.partition0}} after null
check on return of {{affinityCache}}.
There is a similar method {{CacheAffinityProxy.cache}} which makes the same
call to {{affinityCache}} but returns a more descriptive message.
{code:java}
private AffinityInfo cache() throws IgniteCheckedException {
AffinityInfo aff = affinityCache(cacheName,
ctx.discovery().topologyVersionEx());
if (aff == null)
throw new IgniteException("Failed to find cache (cache was not started
" +
"yet or cache was already stopped): " + cacheName);
return aff;
}
{code}
I propose re-using the same message for this patch.
> Provide more descriptive errors when calling affinityRun or affinityCall
>
>
> Key: IGNITE-5119
> URL: https://issues.apache.org/jira/browse/IGNITE-5119
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: William Do
>Assignee: William Do
>Priority: Minor
>
> When calling compute affinityRun or affinityCall using a cache name that
> doesn't exist, an exception is thrown with the message: _Failed to get cache
> affinity_.
> {noformat}
> Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
> get cache affinity.
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
> at
> com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get
> cache affinity.
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
> ... 1 more
> {noformat}
> It would be nice if the message could be more descriptive as to why it was
> unable to determine the affinity (in this case because the cache doesn't
> exist).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-5119) Provide more descriptive errors when calling affinityRun or affinityCall
[
https://issues.apache.org/jira/browse/IGNITE-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Do reassigned IGNITE-5119:
--
Assignee: William Do
> Provide more descriptive errors when calling affinityRun or affinityCall
>
>
> Key: IGNITE-5119
> URL: https://issues.apache.org/jira/browse/IGNITE-5119
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: William Do
>Assignee: William Do
>Priority: Minor
>
> When calling compute affinityRun or affinityCall using a cache name that
> doesn't exist, an exception is thrown with the message: _Failed to get cache
> affinity_.
> {noformat}
> Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
> get cache affinity.
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
> at
> com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get
> cache affinity.
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
> ... 1 more
> {noformat}
> It would be nice if the message could be more descriptive as to why it was
> unable to determine the affinity (in this case because the cache doesn't
> exist).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5119) Provide more descriptive errors when calling affinityRun or affinityCall
[
https://issues.apache.org/jira/browse/IGNITE-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Do updated IGNITE-5119:
---
Description:
When calling compute affinityRun or affinityCall using a cache name that
doesn't exist, an exception is thrown with the message: _Failed to get cache
affinity_.
{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
get cache affinity.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
at
com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get cache
affinity.
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
... 1 more
{noformat}
It would be nice if the message could be more descriptive as to why it was
unable to determine the affinity (in this case because the cache doesn't exist).
was:
When calling compute affinityRun or affinityCall using a cache name that
doesn't exist, an exception is thrown with the message: _Failed to get cache
affinity_.
{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
get cache affinity.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
at
com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get cache
affinity.
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
... 1 more
{noformat}
It would be nice if the message could give a more descriptive message as to why
it was unable to determine the affinity (in this case because the cache doesn't
exist).
> Provide more descriptive errors when calling affinityRun or affinityCall
>
>
> Key: IGNITE-5119
> URL: https://issues.apache.org/jira/browse/IGNITE-5119
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: William Do
>Priority: Minor
>
> When calling compute affinityRun or affinityCall using a cache name that
> doesn't exist, an exception is thrown with the message: _Failed to get cache
> affinity_.
> {noformat}
> Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
> get cache affinity.
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
> at
> com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get
> cache affinity.
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
> at
> org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
> ... 1 more
> {noformat}
> It would be nice if the message could be more descriptive as to why it was
> unable to determine the affinity (in this case because the cache doesn't
> exist).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-5119) Provide more descriptive errors when calling affinityRun or affinityCall
William Do created IGNITE-5119:
--
Summary: Provide more descriptive errors when calling affinityRun
or affinityCall
Key: IGNITE-5119
URL: https://issues.apache.org/jira/browse/IGNITE-5119
Project: Ignite
Issue Type: Improvement
Affects Versions: 1.9
Reporter: William Do
Priority: Minor
When calling compute affinityRun or affinityCall using a cache name that
doesn't exist, an exception is thrown with the message: _Failed to get cache
affinity_.
{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
get cache affinity.
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
at
com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get cache
affinity.
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
at
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
... 1 more
{noformat}
It would be nice if the message could give a more descriptive message as to why
it was unable to determine the affinity (in this case because the cache doesn't
exist).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
