[jira] [Created] (HBASE-24977) [Alter hbase:meta]: Making meta read only should not be be allowed
Ajeet Rai created HBASE-24977:
-
Summary: [Alter hbase:meta]: Making meta read only should not be
be allowed
Key: HBASE-24977
URL: https://issues.apache.org/jira/browse/HBASE-24977
Project: HBase
Issue Type: Bug
Components: meta
Affects Versions: 2.2.3
Reporter: Ajeet Rai
After HBASE-23055, Alter of Meta schema is allowed.
After this change meta table can be made Read only table which is not correct
as per my view,because it will impact majority of the functionality of HBase.
alter 'hbase:meta',\{METHOD=>'table_att', READONLY=>true}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24976) REST Server failes to start without any error message
lujie created HBASE-24976: - Summary: REST Server failes to start without any error message Key: HBASE-24976 URL: https://issues.apache.org/jira/browse/HBASE-24976 Project: HBase Issue Type: Bug Components: REST Affects Versions: 2.2.1 Reporter: lujie -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-24893) TestLogLevel failing on hadoop-ci (branch-1)
[
https://issues.apache.org/jira/browse/HBASE-24893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell reopened HBASE-24893:
-
> TestLogLevel failing on hadoop-ci (branch-1)
>
>
> Key: HBASE-24893
> URL: https://issues.apache.org/jira/browse/HBASE-24893
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Andrew Kyle Purtell
>Assignee: Abhey Rana
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> TestLogLevel is failing the branch-1 builds on hadoop-ci.
> The test needs some improvement. The code seems to be doing the right thing
> but the error condition the test is expecting varies by JVM or JVM version:
> {noformat}
> Expected to find 'Unrecognized SSL message' but got unexpected exception:
> javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24973) Remove read point parameter in method StoreFlush#performFlush and StoreFlush#createScanner
[
https://issues.apache.org/jira/browse/HBASE-24973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-24973.
Fix Version/s: 2.4.0
3.0.0-alpha-1
Resolution: Fixed
Pushed to branch-2+. Thanks [~yuqi] for contributing.
> Remove read point parameter in method StoreFlush#performFlush and
> StoreFlush#createScanner
> --
>
> Key: HBASE-24973
> URL: https://issues.apache.org/jira/browse/HBASE-24973
> Project: HBase
> Issue Type: Improvement
>Reporter: yuqi
>Assignee: yuqi
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> Currently, read point parameter in method StoreFlush#performFlush is useless
> and can be safely removed.
> and then method StoreFlush#createScanner can also remove this parameter
> See below
> {code:java}
> // Some comments here
> /**
>* Performs memstore flush, writing data from scanner into sink.
>* @param scanner Scanner to get data from.
>* @param sink Sink to write data to. Could be StoreFile.Writer.
>* @param smallestReadPoint Smallest read point used for the flush.
>* @param throughputController A controller to avoid flush too fast
>*/
> protected void performFlush(InternalScanner scanner, CellSink sink,
> long smallestReadPoint, ThroughputController throughputController)
> throws IOException
> {code}
> Parameter smallestReadPoint is not used in this method. When
> `smallestReadPoint` is removed, inner method `createScanner` can remove this
> necessary parameter too
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24831) Avoid invoke Counter using reflection in SnapshotInputFormat
[ https://issues.apache.org/jira/browse/HBASE-24831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-24831. Fix Version/s: 2.3.2 2.4.0 3.0.0-alpha-1 Resolution: Fixed Pushed to branch-2.3+. Thanks [~chenyechao] for contributing. > Avoid invoke Counter using reflection in SnapshotInputFormat > - > > Key: HBASE-24831 > URL: https://issues.apache.org/jira/browse/HBASE-24831 > Project: HBase > Issue Type: Improvement >Reporter: Yechao Chen >Assignee: Yechao Chen >Priority: Major > Labels: Performance, mapreduce, snapshot > Fix For: 3.0.0-alpha-1, 2.4.0, 2.3.2 > > > In TableRecordReaderImpl we invoke Counter increment by reflection > This will be called nextKeyValue() in TableSnapshotInputFormat > reflection invoke is very slower than normal method call > we can avoid these to improve the read performance -- This message was sent by Atlassian Jira (v8.3.4#803005)
