geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GEODE-2864) In same cases committing a geode transaction logs a meaningless warning
Date Wed, 03 May 2017 22:31:04 GMT

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

Darrel Schneider resolved GEODE-2864.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0

> In same cases committing a geode transaction logs a meaningless warning
> -----------------------------------------------------------------------
>
>                 Key: GEODE-2864
>                 URL: https://issues.apache.org/jira/browse/GEODE-2864
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>    Affects Versions: 1.0.0-incubating
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Trivial
>             Fix For: 1.2.0
>
>
> Sometimes a transaction commit will log a warning message that looks like this:
> {code}
> [warning 2017/04/27 17:11:15.034 CST GemfireAPIServer2 <ServerConnection on port 40405
Thread 0> tid=0x59] New members for Region: com.gemstone.gemfire.internal.cache.DistributedRegion[path='/exampleRegionRep1';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
concurrencyChecksEnabled] orig list: [pivhdsne(GemfireAPIServer1:79899)<v1>:1265] new
list: [pivhdsne(GemfireAPIServer4:80172)<v4>:56801, pivhdsne(GemfireAPIServer1:79899)<v1>:1265,
pivhdsne(GemfireAPIServer3:80078)<v3>:14603]
> {code}
> This warning can be safely ignored.



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

Mime
View raw message