I put patch v5 on 3904. When user calls HBaseAdmin.createTableAsync() to create the table, HCM.isTableAvailable() is still vulnerable because currently it doesn't known the desired number of regions. We can add a new parameter to HCM.isTableAvailable() but 1. HConnection needs to be modified to accommodate this change 2. I personally think it is not intuitive.
Comments are welcome. On Fri, Jun 17, 2011 at 8:48 AM, Stack <[email protected]> wrote: > On Thu, Jun 16, 2011 at 5:43 PM, Ted Yu <[email protected]> wrote: > > HBA.createTable() takes too long to execute. Client receives Socket > timeout > > exception. > > This is because the create is running in the master? Can we have > waiting happen client-side over in HBaseAdmin? > > > Client calls HCM.isTableAvailable() which would report inaccurate status. > > I want to get other developers' opinion on whether HCM.isTableAvailable() > > should be accurate. > > > > Do we need two forms? An isTableAvailable that will looks at table > and if all regions are online reports true and then another > isTableAvailable where you know how many regions there are supposed to > be in the table and it returns true if that count of regions is open > and deployed? > > St.Ack >
