Please keep in mind we are talking about two issues here:
1) The short default interval time, and
2) the issue that the canary table regions might not be on all servers.
Anyone here that tried write sniffing on a current cluster with the
SLB and saw it work?
Best,
Lars
On Mon, Feb 6, 2017 at 1
Open an issue?
Enis
On Mon, Feb 6, 2017 at 9:39 AM, Stack wrote:
> On Sun, Feb 5, 2017 at 2:25 AM, Lars George wrote:
>
> > The next example is wrong too, claiming to show 60 secs, while it
> > shows 600 secs (the default value as well).
> >
> > The question is still, what is a good value for i
On Sun, Feb 5, 2017 at 2:25 AM, Lars George wrote:
> The next example is wrong too, claiming to show 60 secs, while it
> shows 600 secs (the default value as well).
>
> The question is still, what is a good value for intervals? Anyone here
> that uses the Canary that would like to chime in?
>
>
I
The next example is wrong too, claiming to show 60 secs, while it
shows 600 secs (the default value as well).
The question is still, what is a good value for intervals? Anyone here
that uses the Canary that would like to chime in?
On Sat, Feb 4, 2017 at 5:40 PM, Ted Yu wrote:
> Brief search on H
Brief search on HBASE-4393 didn't reveal why the interval was shortened.
If you read the first paragraph of:
http://hbase.apache.org/book.html#_run_canary_test_as_daemon_mode
possibly the reasoning was that canary would exit upon seeing some error
(the first time).
BTW There was a mismatch in th
Oh right, Ted. An earlier patch attached to the JIRA had 60 secs, the
last one has 6 secs. Am I reading this right? It hands 6000 into the
Thread.sleep() call, which takes millisecs. So that makes 6 secs
between checks, which seems super short, no? I might just dull here.
On Sat, Feb 4, 2017 at 5:
For the default interval , if you were looking at:
private static final long DEFAULT_INTERVAL = 6000;
The above was from:
HBASE-4393 Implement a canary monitoring program
which was integrated on Tue Apr 24 07:20:16 2012
FYI
On Sat, Feb 4, 2017 at 4:06 AM, Lars George wrote:
> Also, th
Also, the default interval used to be 60 secs, but is now 6 secs. Does
that make sense? Seems awfully short for a default, assuming you have
many regions or servers.
On Sat, Feb 4, 2017 at 11:54 AM, Lars George wrote:
> Hi,
>
> Looking at the Canary tool, it tries to ensure that all canary test
>
Hi,
Looking at the Canary tool, it tries to ensure that all canary test
table regions are spread across all region servers. If that is not the
case, it calls:
if (numberOfCoveredServers < numberOfServers) {
admin.balancer();
}
I doubt this will help with the StochasticLoadBalancer, which is kn
