Increase Logging During Replication/Backup?

8 views
Skip to first unread message

Albert Law

unread,
Nov 18, 2014, 3:05:23 PM11/18/14
to hydr...@googlegroups.com
Hi All,

Is there a way I could increase logging during the replication and
backup stages of a job?

I've been looking at the code and can't easily see a way of doing it
without compiling a special version.

I'm hoping for some magical switch. :)


--
Albert Law
Lead Engineer - Data Acquisition
NewBrand
http://www.newbrandanalytics.com/

Ian Barfield

unread,
Nov 18, 2014, 4:53:19 PM11/18/14
to Albert Law, hydr...@googlegroups.com
By increase logging, do you mean adding additional logging statements? That cannot really be done without recompiling.

If you just mean changing the logging level, then sure you can do that via whatever logging framework you use. I think hydra-uber uses log4j2 by default. If you are trying to debug your unusual pauses, then stewart's "mesh.queue.debug" might be of interest. I think it just kinda sidesteps centralized logging control.

--
You received this message because you are subscribed to the Google Groups "hydra-oss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hydra-oss+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Albert Law

unread,
Nov 18, 2014, 5:11:10 PM11/18/14
to Ian Barfield, hydr...@googlegroups.com
Hi Ian,

Sure, log4j logging level setting is possible. I was hoping for a
job-base switch. In the past, I've used "verboseCheck=true" in a job
configuration.

Ian Barfield

unread,
Nov 18, 2014, 5:17:20 PM11/18/14
to Albert Law, hydr...@googlegroups.com
Most of the logging you are probably interested in occurs in Minion rather than the job task itself. Job config settings generally only affect the java "task" process, whereas all the backup and replica logic occurs in minion (or in wrapper scripts that minion creates).

That aside, newer versions of hydra allow for configuring logging settings from within job configs, but it isn't fully hammered out (mostly due to log4j2's configuration framework being awful).
Reply all
Reply to author
Forward
0 new messages