[
https://issues.apache.org/jira/browse/HBASE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gautam Sampathkumar updated HBASE-1948:
---------------------------------------
Stack,
I agree that we can just ignore the clustered case for now and just
focus on the simple single machine test case. I suspect that whatever is the
fix for the single machine mode should fix the clustered situation as well.
I think it's a matter of adding this functionality :
hbase regionservers request a refreshed set of block location information from
hadoop dfs (assuming that this is a simple call to get the info) when they
start up, and update their internal points to the data.
> updates to existing tables do not get reflected after a complete HBase +
> Hadoop + Zookeeper restart
> ---------------------------------------------------------------------------------------------------
>
> Key: HBASE-1948
> URL: https://issues.apache.org/jira/browse/HBASE-1948
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.1
> Environment: ubuntu 9.04
> hadoop 0.20.1 (single machine mode)
> hbase 0.20.0 (pseudo-distributed mode i.e. using HDFS on a single machine)
> zookeeper 3.2.1
> Reporter: Gautam Sampathkumar
> Attachments: hbase-site.xml, hdfs-site.xml
>
>
> I have an existing hbase table with data in it. When I restart hadoop, hbase
> and zookeeper, I am able to read all of the data that existed in the table
> prior to the restart. However when I write data to the table, it does not get
> reflected.
> When I do a disable <table> and then an enable <table> on an hbase shell. The
> data that was written to the table now appears and the table is up to date.
> However, even after this my thrift client still sees the old data and not the
> updated values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
