[jira] [Commented] (HBASE-6372) Add scanner batching to Export job
[
https://issues.apache.org/jira/browse/HBASE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13429020#comment-13429020
]
Shengsheng Huang commented on HBASE-6372:
-
It seems the current Scan#setBatch function may throw exception. Details as
below:
{quote}
public void setBatch(int batch) {
if (this.hasFilter() this.filter.hasFilterRow()) {
throw new IncompatibleFilterException(
Cannot set batch on a scan using a filter +
that returns true for filter.hasFilterRow);
}
this.batch = batch;
}
{quote}
Don't we need to catch that exception in this patch?
Add scanner batching to Export job
--
Key: HBASE-6372
URL: https://issues.apache.org/jira/browse/HBASE-6372
Project: HBase
Issue Type: Improvement
Components: mapreduce
Affects Versions: 0.96.0, 0.94.2
Reporter: Lars George
Assignee: Shengsheng Huang
Priority: Minor
Labels: newbie
Attachments: HBASE-6372.2.patch, HBASE-6372.3.patch,
HBASE-6372.4.patch, HBASE-6372.patch
When a single row is too large for the RS heap then an OOME can take out the
entire RS. Setting scanner batching in custom scans helps avoiding this
scenario, but for the supplied Export job this is not set.
Similar to HBASE-3421 we can set the batching to a low number - or if needed
make it a command line option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6372) Add scanner batching to Export job
[ https://issues.apache.org/jira/browse/HBASE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shengsheng Huang updated HBASE-6372: Attachment: HBASE-6372.3.patch Modified patch according to @Ted's suggestions Add scanner batching to Export job -- Key: HBASE-6372 URL: https://issues.apache.org/jira/browse/HBASE-6372 Project: HBase Issue Type: Improvement Components: mapreduce Affects Versions: 0.96.0, 0.94.2 Reporter: Lars George Assignee: Shengsheng Huang Priority: Minor Labels: newbie Attachments: HBASE-6372.2.patch, HBASE-6372.3.patch, HBASE-6372.patch When a single row is too large for the RS heap then an OOME can take out the entire RS. Setting scanner batching in custom scans helps avoiding this scenario, but for the supplied Export job this is not set. Similar to HBASE-3421 we can set the batching to a low number - or if needed make it a command line option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6372) Add scanner batching to Export job
[
https://issues.apache.org/jira/browse/HBASE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427791#comment-13427791
]
Shengsheng Huang commented on HBASE-6372:
-
{quote}
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestAtomicOperation
{quote}
This unit test passed at my local deployment. And I don't think the patch has
anything to do with this unit test.
Could somebody kindly help confirm why the unit test fail in Hadoop QA?
Thanks very much.
Add scanner batching to Export job
--
Key: HBASE-6372
URL: https://issues.apache.org/jira/browse/HBASE-6372
Project: HBase
Issue Type: Improvement
Components: mapreduce
Affects Versions: 0.96.0, 0.94.2
Reporter: Lars George
Assignee: Shengsheng Huang
Priority: Minor
Labels: newbie
Attachments: HBASE-6372.2.patch, HBASE-6372.patch
When a single row is too large for the RS heap then an OOME can take out the
entire RS. Setting scanner batching in custom scans helps avoiding this
scenario, but for the supplied Export job this is not set.
Similar to HBASE-3421 we can set the batching to a low number - or if needed
make it a command line option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6456) Export Utility throws ClassNotFoundException
[
https://issues.apache.org/jira/browse/HBASE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427800#comment-13427800
]
Shengsheng Huang commented on HBASE-6456:
-
@Lars Yes. Below command also throws exception.
{noformat} bin/hbase org.apache.hadoop.hbase.mapreduce.Export ...{noformat}
Export Utility throws ClassNotFoundException
Key: HBASE-6456
URL: https://issues.apache.org/jira/browse/HBASE-6456
Project: HBase
Issue Type: Bug
Components: mapred, mapreduce, util
Affects Versions: 0.96.0, 0.94.2
Reporter: Shengsheng Huang
Assignee: Shengsheng Huang
Priority: Minor
Attachments: HBASE-6456.patch
The command I ran is as below:
bin/hbase org.apache.hadoop.hbase.mapreduce.Driver export t1 ./t1
And I got the following exceptions:
attempt_201207261322_0002_m_00_0, Status : FAILED
Error: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.util.Bytes
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.apache.hadoop.hbase.client.HTable.init(HTable.java:150)
at
org.apache.hadoop.hbase.mapreduce.TableInputFormat.setConf(TableInputFormat.java:100)
at
org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:62)
at
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:117)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:767)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:371)
at org.apache.hadoop.mapred.Child$4.run(Child.java:266)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.au
...
This exception can be resolved by adding hbase common jar into
HADOOP_CLASSPATH. But this is an extra step for users and not so convenient.
We could add Bytes.class into dependency Jars of the MapReduce job.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6456) Export Utility throws ClassNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427849#comment-13427849 ] Shengsheng Huang commented on HBASE-6456: - The exception is found when I'm running current hbase trunk. Export Utility throws ClassNotFoundException Key: HBASE-6456 URL: https://issues.apache.org/jira/browse/HBASE-6456 Project: HBase Issue Type: Bug Components: mapred, mapreduce, util Affects Versions: 0.96.0, 0.94.2 Reporter: Shengsheng Huang Assignee: Shengsheng Huang Priority: Minor Attachments: HBASE-6456.patch The command I ran is as below: bin/hbase org.apache.hadoop.hbase.mapreduce.Driver export t1 ./t1 And I got the following exceptions: attempt_201207261322_0002_m_00_0, Status : FAILED Error: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.util.Bytes at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:150) at org.apache.hadoop.hbase.mapreduce.TableInputFormat.setConf(TableInputFormat.java:100) at org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:62) at org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:117) at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:767) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:371) at org.apache.hadoop.mapred.Child$4.run(Child.java:266) at java.security.AccessController.doPrivileged(Native Method) at javax.security.au ... This exception can be resolved by adding hbase common jar into HADOOP_CLASSPATH. But this is an extra step for users and not so convenient. We could add Bytes.class into dependency Jars of the MapReduce job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6372) Add scanner batching to Export job
[ https://issues.apache.org/jira/browse/HBASE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shengsheng Huang updated HBASE-6372: Attachment: HBASE-6372.2.patch Modified patch according to @Jonathan's suggestion. Also removed the formatting issue as @stack indicates. Add scanner batching to Export job -- Key: HBASE-6372 URL: https://issues.apache.org/jira/browse/HBASE-6372 Project: HBase Issue Type: Improvement Components: mapreduce Affects Versions: 0.96.0, 0.94.2 Reporter: Lars George Assignee: Shengsheng Huang Priority: Minor Labels: newbie Attachments: HBASE-6372.2.patch, HBASE-6372.patch When a single row is too large for the RS heap then an OOME can take out the entire RS. Setting scanner batching in custom scans helps avoiding this scenario, but for the supplied Export job this is not set. Similar to HBASE-3421 we can set the batching to a low number - or if needed make it a command line option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6372) Add scanner batching to Export job
[
https://issues.apache.org/jira/browse/HBASE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13423698#comment-13423698
]
Shengsheng Huang commented on HBASE-6372:
-
{quote}
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort
{quote}
I don't think this patch has something to do with this unit test. This unit
test had passed at my local deployment.
Add scanner batching to Export job
--
Key: HBASE-6372
URL: https://issues.apache.org/jira/browse/HBASE-6372
Project: HBase
Issue Type: Improvement
Components: mapreduce
Affects Versions: 0.96.0, 0.94.2
Reporter: Lars George
Priority: Minor
Labels: newbie
Attachments: HBASE-6372.patch
When a single row is too large for the RS heap then an OOME can take out the
entire RS. Setting scanner batching in custom scans helps avoiding this
scenario, but for the supplied Export job this is not set.
Similar to HBASE-3421 we can set the batching to a low number - or if needed
make it a command line option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6456) Export Utility throws ClassNotFoundException
[
https://issues.apache.org/jira/browse/HBASE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13423705#comment-13423705
]
Shengsheng Huang commented on HBASE-6456:
-
{quote}
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestFromClientSide
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort
org.apache.hadoop.hbase.catalog.TestMetaReaderEditor
org.apache.hadoop.hbase.master.TestMasterNoCluster
org.apache.hadoop.hbase.security.access.TestZKPermissionsWatcher
{quote}
I don't think this patch has something to do with these unit test. Also, those
test cases had passed at my local deployment.
Export Utility throws ClassNotFoundException
Key: HBASE-6456
URL: https://issues.apache.org/jira/browse/HBASE-6456
Project: HBase
Issue Type: Bug
Reporter: Shengsheng Huang
Assignee: Shengsheng Huang
Priority: Minor
Attachments: HBASE-6456.patch
The command I ran is as below:
bin/hbase org.apache.hadoop.hbase.mapreduce.Driver export t1 ./t1
And I got the following exceptions:
attempt_201207261322_0002_m_00_0, Status : FAILED
Error: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.util.Bytes
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.apache.hadoop.hbase.client.HTable.init(HTable.java:150)
at
org.apache.hadoop.hbase.mapreduce.TableInputFormat.setConf(TableInputFormat.java:100)
at
org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:62)
at
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:117)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:767)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:371)
at org.apache.hadoop.mapred.Child$4.run(Child.java:266)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.au
...
This exception can be resolved by adding hbase common jar into
HADOOP_CLASSPATH. But this is an extra step for users and not so convenient.
We could add Bytes.class into dependency Jars of the MapReduce job.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HBASE-6372) Add scanner batching to Export job
[ https://issues.apache.org/jira/browse/HBASE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shengsheng Huang reassigned HBASE-6372: --- Assignee: Shengsheng Huang Add scanner batching to Export job -- Key: HBASE-6372 URL: https://issues.apache.org/jira/browse/HBASE-6372 Project: HBase Issue Type: Improvement Components: mapreduce Affects Versions: 0.96.0, 0.94.2 Reporter: Lars George Assignee: Shengsheng Huang Priority: Minor Labels: newbie Attachments: HBASE-6372.patch When a single row is too large for the RS heap then an OOME can take out the entire RS. Setting scanner batching in custom scans helps avoiding this scenario, but for the supplied Export job this is not set. Similar to HBASE-3421 we can set the batching to a low number - or if needed make it a command line option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6456) Export Utility throws ClassNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shengsheng Huang updated HBASE-6456: Attachment: HBASE-6456.patch Attached a patch for it Export Utility throws ClassNotFoundException Key: HBASE-6456 URL: https://issues.apache.org/jira/browse/HBASE-6456 Project: HBase Issue Type: Bug Reporter: Shengsheng Huang Priority: Minor Attachments: HBASE-6456.patch The command I ran is as below: bin/hbase org.apache.hadoop.hbase.mapreduce.Driver export t1 ./t1 And I got the following exceptions: attempt_201207261322_0002_m_00_0, Status : FAILED Error: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.util.Bytes at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:150) at org.apache.hadoop.hbase.mapreduce.TableInputFormat.setConf(TableInputFormat.java:100) at org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:62) at org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:117) at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:767) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:371) at org.apache.hadoop.mapred.Child$4.run(Child.java:266) at java.security.AccessController.doPrivileged(Native Method) at javax.security.au ... This exception can be resolved by adding hbase common jar into HADOOP_CLASSPATH. But this is an extra step for users and not so convenient. We could add Bytes.class into dependency Jars of the MapReduce job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-6456) Export Utility throws ClassNotFoundException
Shengsheng Huang created HBASE-6456: --- Summary: Export Utility throws ClassNotFoundException Key: HBASE-6456 URL: https://issues.apache.org/jira/browse/HBASE-6456 Project: HBase Issue Type: Bug Reporter: Shengsheng Huang Priority: Minor The command I ran is as below: bin/hbase org.apache.hadoop.hbase.mapreduce.Driver export t1 ./t1 And I got the following exceptions: attempt_201207261322_0002_m_00_0, Status : FAILED Error: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.util.Bytes at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:150) at org.apache.hadoop.hbase.mapreduce.TableInputFormat.setConf(TableInputFormat.java:100) at org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:62) at org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:117) at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:767) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:371) at org.apache.hadoop.mapred.Child$4.run(Child.java:266) at java.security.AccessController.doPrivileged(Native Method) at javax.security.au ... This exception can be resolved by adding hbase common jar into HADOOP_CLASSPATH. But this is an extra step for users and not so convenient. We could add Bytes.class into dependency Jars of the MapReduce job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6372) Add scanner batching to Export job
[ https://issues.apache.org/jira/browse/HBASE-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shengsheng Huang updated HBASE-6372: Attachment: HBASE-6372.patch I think this is useful. Attached a patch for it. Add scanner batching to Export job -- Key: HBASE-6372 URL: https://issues.apache.org/jira/browse/HBASE-6372 Project: HBase Issue Type: Improvement Components: mapreduce Reporter: Lars George Priority: Minor Labels: newbie Attachments: HBASE-6372.patch When a single row is too large for the RS heap then an OOME can take out the entire RS. Setting scanner batching in custom scans helps avoiding this scenario, but for the supplied Export job this is not set. Similar to HBASE-3421 we can set the batching to a low number - or if needed make it a command line option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6363) HBaseConfiguration can carry a main method that dumps XML output for debug purposes
[ https://issues.apache.org/jira/browse/HBASE-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shengsheng Huang updated HBASE-6363: Attachment: HBASE-6363.patch We happened to have the same requirement for debugging purposes. Attach a patch here. HBaseConfiguration can carry a main method that dumps XML output for debug purposes --- Key: HBASE-6363 URL: https://issues.apache.org/jira/browse/HBASE-6363 Project: HBase Issue Type: Improvement Components: util Affects Versions: 0.94.0 Reporter: Harsh J Priority: Trivial Labels: conf, newbie, noob Attachments: HBASE-6363.patch Just like the Configuration class carries a main() method in it, that simply loads itself and writes XML out to System.out, HBaseConfiguration can use the same kinda method. That way we can do hbase org.apache.hadoop.….HBaseConfiguration to get an Xml dump of things HBaseConfiguration has properly loaded. Nifty in checking app classpaths sometimes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6363) HBaseConfiguration can carry a main method that dumps XML output for debug purposes
[ https://issues.apache.org/jira/browse/HBASE-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shengsheng Huang updated HBASE-6363: Attachment: HBASE-6363.2.patch Updated the patch according to @Harsh's comments. Actually we did the patch for automation purposes. Http master/dump contains much more information than we needed. HBaseConfiguration can carry a main method that dumps XML output for debug purposes --- Key: HBASE-6363 URL: https://issues.apache.org/jira/browse/HBASE-6363 Project: HBase Issue Type: Improvement Components: util Affects Versions: 0.94.0 Reporter: Harsh J Priority: Trivial Labels: conf, newbie, noob Attachments: HBASE-6363.2.patch, HBASE-6363.patch Just like the Configuration class carries a main() method in it, that simply loads itself and writes XML out to System.out, HBaseConfiguration can use the same kinda method. That way we can do hbase org.apache.hadoop.….HBaseConfiguration to get an Xml dump of things HBaseConfiguration has properly loaded. Nifty in checking app classpaths sometimes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6363) HBaseConfiguration can carry a main method that dumps XML output for debug purposes
[ https://issues.apache.org/jira/browse/HBASE-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418900#comment-13418900 ] Shengsheng Huang commented on HBASE-6363: - Thanks very much for clarification Harsh. It seems /conf is only added into Hadoop since release 0.21 (HADOOP-6408). As we're using hadoop v1 it didn't work at our local cluster. We would consider adding HADOOP-6408 patch into our local hadoop branch. After all, servlet config dump would contain all the configuration changes in code. Anyway, do you think it worth a seperate servlet to dump configuration as xml only? Or reorganize the dump output into more consistent format to make it easier for automatic parsing? HBaseConfiguration can carry a main method that dumps XML output for debug purposes --- Key: HBASE-6363 URL: https://issues.apache.org/jira/browse/HBASE-6363 Project: HBase Issue Type: Improvement Components: util Affects Versions: 0.94.0 Reporter: Harsh J Priority: Trivial Labels: conf, newbie, noob Attachments: HBASE-6363.2.patch, HBASE-6363.patch Just like the Configuration class carries a main() method in it, that simply loads itself and writes XML out to System.out, HBaseConfiguration can use the same kinda method. That way we can do hbase org.apache.hadoop.….HBaseConfiguration to get an Xml dump of things HBaseConfiguration has properly loaded. Nifty in checking app classpaths sometimes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6363) HBaseConfiguration can carry a main method that dumps XML output for debug purposes
[ https://issues.apache.org/jira/browse/HBASE-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418940#comment-13418940 ] Shengsheng Huang commented on HBASE-6363: - Seems reasonable. I only got a little bit concern about package dependency, because some of our customers are very reluctant to upgrade their stable hadoop deployment. A standalone patch is good to have. HBaseConfiguration can carry a main method that dumps XML output for debug purposes --- Key: HBASE-6363 URL: https://issues.apache.org/jira/browse/HBASE-6363 Project: HBase Issue Type: Improvement Components: util Affects Versions: 0.94.0 Reporter: Harsh J Priority: Trivial Labels: conf, newbie, noob Attachments: HBASE-6363.2.patch, HBASE-6363.patch Just like the Configuration class carries a main() method in it, that simply loads itself and writes XML out to System.out, HBaseConfiguration can use the same kinda method. That way we can do hbase org.apache.hadoop.….HBaseConfiguration to get an Xml dump of things HBaseConfiguration has properly loaded. Nifty in checking app classpaths sometimes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
