[jira] [Resolved] (HBASE-5691) Importtsv stops the webservice from which it is evoked

2012-03-31 Thread Todd Lipcon (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HBASE-5691.


Resolution: Not A Problem

> Importtsv stops the webservice from which it is evoked
> --
>
> Key: HBASE-5691
> URL: https://issues.apache.org/jira/browse/HBASE-5691
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.90.4
>Reporter: debarshi basak
>Priority: Minor
>
> I was trying to run importtsv from a servlet. Everytime after the completion 
> of job, the tomcat server was shutdown.

--
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] [Resolved] (HBASE-5498) S

2012-02-29 Thread Todd Lipcon (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HBASE-5498.


Resolution: Invalid

> S
> -
>
> Key: HBASE-5498
> URL: https://issues.apache.org/jira/browse/HBASE-5498
> Project: HBase
>  Issue Type: Improvement
>Reporter: Francis Liu
>


--
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] [Resolved] (HBASE-5236) Unable to start master on fresh setup hadoop 1.0 and hbase 0.90.5 on Debian 6

2012-01-20 Thread Todd Lipcon (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HBASE-5236.


Resolution: Invalid

Please use the mailing lists for support - this is the bug tracker. Thanks.

> Unable to start master on fresh setup hadoop 1.0 and hbase 0.90.5 on Debian 6
> -
>
> Key: HBASE-5236
> URL: https://issues.apache.org/jira/browse/HBASE-5236
> Project: HBase
>  Issue Type: Bug
>Reporter: Dan
>Priority: Minor
>
> I can't start HMaster :( 
> Please help me.. second day about this error
> Exception in thread "main" java.lang.RuntimeException: Failed construction of 
> Regionserver: class org.apache.hadoop.hbase.regionserver.HRegionServer
> Unable to start master
> Has already worked well hadoop cluster installation. Wait 30 sec before start 
> hbase.
> I followed this tutorial 
> http://hbase.apache.org/book/example_config.html#d0e2432
> Change system configuration in required section ulimit and nproc
> Have: 1 master, 4 slaves
> Here all diagnostic information
> Java java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
> Debian 6.03 Linux slave1 2.6.32-5-amd64
> Copy hadoop-core to hbase/lib on each machine
> hduser@slave1:/usr/local/hbase$ ls lib/hadoo*
> lib/hadoop-core-1.0.0.jar
> Hbase: hbase-0.90.5
> LOG
> http://pastie.org/private/s9hjy3hsfebzfltvxee6qa
> LOG FROM SLAVE1
> http://pastie.org/private/ebzulfseaotfcehz0cqua
> LOG FROM ZOOKEPER ON SLAVE1
> http://pastie.org/private/y7j11uuhzpebrottsx3ug
> HBASE 
> hbase-site.xml
> http://pastie.org/private/6giqrpeeysidqnjsyimg
> hbase-env.xml
> http://pastie.org/private/9q0abbvmtsgi4kava8zm9w
> regionservers
> http://pastie.org/private/eic5waqafmsm73j9h0nra
> HADOOP
> hadoop-env.sh
> http://pastie.org/private/6lmz3xhmcovwag7vmpecjg
> core-site.xml
> http://pastie.org/private/udskadmow3khd3jqavawww
> hdfs-site.xml
> http://pastie.org/private/b7g1tkpzukkivhjiwgmsfw
> masters and slaves
> http://pastie.org/private/l8o0luukig6jnnba6mpryg

--
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] [Resolved] (HBASE-3949) Add "Master" link to RegionServer pages

2012-01-08 Thread Todd Lipcon (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HBASE-3949.


   Resolution: Fixed
Fix Version/s: 0.94.0

Committed to trunk. The patch didn't apply to the 92 branch as is - if we want 
this in 92, we'll have to prepare a separate patch.

> Add "Master" link to RegionServer pages
> ---
>
> Key: HBASE-3949
> URL: https://issues.apache.org/jira/browse/HBASE-3949
> Project: HBase
>  Issue Type: Improvement
>  Components: regionserver
>Affects Versions: 0.90.3, 0.92.0
>Reporter: Lars George
>Assignee: Gregory Chanan
>Priority: Minor
>  Labels: noob
> Fix For: 0.94.0
>
>
> Use the ZK info where the master is to add a UI link on the top of each 
> RegionServer page. Currently you cannot navigate directly to the Master UI 
> once you are on a RS page.
> Not sure if the info port is exposed OTTOMH, but we could either use the RS 
> local config setting for that or add it to ZK to enable lookup.

--
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] [Resolved] (HBASE-3952) Guava snuck back in as a dependency via hbase-3777

2011-11-22 Thread Todd Lipcon (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HBASE-3952.


  Resolution: Fixed
Hadoop Flags: Reviewed

Committed to 0.90 branch.

> Guava snuck back in as a dependency via hbase-3777
> --
>
> Key: HBASE-3952
> URL: https://issues.apache.org/jira/browse/HBASE-3952
> Project: HBase
>  Issue Type: Task
>Reporter: stack
> Fix For: 0.92.0, 0.90.5
>
> Attachments: hcm.txt
>
>
> Undo it as we did in HBASE-3264.

--
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] [Resolved] (HBASE-3217) Fix the .META. fixer in HBaseFsck

2011-10-20 Thread Todd Lipcon (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HBASE-3217.


Resolution: Cannot Reproduce

going to resolve this one, since hbck has been substantially improved since it 
was filed. I'll assume it's fixed in trunk, or if not, it's a rare enough issue 
that we'll file it again when we see it.

> Fix the .META. fixer in HBaseFsck
> -
>
> Key: HBASE-3217
> URL: https://issues.apache.org/jira/browse/HBASE-3217
> Project: HBase
>  Issue Type: Bug
>Reporter: Jean-Daniel Cryans
>Assignee: Todd Lipcon
>
> I tried writing a few unit tests in the scope of HBASE-3216 since the 
> previous one was only testing a best case scenario but it's at least 
> currently not able to fix the case where .META. says the assignment is on 
> server A when in fact it's on server B (the region gets closed but never 
> reopened).
> Stack says the breakage probably happened with the new master.

--
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] [Resolved] (HBASE-4570) Scan ACID problem with concurrent puts.

2011-10-17 Thread Todd Lipcon (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HBASE-4570.


   Resolution: Fixed
Fix Version/s: 0.92.0
 Assignee: Jonathan Hsieh
 Hadoop Flags: Reviewed

Fixed in 90, 92, trunk branches

> Scan ACID problem with concurrent puts.
> ---
>
> Key: HBASE-4570
> URL: https://issues.apache.org/jira/browse/HBASE-4570
> Project: HBase
>  Issue Type: Bug
>  Components: client, regionserver
>Affects Versions: 0.90.1, 0.90.3
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
> Fix For: 0.92.0, 0.90.5
>
> Attachments: 4570-instrumentation.tgz, hbase-4570.tgz, hbase-4570.txt
>
>
> When scanning a table sometimes rows that have multiple column families get 
> split into two rows if there are concurrent writes.  In this particular case 
> we are overwriting the contents of a Get directly back onto itself as a Put.
> For example, this is a two cf row (with "f1", "f2", .. "f9" cfs).  It is 
> actually returned as two rows (#55 and #56). Interestingly if the two were 
> merged we would have a single proper row.
> Row row024461 had time stamps: [55: 
> keyvalues={row024461/f0:data/1318200440867/Put/vlen=1000, 
> row024461/f0:qual/1318200440867/Put/vlen=10, 
> row024461/f1:data/1318200440867/Put/vlen=1000, 
> row024461/f1:qual/1318200440867/Put/vlen=10, 
> row024461/f2:data/1318200440867/Put/vlen=1000, 
> row024461/f2:qual/1318200440867/Put/vlen=10, 
> row024461/f3:data/1318200440867/Put/vlen=1000, 
> row024461/f3:qual/1318200440867/Put/vlen=10, 
> row024461/f4:data/1318200440867/Put/vlen=1000, 
> row024461/f4:qual/1318200440867/Put/vlen=10}, 
> 56: keyvalues={row024461/f5:data/1318200440867/Put/vlen=1000, 
> row024461/f5:qual/1318200440867/Put/vlen=10, 
> row024461/f6:data/1318200440867/Put/vlen=1000, 
> row024461/f6:qual/1318200440867/Put/vlen=10, 
> row024461/f7:data/1318200440867/Put/vlen=1000, 
> row024461/f7:qual/1318200440867/Put/vlen=10, 
> row024461/f8:data/1318200440867/Put/vlen=1000, 
> row024461/f8:qual/1318200440867/Put/vlen=10, 
> row024461/f9:data/1318200440867/Put/vlen=1000, 
> row024461/f9:qual/1318200440867/Put/vlen=10}]
> I've only tested this on 0.90.1+patches and 0.90.3+patches, but it is 
> consistent and duplicatable.

--
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] [Resolved] (HBASE-4245) Cluster hangs if RS serving root fails during startup sequence

2011-10-03 Thread Todd Lipcon (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HBASE-4245.


Resolution: Duplicate

> Cluster hangs if RS serving root fails during startup sequence
> --
>
> Key: HBASE-4245
> URL: https://issues.apache.org/jira/browse/HBASE-4245
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Affects Versions: 0.90.3
>Reporter: Todd Lipcon
>Assignee: Ming Ma
>
> On a large-ish cluster, the following sequence of events was seen to happen:
> - master started, ROOT and META were both unassigned
> - ROOT is assigned to rs01
> - META is assigned to rs02
> - Upon open of META, it writes its location into ROOT on rs01
> - rs01 crashes while appending to its HLog due to some other bug
> - rs02 fails the region open sequence
> - master notices that rs01 has crashed, and enqueues a ServerShutdownHandler
> - ServerShutdownHandler blocks on CatalogTracker.waitForMeta() since ROOT and 
> META are not assigned yet
> - master times out assignment of META, but never succeeds because ROOT 
> location is still marked as rs01
> This causes the cluster to never start up.

--
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