[jira] [Commented] (HBASE-7027) Use the correct port of info server of region servers

2012-10-23 Thread Hudson (JIRA)

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

Hudson commented on HBASE-7027:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #232 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/232/])
HBASE-7027 Use the correct port of info server of region servers (Revision 
1401454)

 Result = FAILURE
eclark : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/master/RegionServerListTmpl.jamon
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ServerLoad.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/generated/HBaseProtos.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* /hbase/trunk/hbase-server/src/main/protobuf/hbase.proto


> Use the correct port of info server of region servers
> -
>
> Key: HBASE-7027
> URL: https://issues.apache.org/jira/browse/HBASE-7027
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Fix For: 0.96.0
>
> Attachments: HBASE-7027-0.patch, HBASE-7027-1.patch
>
>
> Right now the master ui just guesses that the port of the info server will 
> always be the same on all servers.  This is not a good assumption setting it 
> for each server is possible, also setting the conf variable to 0 will make 
> the info server choose a port randomly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HBASE-7027) Use the correct port of info server of region servers

2012-10-23 Thread Hudson (JIRA)

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

Hudson commented on HBASE-7027:
---

Integrated in HBase-TRUNK #3477 (See 
[https://builds.apache.org/job/HBase-TRUNK/3477/])
HBASE-7027 Use the correct port of info server of region servers (Revision 
1401454)

 Result = FAILURE
eclark : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/master/RegionServerListTmpl.jamon
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ServerLoad.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/generated/HBaseProtos.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* /hbase/trunk/hbase-server/src/main/protobuf/hbase.proto


> Use the correct port of info server of region servers
> -
>
> Key: HBASE-7027
> URL: https://issues.apache.org/jira/browse/HBASE-7027
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Fix For: 0.96.0
>
> Attachments: HBASE-7027-0.patch, HBASE-7027-1.patch
>
>
> Right now the master ui just guesses that the port of the info server will 
> always be the same on all servers.  This is not a good assumption setting it 
> for each server is possible, also setting the conf variable to 0 will make 
> the info server choose a port randomly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HBASE-7027) Use the correct port of info server of region servers

2012-10-23 Thread Elliott Clark (JIRA)

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

Elliott Clark commented on HBASE-7027:
--

Committed revision 1401454.

Thanks for the review.  I agree with you Stack; lets start thinking of how we 
change the heart beat.

> Use the correct port of info server of region servers
> -
>
> Key: HBASE-7027
> URL: https://issues.apache.org/jira/browse/HBASE-7027
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Fix For: 0.96.0
>
> Attachments: HBASE-7027-0.patch, HBASE-7027-1.patch
>
>
> Right now the master ui just guesses that the port of the info server will 
> always be the same on all servers.  This is not a good assumption setting it 
> for each server is possible, also setting the conf variable to 0 will make 
> the info server choose a port randomly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HBASE-7027) Use the correct port of info server of region servers

2012-10-23 Thread stack (JIRA)

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

stack commented on HBASE-7027:
--

+1 on commit

I hate this patch.  It further pollutes ServerLoad with attributes (It is not 
the first offender).  But it fixes this issue until we convert it so master 
learns of serverload via metrics (or chatting here w/ Elliott and Gregory, 
master reads serverload from a metrics table... blue sky) and it learns of 
attributes elsewhere (in the zk ephemeral node -- might be put up too late -- 
might have to rearrange stuff).  TODO.

> Use the correct port of info server of region servers
> -
>
> Key: HBASE-7027
> URL: https://issues.apache.org/jira/browse/HBASE-7027
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-7027-0.patch, HBASE-7027-1.patch
>
>
> Right now the master ui just guesses that the port of the info server will 
> always be the same on all servers.  This is not a good assumption setting it 
> for each server is possible, also setting the conf variable to 0 will make 
> the info server choose a port randomly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HBASE-7027) Use the correct port of info server of region servers

2012-10-23 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-7027:
--

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12550514/HBASE-7027-1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoop 
2.0 profile.

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 
82 warning messages.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 findbugs{color}.  The patch appears to introduce 2 new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

 {color:red}-1 core tests{color}.  The patch failed these unit tests:
   
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3128//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3128//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3128//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3128//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3128//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3128//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3128//console

This message is automatically generated.

> Use the correct port of info server of region servers
> -
>
> Key: HBASE-7027
> URL: https://issues.apache.org/jira/browse/HBASE-7027
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-7027-0.patch, HBASE-7027-1.patch
>
>
> Right now the master ui just guesses that the port of the info server will 
> always be the same on all servers.  This is not a good assumption setting it 
> for each server is possible, also setting the conf variable to 0 will make 
> the info server choose a port randomly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HBASE-7027) Use the correct port of info server of region servers

2012-10-22 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-7027:
--

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12550348/HBASE-7027-0.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoop 
2.0 profile.

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 
82 warning messages.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 findbugs{color}.  The patch appears to introduce 4 new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

 {color:red}-1 core tests{color}.  The patch failed these unit tests:
   org.apache.hadoop.hbase.master.TestOpenedRegionHandler
  org.apache.hadoop.hbase.filter.TestColumnRangeFilter
  org.apache.hadoop.hbase.client.TestMultipleTimestamps
  org.apache.hadoop.hbase.mapred.TestTableInputFormat
  org.apache.hadoop.hbase.coprocessor.TestMasterObserver
  org.apache.hadoop.hbase.rest.TestStatusResource
  org.apache.hadoop.hbase.constraint.TestConstraint
  
org.apache.hadoop.hbase.util.hbck.TestOfflineMetaRebuildOverlap
  org.apache.hadoop.hbase.rest.TestMultiRowResource
  
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesSplitRecovery
  org.apache.hadoop.hbase.mapreduce.TestTableMapReduce
  
org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface
  org.apache.hadoop.hbase.util.TestMergeTable
  
org.apache.hadoop.hbase.master.TestMasterRestartAfterDisablingTable
  org.apache.hadoop.hbase.client.TestScannerTimeout
  org.apache.hadoop.hbase.master.TestMasterFileSystem
  
org.apache.hadoop.hbase.io.encoding.TestLoadAndSwitchEncodeOnDisk
  org.apache.hadoop.hbase.util.TestMiniClusterLoadSequential
  org.apache.hadoop.hbase.client.TestMultiParallel
  org.apache.hadoop.hbase.security.access.TestAccessController
  
org.apache.hadoop.hbase.coprocessor.TestMasterCoprocessorExceptionWithRemove
  org.apache.hadoop.hbase.io.encoding.TestChangingEncoding
  org.apache.hadoop.hbase.rest.TestScannerResource
  org.apache.hadoop.hbase.master.TestMasterMetrics
  
org.apache.hadoop.hbase.regionserver.TestStoreFileBlockCacheSummary
  org.apache.hadoop.hbase.replication.TestReplication
  org.apache.hadoop.hbase.regionserver.TestMXBean
  org.apache.hadoop.hbase.util.TestHBaseFsck
  org.apache.hadoop.hbase.TestRegionRebalancing
  org.apache.hadoop.hbase.TestFullLogReconstruction
  org.apache.hadoop.hbase.regionserver.wal.TestLogRollAbort
  org.apache.hadoop.hbase.master.TestMasterTransitions
  org.apache.hadoop.hbase.regionserver.TestClusterId
  
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort
  org.apache.hadoop.hbase.rest.TestGzipFilter
  org.apache.hadoop.hbase.fs.TestBlockReorder
  org.apache.hadoop.hbase.backup.TestHFileArchiving
  org.apache.hadoop.hbase.master.TestAssignmentManagerOnCluster
  org.apache.hadoop.hbase.TestMultiVersions
  org.apache.hadoop.hbase.trace.TestHTraceHooks
  
org.apache.hadoop.hbase.master.handler.TestTableDeleteFamilyHandler
  
org.apache.hadoop.hbase.security.access.TestZKPermissionsWatcher
  
org.apache.hadoop.hbase.io.encoding.TestUpgradeFromHFileV1ToEncoding
  
org.apache.hadoop.hbase.catalog.TestMetaMigrationConvertingToPB
  
org.apache.hadoop.hbase.regionserver.TestRSKilledWhenMasterInitializing
  
org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor
  org.apache.hadoop.hbase.regionserver.TestHRegionOnCluster
  org.apache.hadoop.hbase.regionser