Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # dev >> table.offline behavior change in 1.6.0


Copy link to this message
-
Re: table.offline behavior change in 1.6.0
On Wed, Dec 4, 2013 at 3:21 PM, John Vines <[EMAIL PROTECTED]> wrote:

>  I disagree. The 1.5.0 code path waits by default. Offline() calls
> doTableOperation, which calls doTableOperation with wait=true, which
> causes waitForTableOperation to trigger. Unless there's weird casing
> for waitForTableOperation, of which there does not appear to be, it will
> wait.
>

In 1.5 and 1.4 its only waiting for the master to change the table state in
zookeeper.  Its not waiting for all of the tablets to go offline.   Take a
look at o.a.a.s.master.tableOps.ChangeTableState, this is what gets
executed on the master.

1.6 adds the ability to wait for all tablets to go offline.
>
>
> On Wed, Dec 4, 2013 at 3:10 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>
>>
>>
>>
>> On Wed, Dec 4, 2013 at 2:33 PM, John Vines <[EMAIL PROTECTED]> wrote:
>>
>>> It has recently come to my attention that the default behavior for
>>> TableOperations.offline(table) to immediately return. There is now an
>>> additional command which offers a wait flag like the old behavior.
>>> However,
>>> I'm really not comfortable changing API behavior between major releases
>>> like that. What is everyone else's thoughts on this?
>>>
>>
>> The old behavior did not wait.  The API preserves the old behavior.
>>
>>
>>
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB