[jira] [Created] (HBASE-5214) synchronization issue during region assignment

2012-01-16 Thread Ming Ma (Created) (JIRA) 
synchronization issue during region assignment
--

 Key: HBASE-5214
 URL: https://issues.apache.org/jira/browse/HBASE-5214
 Project: HBase
  Issue Type: Bug
  Components: master
Reporter: Ming Ma


In master, both the shutdown threads and balancer thread could change the 
region state. It could create some race condition. HBase-4899 fixes the issue 
under normal situation. Still it seems like there is a really small time window 
HBase-4899 won't cover.

T1. ServerShutdownHandler. the check for if (rit != null  !rit.isClosing() 
 !rit.isPendingClose() return false as the region is still in closing state. 
It is actually closed by the RS; Master's state is closing due to the delay 
in ZK notification.
T2. Right after the above check, ZK notification happens and Master starts the 
opening of the region as requested by load balancer.
T3. else { this.services.getAssignmentManager().assign(e.getKey(), true); } 
is called for another assignment.

Also HBase-5094 has fixes and discussion about this.

Could we make it such that only one thread can transition a region at a time?

--
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-5105) TestImportTsv failed with hadoop 0.22

2011-12-29 Thread Ming Ma (Created) (JIRA) 
TestImportTsv failed with hadoop 0.22
-

 Key: HBASE-5105
 URL: https://issues.apache.org/jira/browse/HBASE-5105
 Project: HBase
  Issue Type: Bug
  Components: test
Affects Versions: 0.92.0
Reporter: Ming Ma


java.io.FileNotFoundException: File does not exist: 
/home/henkins/.m2/repository/org/apache/hadoop/hadoop-mapred/0.22-SNAPSHOT/hadoop-mapred-0.22-SNAPSHOT.jar
at 
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:742)
at 
org.apache.hadoop.mapreduce.filecache.TrackerDistributedCacheManager.getFileStatus(TrackerDistributedCacheManager.java:331)
at 
org.apache.hadoop.mapreduce.filecache.TrackerDistributedCacheManager.determineTimestamps(TrackerDistributedCacheManager.java:711)
at 
org.apache.hadoop.mapreduce.JobSubmitter.copyAndConfigureFiles(JobSubmitter.java:245)
at 
org.apache.hadoop.mapreduce.JobSubmitter.copyAndConfigureFiles(JobSubmitter.java:283)
at 
org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:350)
at org.apache.hadoop.mapreduce.Job$2.run(Job.java:1045)
at org.apache.hadoop.mapreduce.Job$2.run(Job.java:1042)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1153)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1042)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1062)
at 
org.apache.hadoop.hbase.mapreduce.TestImportTsv.doMROnTableTest(TestImportTsv.java:215)
at 
org.apache.hadoop.hbase.mapreduce.TestImportTsv.testMROnTable(TestImportTsv.java:165)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


--
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-5109) Fix TestAvroServer so that it waits properly for the modifyTable operation to complete

2011-12-29 Thread Ming Ma (Created) (JIRA) 
Fix TestAvroServer so that it waits properly for the modifyTable operation to 
complete
--

 Key: HBASE-5109
 URL: https://issues.apache.org/jira/browse/HBASE-5109
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: Ming Ma
Assignee: Ming Ma


TestAvroServer has the following issue
 
impl.modifyTable(tableAname, tableA);
// It can take a while for the change to take effect. Wait here a while.
while(impl.describeTable(tableAname) == null ) {
  Threads.sleep(100);
}
assertTrue(impl.describeTable(tableAname).maxFileSize == 123456L);
 
impl.describeTable(tableAname) returns the default maxSize 256M right away as 
modifyTable is async. Before HBASE-4328 is fixed, we can fix the test code to 
wait for say max of 5 seconds to check if 
impl.describeTable(tableAname).maxFileSize is uploaded to 123456L. 

--
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-4524) support for more than one region in .META. table

2011-09-30 Thread Ming Ma (Created) (JIRA) 
support for more than one region in .META. table


 Key: HBASE-4524
 URL: https://issues.apache.org/jira/browse/HBASE-4524
 Project: HBase
  Issue Type: Improvement
Reporter: Ming Ma
Assignee: Ming Ma


It seems there are some assumptions in the code that .META. table only has one 
region FIRST_META_REGIONINFO in the following areas:

1) .META. table update with user region info.
2) .META. regions assignment.
3) .META. table split handling.

Perhaps we don't have such requirement until we scale to really large number of 
regions like 1M.

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