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 Plain View
HBase >> mail # dev >> @Test(timeout = 1000)


+
Nicolas Liochon 2013-04-08, 16:10
+
Ted Yu 2013-04-08, 16:19
+
Enis Söztutar 2013-04-09, 03:06
+
Nicolas Liochon 2013-04-09, 07:49
Copy link to this message
-
Re: @Test(timeout = 1000)
Minor correction: the JIRA number should be 8303

Cheers

On Apr 9, 2013, at 12:49 AM, Nicolas Liochon <[EMAIL PROTECTED]> wrote:

> I've created HBASE-8003 and bumped the tests I found with a timeout
> inferior to 30s to 60s.
> With this, if a timeout occurs, we know it's very likely to be the test or
> hbase, not the env :-)
>
>
>
> On Tue, Apr 9, 2013 at 5:06 AM, Enis Söztutar <[EMAIL PROTECTED]> wrote:
>
>> +1 on increasing the timeouts for those to at least 10sec.
>>
>>
>> On Mon, Apr 8, 2013 at 9:19 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
>>
>>> In trunk, I found 4 tests with such annotation.
>>> They're all small tests.
>>>
>>> I guess the intention was that GC wouldn't be long in a test where
>> cluster
>>> is not spun up.
>>>
>>> I think increasing the timeout should be fine.
>>>
>>> Cheers
>>>
>>> On Mon, Apr 8, 2013 at 9:10 AM, Nicolas Liochon <[EMAIL PROTECTED]>
>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I see some tests with a test timeout of 1s.
>>>> The problem with this is that it may happen with a GC or anything on
>> the
>>>> server.
>>>>
>>>> Any issue to decide to have a minimum of 60s for such settings?
>>>>
>>>> Thanks,
>>>>
>>>> Nicolas
>>
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