Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.incubator.apache.org
Date: Thu, 16 Jun 2016 17:24:05 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@geode.incubator.apache.org
Message-ID: <JIRA.12978338.1465844596000.9038.1466097845865@Atlassian.JIRA>
In-Reply-To: <JIRA.12978338.1465844596000@Atlassian.JIRA>
References: <JIRA.12978338.1465844596000@Atlassian.JIRA> <JIRA.12978338.1465844596729@arcas>
Subject: [jira] [Commented] (GEODE-1543) Not using the the correct log level
 when exceptions are thrown while creating indexes.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 16 Jun 2016 17:24:11 -0000


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

ASF subversion and git services commented on GEODE-1543:
--------------------------------------------------------

Commit 612a9d99566ac71421e5cd986c6ce6e391dedd30 in incubator-geode's branch refs/heads/feature/GEODE-835 from [~nnag]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=612a9d9 ]

GEODE-1543: Change the log level from error to info

    * When multiple peers join the cluster conncurrently, only the first one that joins will distribute the index creation and other will try to create the index locally because of the distributed message and then log an error afterwards.
    * This is an expected behaviour and hence should not be logged as error but rather as a info.

    This closes #156


> Not using the the correct log level when exceptions are thrown while creating indexes.
> --------------------------------------------------------------------------------------
>
>                 Key: GEODE-1543
>                 URL: https://issues.apache.org/jira/browse/GEODE-1543
>             Project: Geode
>          Issue Type: Bug
>            Reporter: nabarun
>
> When two or more peers join the cluster concurrently, only the first one that joins will distribute the index creation while reading its cache.xml file, the rest will create the index locally due to the distributed message and log an error afterwards, while trying to create the index from its own cache.xml file. This error message is currently being registered under "ERROR" log level, and it should be registered under "WARNING", or even not be registered at all since this "exception" is expected during startup (we could easily cache the indexes created locally by other distributed members)
> {noformat}
> [fine 2016/05/12 09:37:01.744 BST host1-server2 <PartitionedRegion Message Processor1> tid=0x44] Index creation message got the pr Partitioned Region @57fd91c9 [path='/ClientSessionRegionPosSrv'; dataPolicy=PARTITION; gatewayEnabled=false; prId=1; isDestroyed=false; isClosed=false; retryTimeout=3600000; serialNumber=7; partition attributes=PartitionAttributes@1828508781[redundantCopies=1;localMaxMemory=5;totalMaxMemory=2147483647;totalNumBuckets=47;partitionResolver=null;colocatedWith=null;recoveryDelay=300000;startupRecoveryDelay=60000;FixedPartitionAttributes=null;partitionListeners=null]; on VM 10.69.252.112(host1-server2:21655)<v2>:34609]
> [fine 2016/05/12 09:37:01.744 BST host1-server2 <main> tid=0x1] LocalRegion.createOQLIndexes on region /ClientSessionRegionPosSrv
> [fine 2016/05/12 09:37:01.744 BST host1-server2 <PartitionedRegion Message Processor1> tid=0x44] Processing index creation message on this remote partitioned region vm for indexes: ClientSessionRegionPosSrv.byUser 
> [fine 2016/05/12 09:37:01.744 BST host1-server2 <PartitionedRegion Message Processor1> tid=0x44] Started creating index with Index Name :ClientSessionRegionPosSrv.byUser On PartitionedRegion /ClientSessionRegionPosSrv, Indexfrom caluse=/ClientSessionRegionPosSrv, Remote Request: true
> [fine 2016/05/12 09:37:01.744 BST host1-server2 <main> tid=0x1] QueryService Index creation process for {}ClientSessionRegionPosSrv.byUser
> [fine 2016/05/12 09:37:01.750 BST host1-server2 <PartitionedRegion Message Processor1> tid=0x44] Completed creating index with Index Name :ClientSessionRegionPosSrv.byUser On PartitionedRegion /ClientSessionRegionPosSrv, Remote Request: true
> [fine 2016/05/12 09:37:01.751 BST host1-server2 <PartitionedRegion Message Processor1> tid=0x44] Multi Index creation completed on remote host and has sent the reply to the originating vm.
> [fine 2016/05/12 09:37:01.769 BST host1-server2 <main> tid=0x1] Started creating index with Index Name :ClientSessionRegionPosSrv.byUser On PartitionedRegion /ClientSessionRegionPosSrv, Indexfrom caluse=/ClientSessionRegionPosSrv, Remote Request: false
> [error 2016/05/12 09:37:01.770 BST host1-server2 <main> tid=0x1] Failed to create index ClientSessionRegionPosSrv.byUser on region /ClientSessionRegionPosSrv with exception: com.gemstone.gemfire.cache.query.IndexNameConflictException: Index named ' ClientSessionRegionPosSrv.byUser ' already exists.
> {noformat}


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