[jira] [Updated] (HBASE-12203) Remove Master from table status query path.
[ https://issues.apache.org/jira/browse/HBASE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12203: -- Fix Version/s: (was: 1.0.0) Remove Master from table status query path. --- Key: HBASE-12203 URL: https://issues.apache.org/jira/browse/HBASE-12203 Project: HBase Issue Type: Improvement Components: Client, master Affects Versions: 2.0.0 Reporter: Andrey Stepachev Priority: Minor Fix For: 2.0.0 With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a good cleanup, but we put additional (substantial) load on master. Some client requests use checks for table state (for example HBASE-12035). Thats is why patch was not back ported to branch1 (HBASE-11978) Lets replicate state back to zk, but as a mirror of table states. What can be done: 1. TableStateManager would push table state changes to zk 2. Return back ZKTableStateClientSideReader. Alternative way: 1. Move table statuses to separate table like namespaces 2. Issue statuses requests against this table Alternative way2: 1. Extend RS api with getTableState() call 2. Each RS will be able to cache table states 3. Clients will call RS instead of master or zk -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12203) Remove Master from table status query path.
[ https://issues.apache.org/jira/browse/HBASE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12203: - Priority: Minor (was: Major) Remove Master from table status query path. --- Key: HBASE-12203 URL: https://issues.apache.org/jira/browse/HBASE-12203 Project: HBase Issue Type: Improvement Components: Client, master Affects Versions: 2.0.0 Reporter: Andrey Stepachev Priority: Minor Fix For: 1.0.0, 2.0.0 With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a good cleanup, but we put additional (substantial) load on master. Some client requests use checks for table state (for example HBASE-12035). Thats is why patch was not back ported to branch1 (HBASE-11978) Lets replicate state back to zk, but as a mirror of table states. What can be done: 1. TableStateManager would push table state changes to zk 2. Return back ZKTableStateClientSideReader. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12203) Remove Master from table status query path.
[ https://issues.apache.org/jira/browse/HBASE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12203: - Description: With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a good cleanup, but we put additional (substantial) load on master. Some client requests use checks for table state (for example HBASE-12035). Thats is why patch was not back ported to branch1 (HBASE-11978) Lets replicate state back to zk, but as a mirror of table states. What can be done: 1. TableStateManager would push table state changes to zk 2. Return back ZKTableStateClientSideReader. Alternative way: 1. Move table statuses to separate table like namespaces 2. Issue statuses requests against this table was: With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a good cleanup, but we put additional (substantial) load on master. Some client requests use checks for table state (for example HBASE-12035). Thats is why patch was not back ported to branch1 (HBASE-11978) Lets replicate state back to zk, but as a mirror of table states. What can be done: 1. TableStateManager would push table state changes to zk 2. Return back ZKTableStateClientSideReader. Remove Master from table status query path. --- Key: HBASE-12203 URL: https://issues.apache.org/jira/browse/HBASE-12203 Project: HBase Issue Type: Improvement Components: Client, master Affects Versions: 2.0.0 Reporter: Andrey Stepachev Priority: Minor Fix For: 1.0.0, 2.0.0 With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a good cleanup, but we put additional (substantial) load on master. Some client requests use checks for table state (for example HBASE-12035). Thats is why patch was not back ported to branch1 (HBASE-11978) Lets replicate state back to zk, but as a mirror of table states. What can be done: 1. TableStateManager would push table state changes to zk 2. Return back ZKTableStateClientSideReader. Alternative way: 1. Move table statuses to separate table like namespaces 2. Issue statuses requests against this table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12203) Remove Master from table status query path.
[ https://issues.apache.org/jira/browse/HBASE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12203: - Description: With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a good cleanup, but we put additional (substantial) load on master. Some client requests use checks for table state (for example HBASE-12035). Thats is why patch was not back ported to branch1 (HBASE-11978) Lets replicate state back to zk, but as a mirror of table states. What can be done: 1. TableStateManager would push table state changes to zk 2. Return back ZKTableStateClientSideReader. Alternative way: 1. Move table statuses to separate table like namespaces 2. Issue statuses requests against this table Alternative way2: 1. Extend RS api with getTableState() call 2. Each RS will be able to cache table states 3. Clients will call RS instead of master or zk was: With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a good cleanup, but we put additional (substantial) load on master. Some client requests use checks for table state (for example HBASE-12035). Thats is why patch was not back ported to branch1 (HBASE-11978) Lets replicate state back to zk, but as a mirror of table states. What can be done: 1. TableStateManager would push table state changes to zk 2. Return back ZKTableStateClientSideReader. Alternative way: 1. Move table statuses to separate table like namespaces 2. Issue statuses requests against this table Remove Master from table status query path. --- Key: HBASE-12203 URL: https://issues.apache.org/jira/browse/HBASE-12203 Project: HBase Issue Type: Improvement Components: Client, master Affects Versions: 2.0.0 Reporter: Andrey Stepachev Priority: Minor Fix For: 1.0.0, 2.0.0 With patch HBASE-7767 we moved table statuses from ZK to HDFS. That was a good cleanup, but we put additional (substantial) load on master. Some client requests use checks for table state (for example HBASE-12035). Thats is why patch was not back ported to branch1 (HBASE-11978) Lets replicate state back to zk, but as a mirror of table states. What can be done: 1. TableStateManager would push table state changes to zk 2. Return back ZKTableStateClientSideReader. Alternative way: 1. Move table statuses to separate table like namespaces 2. Issue statuses requests against this table Alternative way2: 1. Extend RS api with getTableState() call 2. Each RS will be able to cache table states 3. Clients will call RS instead of master or zk -- This message was sent by Atlassian JIRA (v6.3.4#6332)
