batch-cluster
Advanced tools
Changelog
v2.2.0
/PID
option seemed to work downcased, but the docs say
to use uppercase, so I've updated it.(v2.1.2 is the same contents, but np
had a crashbug during publish)
Changelog
v2.1.1
end
for BatchProcess
, which may prevent very long-lived
consumers from sporadically leaking child processes on Mac and linux.Changelog
v2.1.0
Logger.trace
and moved logging related to per-task items down
to trace
, as heavy load and large request or response payloads could
overwhelm loggers. If you really want to see on-the-wire requests and results,
enable trace
in your debugger implementation. By default, the
ConsoleLogger
omits log messages with this level.Changelog
v2.0.0
BatchClusterObserver
with a simple EventEmitter API on
BatchCluster
to be more idiomatic with node's APImaxTaskErrorsPerProcess
parameter was removed)Rate
is simpler and more accurate now.Changelog
v1.11.0
BatchClusterObserver
for error and lifecycle monitoringChangelog
v1.10.0
timers.setInterval
. May address this
issue.
Thanks for the PR, Tim Fish!Changelog
v1.9.1
BatchProcess.end()
to use until()
rather than Promise.race
,
and always use kill(pid, forced)
after waiting the shutdown grace period
to prevent child process leaks.Changelog
v1.9.0
Logger.setLogger()
for debug, info, warning, and errors. debug
and
info
defaults to Node's
debuglog,
warn
and error
default to console.warn
and console.error
,
respectively.tsc
provides good lint coverage nowdelay
now allows
unrefing the
timer, which, in certain circumstances, could prevent node processes from
exiting gracefully until their timeouts expiredChangelog
v1.8.0