Databases
StackOverflow2013
Postsdbo
POlogging while using parallel python
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POlogging while using parallel python
    primarykey
    data
    text
    <p>I'm using parallel python to execute a big function (<code>executePipeline</code>) multiple times. This function is also using multiprocessing (with the <code>multiprocessing</code> module).<br> I'm having some trouble to display correctly the logging messages on my console using the parallel python module. When I'm not using it, the logging messages are well displayed.</p> <p>Here is how it works. I have a server who is calling a worker every time it gets a request from client using: </p> <pre><code>job = self.server.job_server.submit(func = executeWorker, args = (config, ) ) </code></pre> <p>This function is execute from a new thread every time there is a new request from a client. Then the worker is calling the function <code>executePipeline</code> which is executing different processus using multiprocessing.</p> <p>The server a <code>SocketServer.TCPServer</code> I using threading. I set up a logger in my server as following using the root logger:</p> <pre><code>self.logger = logging.getLogger() self.logger.setLevel(logging.INFO) self.logger.addHandler(logging.StreamHandler() self.job_server = pp.Server(ncpus = 8) # for test self.jobs = [] </code></pre> <p>When I'm running my server i can only get the logging from the <code>executePipeline</code> but not from the child processes. Also I get the logging of the execute pipeline only at the end of the job not while is running.</p> <p>Also here is the worker code. The <code>"Executing pipeline with worker number "</code> is well displayed in my terminal</p> <pre><code>''' Setup logging ''' logger = logging.getLogger() logger.setLevel(logging.INFO) # worker name publicIP = socket.gethostbyname(socket.gethostname()) pid = os.getpid() workerID = unicode(str(publicIP) + ":" + str(pid)) logger.info( "Executing pipeline with worker {}".format(workerID)) res = executePipeline(config) markedScore = res["marker.score"] markedDetails = res["marker.detail"] results = {'marker.detail' : markedDetails , 'marker.score' : markedScore } return results </code></pre> <p>Is there a good way too get the logging working properly and see what the child process of my <code>executePipeline</code> function are sending back?</p> <p>Thanks for your help!</p> <p>Romanzo</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStaras
    1. USRomanzo Criminale
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POlogging while using parallel python
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POlogging while using parallel python
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POlogging while using parallel python
      1. USFrancesco
      1. VTFavorite
    1. COI think I could help, but I'm afraid I do not understand your question. I guess it boils down to "get the logger working in the subprocesses created by executePipeline", but you never showed the code of this function. Or did I get it wrong?
      singulars
      1. POlogging while using parallel python
      1. USE.Z.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload