On Tue, May 17, 2011 at 4:25 PM, Vidhyashankar Venkataraman <[email protected]> wrote: > 2. The master getting stuck unable to delete a WAL (I have seen this before > on this forum and a related JIRA on this one): We had worked around by > manually deleting a WAL. But during times when the master crashed during > table creation (with split key boundaries), the node that took over next as > the master (failover) started getting stuck for around 25% of the cluster. I > had to wipe out all the logs so that the master could start up right. > > But even then, the regionservers which had suffered the log issue couldn't > recognize the failed over master. (Is this something that has been observed > before?) >
Please file an issue w/ log samples Vidhya. > 3. createTableAsync with incorrect split keys: By mistake, I had some > duplicate keys in the split key byte array while calling the createTableAsync > function. The master crashed throwing a KeeperException (thanks to the > duplicate keys I guess?) > Do you have the exception Vidhya? I'd think it'd be easy to add a check of the keys passed before running the create. > Also, can you let me know why createTableAsync blocks for some time and > throws a socket timeout exception when I try creating a table with a large > number of regions? > It shouldn't be blocking. It should return. Is this hbase-3744 fixed in 0.90.3? St.Ack
