ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5119) Provide more descriptive errors when calling affinityRun or affinityCall
Date Sat, 06 May 2017 16:52:04 GMT

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

ASF GitHub Bot commented on IGNITE-5119:
----------------------------------------

GitHub user WilliamDo opened a pull request:

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

    IGNITE-5119 Append extra message to exception when unable to determine affinity

    Add detail on cache name to exception message when cache is not available and unable to
determine affinity.

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

    $ git pull https://github.com/WilliamDo/ignite IGNITE-5119

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

    https://github.com/apache/ignite/pull/1918.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 #1918
    
----
commit 617ddba72a0fd18eabf9db662e4d129042864462
Author: William Do <williamd0@outlook.com>
Date:   2017-05-06T16:47:57Z

    IGNITE-5119 Append extra message to exception when unable to determine affinity

----


> 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)

Mime
View raw message