How do I log from my Python Spark script
I have a Python Spark program which I run with spark-submit
. I want to put logging statements in it.
logging.info("This is an informative message.")
logging.debug("This is a debug message.")
I want to use the same logger that Spark is using so that the log messages come out in the same format and the level is controlled by the same configuration files. How do I do this?
I've tried putting the logging
statements in the code and starting out with a logging.getLogger()
. In both cases I see Spark's log messages but not mine. I've been looking at the Python logging documentation, but haven't been able to figure it out from there.
Not sure if this is something specific to scripts submitted to Spark or just me not understanding how logging works.
Solution 1:
You can get the logger from the SparkContext object:
log4jLogger = sc._jvm.org.apache.log4j
LOGGER = log4jLogger.LogManager.getLogger(__name__)
LOGGER.info("pyspark script logger initialized")
Solution 2:
You need to get the logger for spark itself, by default getLogger()
will return the logger for you own module. Try something like:
logger = logging.getLogger('py4j')
logger.info("My test info statement")
It might also be 'pyspark'
instead of 'py4j'
.
In case the function that you use in your spark program (and which does some logging) is defined in the same module as the main function it will give some serialization error.
This is explained here and an example by the same person is given here
I also tested this on spark 1.3.1
EDIT:
To change logging from STDERR
to STDOUT
you will have to remove the current StreamHandler
and add a new one.
Find the existing Stream Handler (This line can be removed when finished)
print(logger.handlers)
# will look like [<logging.StreamHandler object at 0x7fd8f4b00208>]
There will probably only be a single one, but if not you will have to update position.
logger.removeHandler(logger.handlers[0])
Add new handler for sys.stdout
import sys # Put at top if not already there
sh = logging.StreamHandler(sys.stdout)
sh.setLevel(logging.DEBUG)
logger.addHandler(sh)
Solution 3:
We needed to log from the executors, not from the driver node. So we did the following:
We created a
/etc/rsyslog.d/spark.conf
on all of the nodes (using a Bootstrap method with Amazon Elastic Map Reduceso that the Core nodes forwarded syslog
local1` messages to the master node.On the Master node, we enabled the UDP and TCP syslog listeners, and we set it up so that all
local
messages got logged to/var/log/local1.log
.We created a Python
logging
module Syslog logger in our map function.Now we can log with
logging.info()
. ...
One of the things we discovered is that the same partition is being processed simultaneously on multiple executors. Apparently Spark does this all the time, when it has extra resources. This handles the case when an executor is mysteriously delayed or fails.
Logging in the map
functions has taught us a lot about how Spark works.