[
https://issues.apache.org/jira/browse/HBASE-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-3660:
-------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Applied branch and trunk. Thanks for review Cosmin (I took a look for other
places that could have SocketException and this is what I came up with but
yeah, do other researching in another issue -- good on you boss)
> HMaster will exit when starting with stale data in cached locations such as
> -ROOT- or .META.
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-3660
> URL: https://issues.apache.org/jira/browse/HBASE-3660
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Affects Versions: 0.90.1
> Reporter: Cosmin Lehene
> Priority: Critical
> Fix For: 0.90.2
>
> Attachments: 3660.txt, HBASE-3660.patch
>
>
> later edit: I've mixed up two issues here. The main problem is that a client
> (that could be HMaster) will read stale data from -ROOT- or .META. and not
> deal correctly with the raised exceptions.
> I've noticed this when the IP on my machine changed (it's even easier to
> detect when LZO doesn't work)
> Master loads .META. successfully and then starts assigning regions.
> However LZO doesn't work so HRegionServer can't open the regions.
> A client attempts to get data from a table so it reads the location from
> .META. but goes to a totally different server (the old value in .META.)
> This could happen without the LZO story too.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
