[jira] [Created] (HBASE-22980) HRegionPartioner getPartition() method incorrectly partitions the regions of the table.
Shardul Singh created HBASE-22980:
-
Summary: HRegionPartioner getPartition() method incorrectly
partitions the regions of the table.
Key: HBASE-22980
URL: https://issues.apache.org/jira/browse/HBASE-22980
Project: HBase
Issue Type: Bug
Environment: Instead of
{code:java}
if(i >= numPartitions-1)
{code}
It should be
{code:java}
if(i >= numPartitions)
{code}
Reporter: Shardul Singh
Assignee: Shardul Singh
In HRegionPartitioner getPartition(), the case where we have less reduces than
region is incorrect.
https://github.com/apache/hbase/blob/fbd5b5e32753104f88600b0f4c803ab5659bce64/hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/HRegionPartitioner.java#L92
Consider the following scenario:
1. if there are 5 regions for the table, partitions = 5 and number of reducers
is also 5.
So in this case above code should not return true. But for the last region when
i=4, getPartition should return 4 but it returns 2 because it falls in the case
of when we have less reduces than region and returns true for the above
condition.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (HBASE-22944) TableNotFoundException: hbase:quota is thrown when region server is restarted.
Shardul Singh created HBASE-22944:
-
Summary: TableNotFoundException: hbase:quota is thrown when
region server is restarted.
Key: HBASE-22944
URL: https://issues.apache.org/jira/browse/HBASE-22944
Project: HBase
Issue Type: Bug
Components: Quotas
Reporter: Shardul Singh
Assignee: Shardul Singh
SpaceQuotaRefresherChore does not checks whether hbase:quota table is
present,before starting its operation which sometimes may result to
TableNotFoundExceptions like below.
This is becuase master has not created the hbase:quota table and
SpaceQuotaRefresherChore is running.
```
java.io.UncheckedIOException: org.apache.hadoop.hbase.
{quote}TableNotFoundException: hbase:quota
{quote}
at
org.apache.hadoop.hbase.client.ResultScanner$1.hasNext(ResultScanner.java:55)
at
org.apache.hadoop.hbase.quotas.SpaceQuotaRefresherChore.fetchSnapshotsFromQuotaTable(SpaceQuotaRefresherChore.java:170)
at
org.apache.hadoop.hbase.quotas.SpaceQuotaRefresherChore.chore(SpaceQuotaRefresherChore.java:84)
at org.apache.hadoop.hbase.ScheduledChore.run(ScheduledChore.java:186)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
org.apache.hadoop.hbase.JitterScheduledThreadPoolExecutorImpl$JitteredRunnableScheduledFuture.run(JitterScheduledThreadPoolExecutorImpl.java:111)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
```
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (HBASE-22142) Space quota: If table is dropped inside namespace, data size usage is still considered for the drop table.
Shardul Singh created HBASE-22142: - Summary: Space quota: If table is dropped inside namespace, data size usage is still considered for the drop table. Key: HBASE-22142 URL: https://issues.apache.org/jira/browse/HBASE-22142 Project: HBase Issue Type: Bug Affects Versions: 2.1.1 Reporter: Shardul Singh steps to follow: 1.create a quota at namespace level 2.create 2 tables t1 and t2 inside namespace and write data. 3.write 5 mb of data each in both t1 and t2. 4. drop t1. 5. data usage for t2 will be shown 10 mb for 10 minutes. If table is dropped inside namespace, data size usage is still shown for 10 minutes because of the configuration "hbase.master.quotas.region.report.retention.millis". This conf maintains the region report in cache(regionSizes) and old entry is used for 10 minutes. We can remove the entry during the drop command only, so that correct usage is show instantaneously after the drop command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
