Bug 1146786 - Rebalancing "Finished cluster wide rebalance" message is not logged in INFO
Summary: Rebalancing "Finished cluster wide rebalance" message is not logged in INFO
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.3.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER5
: 6.4.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1168233
TreeView+ depends on / blocked
 
Reported: 2014-09-26 04:56 UTC by ksuzumur
Modified: 2019-02-15 13:46 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
: 1168233 (view as bug list)
Environment:
Last Closed: 2015-01-28 13:27:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-4957 0 Major Resolved Rebalancing "Finished cluster wide rebalance" message is not logged in INFO 2016-10-27 09:16:09 UTC
Red Hat Issue Tracker PRODMGT-930 0 Major Resolved Rebalancing log level 2016-10-27 09:16:09 UTC

Description ksuzumur 2014-09-26 04:56:02 UTC
Description of problem:
Rebalancing "Finished cluster wide rebalance" message is not logged in INFO. I can get the log (started/enabled/suspended) messages, but can't get the finished message.

Version-Release number of selected component (if applicable):
JDG 6.3.1

Actual results:
The "finished cluster wide rebalance" message is not logged in INFO.

Expected results:
The "finished cluster wide rebalance" message is logged in INFO.

Additional info:
Bug 1131117 - Log rebalancing messages to specific category
https://bugzilla.redhat.com/show_bug.cgi?id=1131117

Comment 3 Adrian Nistor 2014-11-11 19:54:24 UTC
Integrated PR for jdg-6.4.x: https://github.com/infinispan/jdg/pull/343

Comment 4 Adrian Nistor 2014-11-12 09:21:05 UTC
Integrated PR for jdg-6.3.x also: https://github.com/infinispan/jdg/pull/342

Comment 5 Martin Gencur 2014-11-12 11:46:04 UTC
Verified with ER5.


Note You need to log in before you can comment on or make changes to this bug.