geode-dev 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] (GEODE-3013) Reduce logging level for FunctionExceptions : InternalFunctionInvocationTargetException: Multiple target nodes found for single hop operation
Date Wed, 31 May 2017 18:32:04 GMT

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

ASF GitHub Bot commented on GEODE-3013:
---------------------------------------

GitHub user ladyVader opened a pull request:

    https://github.com/apache/geode/pull/552

    GEODE-3013: Reduce log level for FunctionInvocationTargetException

    GEODE-3013: Reduce log level for FunctionInvocationTargetExceptions
    
    - Modified to display at debug vs. warning level (includes full stack trace)
    
    @upthewaterspout @nabarunnag, @boglesby, @jhuynh1, @gesterzhou
    
    Thank you for submitting a contribution to Apache Geode.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
    
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically
`develop`)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    - [ ] Does `gradlew build` run cleanly?
    
    - [ ] Have you written or updated unit tests to verify your changes?
    
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
    submit an update to your PR as soon as possible. If you need help, please send an
    email to dev@geode.apache.org.


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

    $ git pull https://github.com/apache/geode feature/GEODE-3013

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

    https://github.com/apache/geode/pull/552.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 #552
    
----
commit d9f219ad048668a99ccdf4ac630326c1e13c6f19
Author: Lynn Hughes-Godfrey <lhughesgodfrey@pivotal.io>
Date:   2017-05-31T01:16:34Z

    GEODE-3013: Reduce logging level for FunctionInvocationTargetException: Multiple target
nodes found for single hop operation
    
    - Modified to display at debug vs. warning level

----


> Reduce logging level for FunctionExceptions : InternalFunctionInvocationTargetException:
Multiple target nodes found for single hop operation
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-3013
>                 URL: https://issues.apache.org/jira/browse/GEODE-3013
>             Project: Geode
>          Issue Type: Bug
>          Components: lucene
>    Affects Versions: 1.2.0
>            Reporter: Shelley Lynn Hughes-Godfrey
>            Assignee: Shelley Lynn Hughes-Godfrey
>
> The following exception should not be logged as a warning with a full stack dump (as
it is not actionable by the user).
> Changing this to debug log level.
> {noformat}
> Multiple target nodes found for single hop operation
> [warning 2017/04/04 14:53:06.031 PDT bridgegemfire1_monaco_15778 <ServerConnection
on port 23318 Thread 8> tid=0x98] Exception on server while executing function : org.apache.geode.cache.lucene.internal.distributed.LuceneQueryFunction
> org.apache.geode.internal.cache.execute.InternalFunctionInvocationTargetException: Multiple
target nodes found for single hop operation
>         at org.apache.geode.internal.cache.PartitionedRegion.executeOnBucketSet(PartitionedRegion.java:3684)
>         at org.apache.geode.internal.cache.PartitionedRegion.executeFunction(PartitionedRegion.java:3344)
>         at org.apache.geode.internal.cache.execute.PartitionedRegionFunctionExecutor.executeFunction(PartitionedRegionFunctionExecutor.java:225)
>         at org.apache.geode.internal.cache.execute.AbstractExecution.execute(AbstractExecution.java:563)
>         at org.apache.geode.internal.cache.tier.sockets.command.ExecuteRegionFunctionSingleHop.cmdExecute(ExecuteRegionFunctionSingleHop.java:264)
>         at org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
>         at org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:783)
>         at org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
>         at org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1171)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         at org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message