[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-29859:
--
Fix Version/s: 2.6.5
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Cherry-picked to branch-2.6.
Thanks [~liuxiaocs] and [~paksyd]!
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 3.0.0-beta-1, 2.6.4, 2.5.13
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.5
>
>
> In the \{{DataTieringManager.instantiate}} method, if \{{DataTieringFeature}}
> is not enabled, we still see the log message \{{DataTieringManager is already
> instantiated.}} when the regionserver starts, which is quite confusing. The
> code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dávid Paksy updated HBASE-29859:
Fix Version/s: (was: 2.6.5)
(was: 2.5.14)
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 3.0.0-beta-1, 2.6.4, 2.5.13
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2
>
>
> In the \{{DataTieringManager.instantiate}} method, if \{{DataTieringFeature}}
> is not enabled, we still see the log message \{{DataTieringManager is already
> instantiated.}} when the regionserver starts, which is quite confusing. The
> code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Liu updated HBASE-29859:
-
Fix Version/s: 2.7.0
2.6.5
2.5.14
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 3.0.0-beta-1
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.5, 2.5.14
>
>
> In the \{{DataTieringManager.instantiate}} method, if \{{DataTieringFeature}}
> is not enabled, we still see the log message \{{DataTieringManager is already
> instantiated.}} when the regionserver starts, which is quite confusing. The
> code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Liu updated HBASE-29859:
-
Status: Patch Available (was: Open)
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 2.5.13, 2.6.4, 3.0.0-beta-1
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.5, 2.5.14
>
>
> In the \{{DataTieringManager.instantiate}} method, if \{{DataTieringFeature}}
> is not enabled, we still see the log message \{{DataTieringManager is already
> instantiated.}} when the regionserver starts, which is quite confusing. The
> code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Liu updated HBASE-29859:
-
Affects Version/s: 2.5.13
2.6.4
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 3.0.0-beta-1, 2.6.4, 2.5.13
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.5, 2.5.14
>
>
> In the \{{DataTieringManager.instantiate}} method, if \{{DataTieringFeature}}
> is not enabled, we still see the log message \{{DataTieringManager is already
> instantiated.}} when the regionserver starts, which is quite confusing. The
> code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Liu updated HBASE-29859:
-
Description:
In the \{{DataTieringManager.instantiate}} method, if \{{DataTieringFeature}}
is not enabled, we still see the log message \{{DataTieringManager is already
instantiated.}} when the regionserver starts, which is quite confusing. The
code is as follows:
{code:java}
public static synchronized boolean instantiate(Configuration conf,
Map onlineRegions) {
if (isDataTieringFeatureEnabled(conf) && instance == null) {
instance = new DataTieringManager(onlineRegions);
LOG.info("DataTieringManager instantiated successfully.");
return true;
} else {
LOG.warn("DataTieringManager is already instantiated.");
}
return false;
} {code}
was:
In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}} is
not enabled, we still see the log message \{{DataTieringManager is already
instantiated. }} when rs starts, which is quite confusing. The code is as
follows:
{code:java}
public static synchronized boolean instantiate(Configuration conf,
Map onlineRegions) {
if (isDataTieringFeatureEnabled(conf) && instance == null) {
instance = new DataTieringManager(onlineRegions);
LOG.info("DataTieringManager instantiated successfully.");
return true;
} else {
LOG.warn("DataTieringManager is already instantiated.");
}
return false;
} {code}
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 3.0.0-beta-1
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> In the \{{DataTieringManager.instantiate}} method, if \{{DataTieringFeature}}
> is not enabled, we still see the log message \{{DataTieringManager is already
> instantiated.}} when the regionserver starts, which is quite confusing. The
> code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Liu updated HBASE-29859:
-
Description:
In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}} is
not enabled, we still see the log message \{{DataTieringManager is already
instantiated. }} when rs starts, which is quite confusing. The code is as
follows:
{code:java}
public static synchronized boolean instantiate(Configuration conf,
Map onlineRegions) {
if (isDataTieringFeatureEnabled(conf) && instance == null) {
instance = new DataTieringManager(onlineRegions);
LOG.info("DataTieringManager instantiated successfully.");
return true;
} else {
LOG.warn("DataTieringManager is already instantiated.");
}
return false;
} {code}
was:
In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}} is
not enabled, we still see the log message {{DataTieringManager is already
instantiated. }}when rs starts, which is quite confusing. The code is as
follows:
{code:java}
public static synchronized boolean instantiate(Configuration conf,
Map onlineRegions) {
if (isDataTieringFeatureEnabled(conf) && instance == null) {
instance = new DataTieringManager(onlineRegions);
LOG.info("DataTieringManager instantiated successfully.");
return true;
} else {
LOG.warn("DataTieringManager is already instantiated.");
}
return false;
} {code}
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 3.0.0-beta-1
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}}
> is not enabled, we still see the log message \{{DataTieringManager is already
> instantiated. }} when rs starts, which is quite confusing. The code is as
> follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Liu updated HBASE-29859:
-
Description:
In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}} is
not enabled, we still see the log message {{DataTieringManager is already
instantiated. }}when rs starts, which is quite confusing. The code is as
follows:
{code:java}
public static synchronized boolean instantiate(Configuration conf,
Map onlineRegions) {
if (isDataTieringFeatureEnabled(conf) && instance == null) {
instance = new DataTieringManager(onlineRegions);
LOG.info("DataTieringManager instantiated successfully.");
return true;
} else {
LOG.warn("DataTieringManager is already instantiated.");
}
return false;
} {code}
was:
In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}} is
not enabled, we still see the log message {{{}DataTieringManager is already
instantiated.{}}}, which is quite confusing. The code is as follows:
{code:java}
public static synchronized boolean instantiate(Configuration conf,
Map onlineRegions) {
if (isDataTieringFeatureEnabled(conf) && instance == null) {
instance = new DataTieringManager(onlineRegions);
LOG.info("DataTieringManager instantiated successfully.");
return true;
} else {
LOG.warn("DataTieringManager is already instantiated.");
}
return false;
} {code}
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 3.0.0-beta-1
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}}
> is not enabled, we still see the log message {{DataTieringManager is already
> instantiated. }}when rs starts, which is quite confusing. The code is as
> follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Liu updated HBASE-29859:
-
Issue Type: Bug (was: Improvement)
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 3.0.0-beta-1
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}}
> is not enabled, we still see the log message {{{}DataTieringManager is
> already instantiated.{}}}, which is quite confusing. The code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HBASE-29859:
---
Labels: pull-request-available (was: )
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
>Affects Versions: 3.0.0-beta-1
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}}
> is not enabled, we still see the log message {{{}DataTieringManager is
> already instantiated.{}}}, which is quite confusing. The code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-29859) Initialization log for DataTieringManager is incorrect
[
https://issues.apache.org/jira/browse/HBASE-29859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Liu updated HBASE-29859:
-
Description:
In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}} is
not enabled, we still see the log message {{{}DataTieringManager is already
instantiated.{}}}, which is quite confusing. The code is as follows:
{code:java}
public static synchronized boolean instantiate(Configuration conf,
Map onlineRegions) {
if (isDataTieringFeatureEnabled(conf) && instance == null) {
instance = new DataTieringManager(onlineRegions);
LOG.info("DataTieringManager instantiated successfully.");
return true;
} else {
LOG.warn("DataTieringManager is already instantiated.");
}
return false;
} {code}
was:
In the \{{DataTieringManager.instantiate}} method, if \{{DataTieringFeature}}
is not enabled, we still see the log message \{{DataTieringManager is already
instantiated.}}, which is quite confusing. The code is as follows:
{code:language=java|borderStyle=solid|theme=RDark|linenumbers=true|collapse=false}
public static synchronized boolean instantiate(Configuration conf,
Map onlineRegions) {
if (isDataTieringFeatureEnabled(conf) && instance == null) {
instance = new DataTieringManager(onlineRegions);
LOG.info("DataTieringManager instantiated successfully.");
return true;
} else {
LOG.warn("DataTieringManager is already instantiated.");
}
return false;
}
{code}
> Initialization log for DataTieringManager is incorrect
> --
>
> Key: HBASE-29859
> URL: https://issues.apache.org/jira/browse/HBASE-29859
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
>Affects Versions: 3.0.0-beta-1
>Reporter: Xiao Liu
>Assignee: Xiao Liu
>Priority: Minor
> Fix For: 3.0.0-beta-2
>
>
> In the {{DataTieringManager.instantiate}} method, if {{DataTieringFeature}}
> is not enabled, we still see the log message {{{}DataTieringManager is
> already instantiated.{}}}, which is quite confusing. The code is as follows:
> {code:java}
> public static synchronized boolean instantiate(Configuration conf,
> Map onlineRegions) {
> if (isDataTieringFeatureEnabled(conf) && instance == null) {
> instance = new DataTieringManager(onlineRegions);
> LOG.info("DataTieringManager instantiated successfully.");
> return true;
> } else {
> LOG.warn("DataTieringManager is already instantiated.");
> }
> return false;
> } {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
