Thanks Dave,
Yes, we are using Accumulo 2.0.1.
The workaround `--address accumulo_tracer`works perfectly in my local
development environment.
We can see compaction trace messages in the trace table.
Thanks again Christopher!
We are deploying in AWS to do final testing...
Cheers!...
If the version being used is 2.0.1, then that version is still affected by
the bug you mention. However, since TraceServer never used AbstractServer,
it was not affected and should still work fine.
On Fri, Jul 29, 2022 at 3:05 PM Dave Marion wrote:
> Ok, I wasn't sure what version was being
Ok, I wasn't sure what version was being used here. I saw a reference to
2.0.1 in an earlier email.
On Fri, Jul 29, 2022 at 3:03 PM Christopher wrote:
> That was a bug in the new AbstractServer class in 2.x. I don't think it
> ever affected 1.x
> I checked the 1.10 code and it wouldn't affect
That was a bug in the new AbstractServer class in 2.x. I don't think it
ever affected 1.x
I checked the 1.10 code and it wouldn't affect the tracer server. `-a`
should still work fine there.
On Fri, Jul 29, 2022 at 3:00 PM Dave Marion wrote:
> https://github.com/apache/accumulo/pull/2119 fixed
https://github.com/apache/accumulo/pull/2119 fixed a bug in 2.1 where the
-a argument was not correctly setting the hostname. It looks like 2.0.1 is
affected by this too.
On Fri, Jul 29, 2022 at 12:57 PM Christopher wrote:
> The tracer should be advertising its own address in ZK. By default,
The tracer should be advertising its own address in ZK. By default, the
server listens on `0.0.0.0`, unless `-a` or `--address` is specified on the
command-line when it is started. Most server types use a utility class that
will use `InetAddress.getLocalHost().getCanonicalHostName()` for the
Nice,
Turn on debug really help.
2022-07-29 12:12:14,235 [tracer.ZooTraceClient] DEBUG: Scanning trace
hosts in zookeeper: /tracers
2022-07-29 12:12:14,240 [tracer.ZooTraceClient] DEBUG: Trace hosts:
[0.0.0.0:12234, 0.0.0.0:12234]
2022-07-29 12:12:14,240 [tracer.ZooTraceClient] DEBUG:
