[jira] [Created] (HBASE-24282) 'scandetail' log message is missing when responseTooSlow happens on the first scan rpc call
song XinCun created HBASE-24282: --- Summary: 'scandetail' log message is missing when responseTooSlow happens on the first scan rpc call Key: HBASE-24282 URL: https://issues.apache.org/jira/browse/HBASE-24282 Project: HBase Issue Type: Bug Reporter: song XinCun When responseTooSlow happens, the 'scandetail' message is printed to the warn log. But when the call is the first scan rpc call, this message is missing. This is because we get the 'scandetail' message with scannerId, but the first scan rpc call doesn't have scannerId yet. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-24282) 'scandetail' log message is missing when responseTooSlow happens on the first scan rpc call
[ https://issues.apache.org/jira/browse/HBASE-24282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun reassigned HBASE-24282: --- Assignee: song XinCun > 'scandetail' log message is missing when responseTooSlow happens on the first > scan rpc call > --- > > Key: HBASE-24282 > URL: https://issues.apache.org/jira/browse/HBASE-24282 > Project: HBase > Issue Type: Bug >Reporter: song XinCun >Assignee: song XinCun >Priority: Major > > When responseTooSlow happens, the 'scandetail' message is printed to the warn > log. But when the call is the first scan rpc call, this message is missing. > This is because we get the 'scandetail' message with scannerId, but the first > scan rpc call doesn't have scannerId yet. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24282) 'scandetail' log message is missing when responseTooSlow happens on the first scan rpc call
[ https://issues.apache.org/jira/browse/HBASE-24282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24282: Component/s: Operability > 'scandetail' log message is missing when responseTooSlow happens on the first > scan rpc call > --- > > Key: HBASE-24282 > URL: https://issues.apache.org/jira/browse/HBASE-24282 > Project: HBase > Issue Type: Bug > Components: Operability >Reporter: song XinCun >Assignee: song XinCun >Priority: Major > > When responseTooSlow happens, the 'scandetail' message is printed to the warn > log. But when the call is the first scan rpc call, this message is missing. > This is because we get the 'scandetail' message with scannerId, but the first > scan rpc call doesn't have scannerId yet. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24288) Allow admin user to create table and do bulkLoad
song XinCun created HBASE-24288: --- Summary: Allow admin user to create table and do bulkLoad Key: HBASE-24288 URL: https://issues.apache.org/jira/browse/HBASE-24288 Project: HBase Issue Type: Bug Components: acl Affects Versions: 2.2.2 Reporter: song XinCun Assignee: song XinCun Allow admin user who doesn't have CREATE privileges to create table and do bulkload. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24288) Allow admin user to create table and do bulkLoad
[ https://issues.apache.org/jira/browse/HBASE-24288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24288: Description: Allow admin users who don't have CREATE privileges to create tables and do bulkload. (was: Allow admin user who doesn't have CREATE privileges to create table and do bulkload.) > Allow admin user to create table and do bulkLoad > > > Key: HBASE-24288 > URL: https://issues.apache.org/jira/browse/HBASE-24288 > Project: HBase > Issue Type: Bug > Components: acl >Affects Versions: 2.2.2 >Reporter: song XinCun >Assignee: song XinCun >Priority: Major > > Allow admin users who don't have CREATE privileges to create tables and do > bulkload. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24441) CacheConfig details logged at Store open is not really useful
[
https://issues.apache.org/jira/browse/HBASE-24441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117566#comment-17117566
]
song XinCun commented on HBASE-24441:
-
[~anoop.hbase] If you don't mind, can I take this?
> CacheConfig details logged at Store open is not really useful
> -
>
> Key: HBASE-24441
> URL: https://issues.apache.org/jira/browse/HBASE-24441
> Project: HBase
> Issue Type: Improvement
>Reporter: Anoop Sam John
>Assignee: Anoop Sam John
>Priority: Minor
>
> CacheConfig constructor is logging 'this' object at INFO level. This log
> comes during Store open(As CacheConfig instance for that store is created).
> As the log is at CacheConfig only, we don't get to know this is for which
> region:store. So not really useful log.
> {code}
> blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@7bc02941,
> cacheDataOnRead=true, cacheDataOnWrite=true, cacheIndexesOnWrite=false,
> cacheBloomsOnWrite=false, cacheEvictOnClose=false, cacheDataCompressed=false,
> prefetchOnOpen=false
> {code}
> Also during every compaction also this logs keeps coming. This is because
> during compaction we create new CacheConfig based on the HStore level
> CacheConfig object. We can avoid this log with every compaction happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HBASE-24441) CacheConfig details logged at Store open is not really useful
[
https://issues.apache.org/jira/browse/HBASE-24441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun reassigned HBASE-24441:
---
Assignee: song XinCun (was: Anoop Sam John)
> CacheConfig details logged at Store open is not really useful
> -
>
> Key: HBASE-24441
> URL: https://issues.apache.org/jira/browse/HBASE-24441
> Project: HBase
> Issue Type: Improvement
>Reporter: Anoop Sam John
>Assignee: song XinCun
>Priority: Minor
>
> CacheConfig constructor is logging 'this' object at INFO level. This log
> comes during Store open(As CacheConfig instance for that store is created).
> As the log is at CacheConfig only, we don't get to know this is for which
> region:store. So not really useful log.
> {code}
> blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@7bc02941,
> cacheDataOnRead=true, cacheDataOnWrite=true, cacheIndexesOnWrite=false,
> cacheBloomsOnWrite=false, cacheEvictOnClose=false, cacheDataCompressed=false,
> prefetchOnOpen=false
> {code}
> Also during every compaction also this logs keeps coming. This is because
> during compaction we create new CacheConfig based on the HStore level
> CacheConfig object. We can avoid this log with every compaction happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24441) CacheConfig details logged at Store open is not really useful
[
https://issues.apache.org/jira/browse/HBASE-24441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119247#comment-17119247
]
song XinCun commented on HBASE-24441:
-
Log after patch would look like:
{code:java}
2020-05-28 21:35:46,842 INFO [StoreOpener-3e735faebf71bb030f365fac2427f7bd-1]
hfile.CacheConfig: Created cacheConfig: cacheDataOnRead=true,
cacheDataOnWrite=true, cacheIndexesOnWrite=true, cacheBloomsOnWrite=true,
cacheEvictOnClose=false, cacheDataCompressed=false, prefetchOnOpen=false for
family {NAME => 'cf', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS => 'FALSE',
CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'DIFF', TTL =>
'FOREVER', MIN_VERSIONS => '0', REPLICATION_SCOPE => '0', BLOOMFILTER => 'ROW',
CACHE_INDEX_ON_WRITE => 'false', IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE =>
'false', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'SNAPPY',
BLOCKCACHE => 'true', BLOCKSIZE => '65536'} in region
table_100B_10,user5246,1590642270538.3e735faebf71bb030f365fac2427f7bd. with
blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@47c0732b
{code}
The region info which contains table and region name is added to the log.
> CacheConfig details logged at Store open is not really useful
> -
>
> Key: HBASE-24441
> URL: https://issues.apache.org/jira/browse/HBASE-24441
> Project: HBase
> Issue Type: Improvement
>Reporter: Anoop Sam John
>Assignee: song XinCun
>Priority: Minor
>
> CacheConfig constructor is logging 'this' object at INFO level. This log
> comes during Store open(As CacheConfig instance for that store is created).
> As the log is at CacheConfig only, we don't get to know this is for which
> region:store. So not really useful log.
> {code}
> blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@7bc02941,
> cacheDataOnRead=true, cacheDataOnWrite=true, cacheIndexesOnWrite=false,
> cacheBloomsOnWrite=false, cacheEvictOnClose=false, cacheDataCompressed=false,
> prefetchOnOpen=false
> {code}
> Also during every compaction also this logs keeps coming. This is because
> during compaction we create new CacheConfig based on the HStore level
> CacheConfig object. We can avoid this log with every compaction happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-24441) CacheConfig details logged at Store open is not really useful
[
https://issues.apache.org/jira/browse/HBASE-24441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun updated HBASE-24441:
Component/s: regionserver
logging
> CacheConfig details logged at Store open is not really useful
> -
>
> Key: HBASE-24441
> URL: https://issues.apache.org/jira/browse/HBASE-24441
> Project: HBase
> Issue Type: Improvement
> Components: logging, regionserver
>Reporter: Anoop Sam John
>Assignee: song XinCun
>Priority: Minor
>
> CacheConfig constructor is logging 'this' object at INFO level. This log
> comes during Store open(As CacheConfig instance for that store is created).
> As the log is at CacheConfig only, we don't get to know this is for which
> region:store. So not really useful log.
> {code}
> blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@7bc02941,
> cacheDataOnRead=true, cacheDataOnWrite=true, cacheIndexesOnWrite=false,
> cacheBloomsOnWrite=false, cacheEvictOnClose=false, cacheDataCompressed=false,
> prefetchOnOpen=false
> {code}
> Also during every compaction also this logs keeps coming. This is because
> during compaction we create new CacheConfig based on the HStore level
> CacheConfig object. We can avoid this log with every compaction happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-24441) CacheConfig details logged at Store open is not really useful
[
https://issues.apache.org/jira/browse/HBASE-24441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun updated HBASE-24441:
Affects Version/s: 2.2.5
> CacheConfig details logged at Store open is not really useful
> -
>
> Key: HBASE-24441
> URL: https://issues.apache.org/jira/browse/HBASE-24441
> Project: HBase
> Issue Type: Improvement
> Components: logging, regionserver
>Affects Versions: 2.2.5
>Reporter: Anoop Sam John
>Assignee: song XinCun
>Priority: Minor
>
> CacheConfig constructor is logging 'this' object at INFO level. This log
> comes during Store open(As CacheConfig instance for that store is created).
> As the log is at CacheConfig only, we don't get to know this is for which
> region:store. So not really useful log.
> {code}
> blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@7bc02941,
> cacheDataOnRead=true, cacheDataOnWrite=true, cacheIndexesOnWrite=false,
> cacheBloomsOnWrite=false, cacheEvictOnClose=false, cacheDataCompressed=false,
> prefetchOnOpen=false
> {code}
> Also during every compaction also this logs keeps coming. This is because
> during compaction we create new CacheConfig based on the HStore level
> CacheConfig object. We can avoid this log with every compaction happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-24441) CacheConfig details logged at Store open is not really useful
[
https://issues.apache.org/jira/browse/HBASE-24441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun updated HBASE-24441:
Affects Version/s: (was: 2.2.5)
3.0.0-alpha-1
> CacheConfig details logged at Store open is not really useful
> -
>
> Key: HBASE-24441
> URL: https://issues.apache.org/jira/browse/HBASE-24441
> Project: HBase
> Issue Type: Improvement
> Components: logging, regionserver
>Affects Versions: 3.0.0-alpha-1
>Reporter: Anoop Sam John
>Assignee: song XinCun
>Priority: Minor
>
> CacheConfig constructor is logging 'this' object at INFO level. This log
> comes during Store open(As CacheConfig instance for that store is created).
> As the log is at CacheConfig only, we don't get to know this is for which
> region:store. So not really useful log.
> {code}
> blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@7bc02941,
> cacheDataOnRead=true, cacheDataOnWrite=true, cacheIndexesOnWrite=false,
> cacheBloomsOnWrite=false, cacheEvictOnClose=false, cacheDataCompressed=false,
> prefetchOnOpen=false
> {code}
> Also during every compaction also this logs keeps coming. This is because
> during compaction we create new CacheConfig based on the HStore level
> CacheConfig object. We can avoid this log with every compaction happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24468) Add region info when log meessages in HStore.
song XinCun created HBASE-24468:
---
Summary: Add region info when log meessages in HStore.
Key: HBASE-24468
URL: https://issues.apache.org/jira/browse/HBASE-24468
Project: HBase
Issue Type: Improvement
Components: logging, regionserver
Affects Versions: 3.0.0-alpha-1
Reporter: song XinCun
Assignee: song XinCun
Region info message is need to added when HStore is created
{code:java}
2020-05-28 21:39:55,515 INFO [StoreOpener-84d6181342585332d77c9e4ee2f9ef19-1]
regionserver.HStore: Store=cf, memstore type=DefaultMemStore,
storagePolicy=HOT, verifyBulkLoads=false, parallelPutCountPrintThreshold=50,
encoding=DIFF, compression=SNAPPY{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-24468) Add region info when log meessages in HStore.
[
https://issues.apache.org/jira/browse/HBASE-24468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun updated HBASE-24468:
Description:
Region info message is need to added when HStore is created or some other logs
{code:java}
2020-05-28 21:39:55,515 INFO [StoreOpener-84d6181342585332d77c9e4ee2f9ef19-1]
regionserver.HStore: Store=cf, memstore type=DefaultMemStore,
storagePolicy=HOT, verifyBulkLoads=false, parallelPutCountPrintThreshold=50,
encoding=DIFF, compression=SNAPPY{code}
was:
Region info message is need to added when HStore is created
{code:java}
2020-05-28 21:39:55,515 INFO [StoreOpener-84d6181342585332d77c9e4ee2f9ef19-1]
regionserver.HStore: Store=cf, memstore type=DefaultMemStore,
storagePolicy=HOT, verifyBulkLoads=false, parallelPutCountPrintThreshold=50,
encoding=DIFF, compression=SNAPPY{code}
> Add region info when log meessages in HStore.
> -
>
> Key: HBASE-24468
> URL: https://issues.apache.org/jira/browse/HBASE-24468
> Project: HBase
> Issue Type: Improvement
> Components: logging, regionserver
>Affects Versions: 3.0.0-alpha-1
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Minor
>
> Region info message is need to added when HStore is created or some other logs
> {code:java}
> 2020-05-28 21:39:55,515 INFO
> [StoreOpener-84d6181342585332d77c9e4ee2f9ef19-1] regionserver.HStore:
> Store=cf, memstore type=DefaultMemStore, storagePolicy=HOT,
> verifyBulkLoads=false, parallelPutCountPrintThreshold=50, encoding=DIFF,
> compression=SNAPPY{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (HBASE-24468) Add region info when log meessages in HStore.
[
https://issues.apache.org/jira/browse/HBASE-24468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun updated HBASE-24468:
Description:
Region info is needed to be added when HStore is created or in some other case
{code:java}
2020-05-28 21:39:55,515 INFO [StoreOpener-84d6181342585332d77c9e4ee2f9ef19-1]
regionserver.HStore: Store=cf, memstore type=DefaultMemStore,
storagePolicy=HOT, verifyBulkLoads=false, parallelPutCountPrintThreshold=50,
encoding=DIFF, compression=SNAPPY{code}
was:
Region info message is need to added when HStore is created or some other logs
{code:java}
2020-05-28 21:39:55,515 INFO [StoreOpener-84d6181342585332d77c9e4ee2f9ef19-1]
regionserver.HStore: Store=cf, memstore type=DefaultMemStore,
storagePolicy=HOT, verifyBulkLoads=false, parallelPutCountPrintThreshold=50,
encoding=DIFF, compression=SNAPPY{code}
> Add region info when log meessages in HStore.
> -
>
> Key: HBASE-24468
> URL: https://issues.apache.org/jira/browse/HBASE-24468
> Project: HBase
> Issue Type: Improvement
> Components: logging, regionserver
>Affects Versions: 3.0.0-alpha-1
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Minor
>
> Region info is needed to be added when HStore is created or in some other case
> {code:java}
> 2020-05-28 21:39:55,515 INFO
> [StoreOpener-84d6181342585332d77c9e4ee2f9ef19-1] regionserver.HStore:
> Store=cf, memstore type=DefaultMemStore, storagePolicy=HOT,
> verifyBulkLoads=false, parallelPutCountPrintThreshold=50, encoding=DIFF,
> compression=SNAPPY{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24470) Add store file info when log meessages in HStore.
song XinCun created HBASE-24470: --- Summary: Add store file info when log meessages in HStore. Key: HBASE-24470 URL: https://issues.apache.org/jira/browse/HBASE-24470 Project: HBase Issue Type: Improvement Components: logging, regionserver Affects Versions: 3.0.0-alpha-1 Reporter: song XinCun Assignee: song XinCun Some log message do not have store file info when log, need to add it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24468) Add region info when log meessages in HStore.
[
https://issues.apache.org/jira/browse/HBASE-24468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun updated HBASE-24468:
Description: Some log message do not have region info when log, need to add
it. (was: Region info is needed to be added when HStore is created or in some
other case
{code:java}
2020-05-28 21:39:55,515 INFO [StoreOpener-84d6181342585332d77c9e4ee2f9ef19-1]
regionserver.HStore: Store=cf, memstore type=DefaultMemStore,
storagePolicy=HOT, verifyBulkLoads=false, parallelPutCountPrintThreshold=50,
encoding=DIFF, compression=SNAPPY{code})
> Add region info when log meessages in HStore.
> -
>
> Key: HBASE-24468
> URL: https://issues.apache.org/jira/browse/HBASE-24468
> Project: HBase
> Issue Type: Improvement
> Components: logging, regionserver
>Affects Versions: 3.0.0-alpha-1
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Minor
>
> Some log message do not have region info when log, need to add it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work stopped] (HBASE-24010) HBase shell list_peers command is displayed incorrectly
[
https://issues.apache.org/jira/browse/HBASE-24010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-24010 stopped by song XinCun.
---
> HBase shell list_peers command is displayed incorrectly
> ---
>
> Key: HBASE-24010
> URL: https://issues.apache.org/jira/browse/HBASE-24010
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Major
>
> In 2.X version, I found hbase shell list_peers command displays java object
> id not the human readable peer messages
> {code:java}
> hbase(main):002:0> list_peers
> PEER_ID CLUSTER_KEY ENDPOINT_CLASSNAME STATE REPLICATE_ALL NAMESPACES
> TABLE_CFS BANDWIDTH SERIAL
> 0 row(s)
> Took 0.3336 seconds
> => #
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (HBASE-24441) CacheConfig details logged at Store open is not really useful
[
https://issues.apache.org/jira/browse/HBASE-24441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun updated HBASE-24441:
Comment: was deleted
(was: Log after patch would look like:
{code:java}
2020-05-28 21:35:46,842 INFO [StoreOpener-3e735faebf71bb030f365fac2427f7bd-1]
hfile.CacheConfig: Created cacheConfig: cacheDataOnRead=true,
cacheDataOnWrite=true, cacheIndexesOnWrite=true, cacheBloomsOnWrite=true,
cacheEvictOnClose=false, cacheDataCompressed=false, prefetchOnOpen=false for
family {NAME => 'cf', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS => 'FALSE',
CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'DIFF', TTL =>
'FOREVER', MIN_VERSIONS => '0', REPLICATION_SCOPE => '0', BLOOMFILTER => 'ROW',
CACHE_INDEX_ON_WRITE => 'false', IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE =>
'false', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'SNAPPY',
BLOCKCACHE => 'true', BLOCKSIZE => '65536'} in region
table_100B_10,user5246,1590642270538.3e735faebf71bb030f365fac2427f7bd. with
blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@47c0732b
{code}
The region info which contains table and region name is added to the log.)
> CacheConfig details logged at Store open is not really useful
> -
>
> Key: HBASE-24441
> URL: https://issues.apache.org/jira/browse/HBASE-24441
> Project: HBase
> Issue Type: Improvement
> Components: logging, regionserver
>Affects Versions: 3.0.0-alpha-1
>Reporter: Anoop Sam John
>Assignee: song XinCun
>Priority: Minor
>
> CacheConfig constructor is logging 'this' object at INFO level. This log
> comes during Store open(As CacheConfig instance for that store is created).
> As the log is at CacheConfig only, we don't get to know this is for which
> region:store. So not really useful log.
> {code}
> blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@7bc02941,
> cacheDataOnRead=true, cacheDataOnWrite=true, cacheIndexesOnWrite=false,
> cacheBloomsOnWrite=false, cacheEvictOnClose=false, cacheDataCompressed=false,
> prefetchOnOpen=false
> {code}
> Also during every compaction also this logs keeps coming. This is because
> during compaction we create new CacheConfig based on the HStore level
> CacheConfig object. We can avoid this log with every compaction happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24478) The regionInfo parameter for MasterProcedureScheduler#waitRegions should be plural
song XinCun created HBASE-24478: --- Summary: The regionInfo parameter for MasterProcedureScheduler#waitRegions should be plural Key: HBASE-24478 URL: https://issues.apache.org/jira/browse/HBASE-24478 Project: HBase Issue Type: Improvement Components: proc-v2 Affects Versions: 3.0.0-alpha-1 Reporter: song XinCun Assignee: song XinCun MasterProcedureScheduler#waitRegions deal with a list of regions, so the variable name of region info should be plural -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24478) The regionInfo parameter for MasterProcedureScheduler#waitRegions should be plural
[ https://issues.apache.org/jira/browse/HBASE-24478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120545#comment-17120545 ] song XinCun commented on HBASE-24478: - Same so for MasterProcedureScheduler#wakeRegions > The regionInfo parameter for MasterProcedureScheduler#waitRegions should be > plural > --- > > Key: HBASE-24478 > URL: https://issues.apache.org/jira/browse/HBASE-24478 > Project: HBase > Issue Type: Improvement > Components: proc-v2 >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > > MasterProcedureScheduler#waitRegions deal with a list of regions, so the > variable name of region info should be plural -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24478) The regionInfo parameter for MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions should be plural
[ https://issues.apache.org/jira/browse/HBASE-24478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24478: Summary: The regionInfo parameter for MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions should be plural (was: The regionInfo parameter for MasterProcedureScheduler#waitRegions should be plural ) > The regionInfo parameter for MasterProcedureScheduler#waitRegions and > MasterProcedureScheduler#wakeRegions should be plural > > > Key: HBASE-24478 > URL: https://issues.apache.org/jira/browse/HBASE-24478 > Project: HBase > Issue Type: Improvement > Components: proc-v2 >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > > MasterProcedureScheduler#waitRegions deal with a list of regions, so the > variable name of region info should be plural -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24478) The regionInfo parameter for MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions should be plural
[ https://issues.apache.org/jira/browse/HBASE-24478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24478: Description: MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions deal with a list of regions, so the variable name of region info should be plural (was: MasterProcedureScheduler#waitRegions deal with a list of regions, so the variable name of region info should be plural) > The regionInfo parameter for MasterProcedureScheduler#waitRegions and > MasterProcedureScheduler#wakeRegions should be plural > > > Key: HBASE-24478 > URL: https://issues.apache.org/jira/browse/HBASE-24478 > Project: HBase > Issue Type: Improvement > Components: proc-v2 >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > > MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions > deal with a list of regions, so the variable name of region info should be > plural -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24010) HBase shell list_peers command is displayed incorrectly
song XinCun created HBASE-24010:
---
Summary: HBase shell list_peers command is displayed incorrectly
Key: HBASE-24010
URL: https://issues.apache.org/jira/browse/HBASE-24010
Project: HBase
Issue Type: Bug
Components: shell
Reporter: song XinCun
In 2.X version, I found hbase shell list_peers command displays java object id
not the human readable peer messages
{code:java}
hbase(main):002:0> list_peers
PEER_ID CLUSTER_KEY ENDPOINT_CLASSNAME STATE REPLICATE_ALL NAMESPACES
TABLE_CFS BANDWIDTH SERIAL
0 row(s)
Took 0.3336 seconds
=> #
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (HBASE-24010) HBase shell list_peers command is displayed incorrectly
[
https://issues.apache.org/jira/browse/HBASE-24010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-24010 started by song XinCun.
---
> HBase shell list_peers command is displayed incorrectly
> ---
>
> Key: HBASE-24010
> URL: https://issues.apache.org/jira/browse/HBASE-24010
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Major
>
> In 2.X version, I found hbase shell list_peers command displays java object
> id not the human readable peer messages
> {code:java}
> hbase(main):002:0> list_peers
> PEER_ID CLUSTER_KEY ENDPOINT_CLASSNAME STATE REPLICATE_ALL NAMESPACES
> TABLE_CFS BANDWIDTH SERIAL
> 0 row(s)
> Took 0.3336 seconds
> => #
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (HBASE-22879) user_permission command failed to show global permission
[
https://issues.apache.org/jira/browse/HBASE-22879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun reopened HBASE-22879:
-
Assignee: song XinCun (was: Yi Mei)
This exception is still occurred when we use '.*' as the argument of
user_permission
{code:java}
hbase(main):001:0> grant 'user3', 'RW'
Took 0.4144 seconds
hbase(main):002:0> user_permission
User
Namespace,Table,Family,Qualifier:Permission
user2 ,,,: [Permission:
actions=READ,WRITE]
user3 ,,,: [Permission:
actions=READ,WRITE]
hbaseadmin ,,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
3 row(s)
Took 0.0445 seconds
hbase(main):003:0> user_permission '.*'
User
Namespace,Table,Family,Qualifier:Permission
user1 default,t1,,: [Permission:
actions=READ,WRITE]
hbaseadmin default,t1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
ERROR: failed to coerce
org.apache.hadoop.hbase.security.access.GlobalPermission to
org.apache.hadoop.hbase.security.access.TablePermissionFor usage try 'help
"user_permission"'Took 0.0940 seconds
{code}
> user_permission command failed to show global permission
>
>
> Key: HBASE-22879
> URL: https://issues.apache.org/jira/browse/HBASE-22879
> Project: HBase
> Issue Type: Bug
>Reporter: Yi Mei
>Assignee: song XinCun
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.1
>
>
> When use user_permission command to show global permissions, the following
> exception occurred:
> {code:java}
> hbase(main):001:0> user_permission
> User Namespace,Table,Family,Qualifier:Permission
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermission
> For usage try 'help "user_permission"'
> Took 1.1249 seconds
> hbase(main):002:0>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work stopped] (HBASE-22879) user_permission command failed to show global permission
[
https://issues.apache.org/jira/browse/HBASE-22879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-22879 stopped by song XinCun.
---
> user_permission command failed to show global permission
>
>
> Key: HBASE-22879
> URL: https://issues.apache.org/jira/browse/HBASE-22879
> Project: HBase
> Issue Type: Bug
>Reporter: Yi Mei
>Assignee: song XinCun
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.1
>
>
> When use user_permission command to show global permissions, the following
> exception occurred:
> {code:java}
> hbase(main):001:0> user_permission
> User Namespace,Table,Family,Qualifier:Permission
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermission
> For usage try 'help "user_permission"'
> Took 1.1249 seconds
> hbase(main):002:0>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (HBASE-22879) user_permission command failed to show global permission
[
https://issues.apache.org/jira/browse/HBASE-22879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-22879 started by song XinCun.
---
> user_permission command failed to show global permission
>
>
> Key: HBASE-22879
> URL: https://issues.apache.org/jira/browse/HBASE-22879
> Project: HBase
> Issue Type: Bug
>Reporter: Yi Mei
>Assignee: song XinCun
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.1
>
>
> When use user_permission command to show global permissions, the following
> exception occurred:
> {code:java}
> hbase(main):001:0> user_permission
> User Namespace,Table,Family,Qualifier:Permission
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermission
> For usage try 'help "user_permission"'
> Took 1.1249 seconds
> hbase(main):002:0>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (HBASE-22879) user_permission command failed to show global permission
[
https://issues.apache.org/jira/browse/HBASE-22879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun updated HBASE-22879:
Comment: was deleted
(was: This exception is still occurred when we use '.*' as the argument of
user_permission
{code:java}
hbase(main):001:0> grant 'user3', 'RW'
Took 0.4144 seconds
hbase(main):002:0> user_permission
User
Namespace,Table,Family,Qualifier:Permission
user2 ,,,: [Permission:
actions=READ,WRITE]
user3 ,,,: [Permission:
actions=READ,WRITE]
hbaseadmin ,,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
3 row(s)
Took 0.0445 seconds
hbase(main):003:0> user_permission '.*'
User
Namespace,Table,Family,Qualifier:Permission
user1 default,t1,,: [Permission:
actions=READ,WRITE]
hbaseadmin default,t1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
ERROR: failed to coerce
org.apache.hadoop.hbase.security.access.GlobalPermission to
org.apache.hadoop.hbase.security.access.TablePermissionFor usage try 'help
"user_permission"'Took 0.0940 seconds
{code})
> user_permission command failed to show global permission
>
>
> Key: HBASE-22879
> URL: https://issues.apache.org/jira/browse/HBASE-22879
> Project: HBase
> Issue Type: Bug
>Reporter: Yi Mei
>Assignee: song XinCun
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.1
>
>
> When use user_permission command to show global permissions, the following
> exception occurred:
> {code:java}
> hbase(main):001:0> user_permission
> User Namespace,Table,Family,Qualifier:Permission
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermission
> For usage try 'help "user_permission"'
> Took 1.1249 seconds
> hbase(main):002:0>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HBASE-22879) user_permission command failed to show global permission
[
https://issues.apache.org/jira/browse/HBASE-22879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun reassigned HBASE-22879:
---
Assignee: Yi Mei (was: song XinCun)
> user_permission command failed to show global permission
>
>
> Key: HBASE-22879
> URL: https://issues.apache.org/jira/browse/HBASE-22879
> Project: HBase
> Issue Type: Bug
>Reporter: Yi Mei
>Assignee: Yi Mei
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.1
>
>
> When use user_permission command to show global permissions, the following
> exception occurred:
> {code:java}
> hbase(main):001:0> user_permission
> User Namespace,Table,Family,Qualifier:Permission
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermission
> For usage try 'help "user_permission"'
> Took 1.1249 seconds
> hbase(main):002:0>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-22879) user_permission command failed to show global permission
[
https://issues.apache.org/jira/browse/HBASE-22879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
song XinCun resolved HBASE-22879.
-
Resolution: Fixed
> user_permission command failed to show global permission
>
>
> Key: HBASE-22879
> URL: https://issues.apache.org/jira/browse/HBASE-22879
> Project: HBase
> Issue Type: Bug
>Reporter: Yi Mei
>Assignee: Yi Mei
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.1
>
>
> When use user_permission command to show global permissions, the following
> exception occurred:
> {code:java}
> hbase(main):001:0> user_permission
> User Namespace,Table,Family,Qualifier:Permission
> ERROR: failed to coerce
> org.apache.hadoop.hbase.security.access.GlobalPermission to
> org.apache.hadoop.hbase.security.access.TablePermission
> For usage try 'help "user_permission"'
> Took 1.1249 seconds
> hbase(main):002:0>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24176) user_permission '.*' command failed to show all table permissions
song XinCun created HBASE-24176:
---
Summary: user_permission '.*' command failed to show all table
permissions
Key: HBASE-24176
URL: https://issues.apache.org/jira/browse/HBASE-24176
Project: HBase
Issue Type: Bug
Reporter: song XinCun
Assignee: song XinCun
When we grant somebody global permission, then we use '.*' as the argument of
user_permission to show all table permissions, the following exception occurred:
{code:java}
hbase(main):001:0> grant 'user3', 'RW'
Took 0.4144 seconds
hbase(main):002:0> user_permission
User
Namespace,Table,Family,Qualifier:Permission
user2 ,,,: [Permission:
actions=READ,WRITE]
user3 ,,,: [Permission:
actions=READ,WRITE]
hbaseadmin ,,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
3 row(s)
Took 0.0445 seconds
hbase(main):003:0> user_permission '.*'
User
Namespace,Table,Family,Qualifier:Permission
user1 default,t1,,: [Permission:
actions=READ,WRITE]
hbaseadmin default,t1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
ERROR: failed to coerce
org.apache.hadoop.hbase.security.access.GlobalPermission to
org.apache.hadoop.hbase.security.access.TablePermissionFor usage try 'help
"user_permission"'Took 0.0940 seconds
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24605) Break long region names in the web
song XinCun created HBASE-24605: --- Summary: Break long region names in the web Key: HBASE-24605 URL: https://issues.apache.org/jira/browse/HBASE-24605 Project: HBase Issue Type: Improvement Reporter: song XinCun -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24605: Summary: Break long region names in the web UI (was: Break long region names in the web) > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement >Reporter: song XinCun >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun reassigned HBASE-24605: --- Attachment: image-2020-06-21-20-18-37-041.png image-2020-06-21-20-19-25-183.png image-2020-06-21-20-20-02-782.png image-2020-06-21-20-27-23-474.png image-2020-06-21-20-28-36-464.png image-2020-06-21-20-29-07-819.png Component/s: UI Affects Version/s: 3.0.0-alpha-1 Assignee: song XinCun Description: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=921,height=85! !image-2020-06-21-20-19-25-183.png! !image-2020-06-21-20-20-02-782.png! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png! !image-2020-06-21-20-28-36-464.png! !image-2020-06-21-20-29-07-819.png! Due Date: 21/Jun/20 Priority: Minor (was: Major) > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=921,height=85! > !image-2020-06-21-20-19-25-183.png! > !image-2020-06-21-20-20-02-782.png! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png! > !image-2020-06-21-20-28-36-464.png! > !image-2020-06-21-20-29-07-819.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24605: Description: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=704,height=65! !image-2020-06-21-20-19-25-183.png|width=786,height=34! !image-2020-06-21-20-20-02-782.png|width=587,height=158! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=1074,height=71! !image-2020-06-21-20-28-36-464.png! !image-2020-06-21-20-29-07-819.png! was: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=704,height=65! !image-2020-06-21-20-19-25-183.png|width=786,height=34! !image-2020-06-21-20-20-02-782.png|width=587,height=158! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png! !image-2020-06-21-20-28-36-464.png! !image-2020-06-21-20-29-07-819.png! > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=704,height=65! > !image-2020-06-21-20-19-25-183.png|width=786,height=34! > !image-2020-06-21-20-20-02-782.png|width=587,height=158! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png|width=1074,height=71! > !image-2020-06-21-20-28-36-464.png! > !image-2020-06-21-20-29-07-819.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24605: Description: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=704,height=65! !image-2020-06-21-20-19-25-183.png|width=786,height=34! !image-2020-06-21-20-20-02-782.png|width=587,height=158! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png! !image-2020-06-21-20-28-36-464.png! !image-2020-06-21-20-29-07-819.png! was: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=921,height=85! !image-2020-06-21-20-19-25-183.png! !image-2020-06-21-20-20-02-782.png! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png! !image-2020-06-21-20-28-36-464.png! !image-2020-06-21-20-29-07-819.png! > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=704,height=65! > !image-2020-06-21-20-19-25-183.png|width=786,height=34! > !image-2020-06-21-20-20-02-782.png|width=587,height=158! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png! > !image-2020-06-21-20-28-36-464.png! > !image-2020-06-21-20-29-07-819.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24605: Description: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=704,height=65! !image-2020-06-21-20-19-25-183.png|width=786,height=34! !image-2020-06-21-20-20-02-782.png|width=587,height=158! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=711,height=47! !image-2020-06-21-20-28-36-464.png|width=775,height=48! !image-2020-06-21-20-29-07-819.png|width=472,height=104! was: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=704,height=65! !image-2020-06-21-20-19-25-183.png|width=786,height=34! !image-2020-06-21-20-20-02-782.png|width=587,height=158! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=1074,height=71! !image-2020-06-21-20-28-36-464.png! !image-2020-06-21-20-29-07-819.png! > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=704,height=65! > !image-2020-06-21-20-19-25-183.png|width=786,height=34! > !image-2020-06-21-20-20-02-782.png|width=587,height=158! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png|width=711,height=47! > !image-2020-06-21-20-28-36-464.png|width=775,height=48! > !image-2020-06-21-20-29-07-819.png|width=472,height=104! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24605: Description: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=520,height=48! !image-2020-06-21-20-19-25-183.png|width=485,height=21! !image-2020-06-21-20-20-02-782.png|width=427,height=115! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=711,height=47! !image-2020-06-21-20-28-36-464.png|width=775,height=48! !image-2020-06-21-20-29-07-819.png|width=472,height=104! was: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=704,height=65! !image-2020-06-21-20-19-25-183.png|width=786,height=34! !image-2020-06-21-20-20-02-782.png|width=587,height=158! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=711,height=47! !image-2020-06-21-20-28-36-464.png|width=775,height=48! !image-2020-06-21-20-29-07-819.png|width=472,height=104! > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=520,height=48! > !image-2020-06-21-20-19-25-183.png|width=485,height=21! > !image-2020-06-21-20-20-02-782.png|width=427,height=115! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png|width=711,height=47! > !image-2020-06-21-20-28-36-464.png|width=775,height=48! > !image-2020-06-21-20-29-07-819.png|width=472,height=104! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24605: Description: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=542,height=50! !image-2020-06-21-20-19-25-183.png|width=531,height=23! !image-2020-06-21-20-20-02-782.png|width=542,height=146! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=711,height=47! !image-2020-06-21-20-28-36-464.png|width=775,height=48! !image-2020-06-21-20-29-07-819.png|width=472,height=104! was: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=520,height=48! !image-2020-06-21-20-19-25-183.png|width=485,height=21! !image-2020-06-21-20-20-02-782.png|width=427,height=115! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=711,height=47! !image-2020-06-21-20-28-36-464.png|width=775,height=48! !image-2020-06-21-20-29-07-819.png|width=472,height=104! > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=542,height=50! > !image-2020-06-21-20-19-25-183.png|width=531,height=23! > !image-2020-06-21-20-20-02-782.png|width=542,height=146! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png|width=711,height=47! > !image-2020-06-21-20-28-36-464.png|width=775,height=48! > !image-2020-06-21-20-29-07-819.png|width=472,height=104! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24605: Description: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=542,height=50! !image-2020-06-21-20-19-25-183.png|width=531,height=23! !image-2020-06-21-20-20-02-782.png|width=542,height=146! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=529,height=35! !image-2020-06-21-20-28-36-464.png|width=533,height=33! !image-2020-06-21-20-29-07-819.png|width=531,height=117! was: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=542,height=50! !image-2020-06-21-20-19-25-183.png|width=531,height=23! !image-2020-06-21-20-20-02-782.png|width=542,height=146! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=529,height=35! !image-2020-06-21-20-28-36-464.png|width=775,height=48! !image-2020-06-21-20-29-07-819.png|width=472,height=104! > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=542,height=50! > !image-2020-06-21-20-19-25-183.png|width=531,height=23! > !image-2020-06-21-20-20-02-782.png|width=542,height=146! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png|width=529,height=35! > !image-2020-06-21-20-28-36-464.png|width=533,height=33! > !image-2020-06-21-20-29-07-819.png|width=531,height=117! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24605) Break long region names in the web UI
[ https://issues.apache.org/jira/browse/HBASE-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24605: Description: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=542,height=50! !image-2020-06-21-20-19-25-183.png|width=531,height=23! !image-2020-06-21-20-20-02-782.png|width=542,height=146! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=529,height=35! !image-2020-06-21-20-28-36-464.png|width=775,height=48! !image-2020-06-21-20-29-07-819.png|width=472,height=104! was: Before this patch, when it comes to the long region name, the UI content will be out of the screen, making it unreadable. Like this: !image-2020-06-21-20-18-37-041.png|width=542,height=50! !image-2020-06-21-20-19-25-183.png|width=531,height=23! !image-2020-06-21-20-20-02-782.png|width=542,height=146! After this patch, the long region name wil be break to the new line, like this: !image-2020-06-21-20-27-23-474.png|width=711,height=47! !image-2020-06-21-20-28-36-464.png|width=775,height=48! !image-2020-06-21-20-29-07-819.png|width=472,height=104! > Break long region names in the web UI > - > > Key: HBASE-24605 > URL: https://issues.apache.org/jira/browse/HBASE-24605 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > Attachments: image-2020-06-21-20-18-37-041.png, > image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, > image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, > image-2020-06-21-20-29-07-819.png > > > Before this patch, when it comes to the long region name, the UI content will > be out of the screen, making it unreadable. Like this: > !image-2020-06-21-20-18-37-041.png|width=542,height=50! > !image-2020-06-21-20-19-25-183.png|width=531,height=23! > !image-2020-06-21-20-20-02-782.png|width=542,height=146! > > After this patch, the long region name wil be break to the new line, like > this: > !image-2020-06-21-20-27-23-474.png|width=529,height=35! > !image-2020-06-21-20-28-36-464.png|width=775,height=48! > !image-2020-06-21-20-29-07-819.png|width=472,height=104! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24624) Optimize table.jsp code
song XinCun created HBASE-24624: --- Summary: Optimize table.jsp code Key: HBASE-24624 URL: https://issues.apache.org/jira/browse/HBASE-24624 Project: HBase Issue Type: Improvement Components: UI Affects Versions: 3.0.0-alpha-1 Reporter: song XinCun Assignee: song XinCun # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set the wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, make the code unreadable, remove it and let the page always show the replica id of regions. # Show 0 not null, when there is no primary region on regionserver, -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24624) Optimize table.jsp code
[ https://issues.apache.org/jira/browse/HBASE-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24624: Description: # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set the wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, remove it and let the page always show the replica id of regions. This can help to keep the code simple and the UI style union. # Show 0 not null, when there is no primary region on regionserver, was: # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set the wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, make the code unreadable, remove it and let the page always show the replica id of regions. # Show 0 not null, when there is no primary region on regionserver, > Optimize table.jsp code > --- > > Key: HBASE-24624 > URL: https://issues.apache.org/jira/browse/HBASE-24624 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > > # Rename buildRegionServerLink to buildRegionLink, for it returns the link of > region, not regionserver. > # Add buildRegionDeployedServerTag and moreRegionsToRender, this two > function can be used everywhere in table.jsp, and with them we can reduce a > lot of same code. > # Fix bug which locality stats tab can not sort. This is because we set the > wrong id for locality stats tab. > # We use too much "if (withReplica)..." statements, remove it and let the > page always show the replica id of regions. This can help to keep the code > simple and the UI style union. > # Show 0 not null, when there is no primary region on regionserver, -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24624) Optimize table.jsp code
[ https://issues.apache.org/jira/browse/HBASE-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24624: Description: # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set the wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, remove it and let the page always show the replica id of regions. This can help to keep the code simple and the UI style union. # When there is no primary region on regionserver, Show 0 instead of null was: # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set the wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, remove it and let the page always show the replica id of regions. This can help to keep the code simple and the UI style union. # Show 0 not null, when there is no primary region on regionserver, > Optimize table.jsp code > --- > > Key: HBASE-24624 > URL: https://issues.apache.org/jira/browse/HBASE-24624 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > > # Rename buildRegionServerLink to buildRegionLink, for it returns the link of > region, not regionserver. > # Add buildRegionDeployedServerTag and moreRegionsToRender, this two > function can be used everywhere in table.jsp, and with them we can reduce a > lot of same code. > # Fix bug which locality stats tab can not sort. This is because we set the > wrong id for locality stats tab. > # We use too much "if (withReplica)..." statements, remove it and let the > page always show the replica id of regions. This can help to keep the code > simple and the UI style union. > # When there is no primary region on regionserver, Show 0 instead of null -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24624) Optimize table.jsp code
[ https://issues.apache.org/jira/browse/HBASE-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24624: Description: # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set the wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, remove it and let the page always show the replica id of regions. This can help to keep the code simple and the UI style union. # When there is no primary region on regionserver, show 0 instead of null was: # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set the wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, remove it and let the page always show the replica id of regions. This can help to keep the code simple and the UI style union. # When there is no primary region on regionserver, Show 0 instead of null > Optimize table.jsp code > --- > > Key: HBASE-24624 > URL: https://issues.apache.org/jira/browse/HBASE-24624 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > > # Rename buildRegionServerLink to buildRegionLink, for it returns the link of > region, not regionserver. > # Add buildRegionDeployedServerTag and moreRegionsToRender, this two > function can be used everywhere in table.jsp, and with them we can reduce a > lot of same code. > # Fix bug which locality stats tab can not sort. This is because we set the > wrong id for locality stats tab. > # We use too much "if (withReplica)..." statements, remove it and let the > page always show the replica id of regions. This can help to keep the code > simple and the UI style union. > # When there is no primary region on regionserver, show 0 instead of null -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24624) Optimize table.jsp code
[ https://issues.apache.org/jira/browse/HBASE-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] song XinCun updated HBASE-24624: Description: # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, remove it and let the page always show the replica id of regions. This can help to keep the code simple and the UI style union. # When there is no primary region on regionserver, show 0 instead of null was: # Rename buildRegionServerLink to buildRegionLink, for it returns the link of region, not regionserver. # Add buildRegionDeployedServerTag and moreRegionsToRender, this two function can be used everywhere in table.jsp, and with them we can reduce a lot of same code. # Fix bug which locality stats tab can not sort. This is because we set the wrong id for locality stats tab. # We use too much "if (withReplica)..." statements, remove it and let the page always show the replica id of regions. This can help to keep the code simple and the UI style union. # When there is no primary region on regionserver, show 0 instead of null > Optimize table.jsp code > --- > > Key: HBASE-24624 > URL: https://issues.apache.org/jira/browse/HBASE-24624 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 3.0.0-alpha-1 >Reporter: song XinCun >Assignee: song XinCun >Priority: Minor > > # Rename buildRegionServerLink to buildRegionLink, for it returns the link of > region, not regionserver. > # Add buildRegionDeployedServerTag and moreRegionsToRender, this two > function can be used everywhere in table.jsp, and with them we can reduce a > lot of same code. > # Fix bug which locality stats tab can not sort. This is because we set > wrong id for locality stats tab. > # We use too much "if (withReplica)..." statements, remove it and let the > page always show the replica id of regions. This can help to keep the code > simple and the UI style union. > # When there is no primary region on regionserver, show 0 instead of null -- This message was sent by Atlassian Jira (v8.3.4#803005)
