<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [ERROR] Worker (pid:11) was sent code 132 When deploying a Custom Model in serving in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/error-worker-pid-11-was-sent-code-132-when-deploying-a-custom/m-p/128657#M4222</link>
    <description>&lt;P&gt;Great observation! The difference between Using worker: sync and Using worker: gevent typically refers to the worker class used by Gunicorn, the web server behind many MLflow model deployments (like in Databricks model serving or other MLflow-compatible environments).&lt;/P&gt;&lt;P&gt;The error:&lt;/P&gt;&lt;P&gt;[ERROR] Worker (pid:11) was sent code 132&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;...often indicates a crash during model loading or execution, and differences in worker type (sync vs gevent) can affect how threads and concurrency are handled — which matters a lot when you're using libraries like ANNOY, which might rely on file descriptors or multithreading.&lt;/P&gt;&lt;P&gt;- Solution: Force the model serving to use the gevent worker&lt;/P&gt;&lt;P&gt;MLflow doesn't let you directly set the Gunicorn worker type via the Python API (e.g., mlflow.models.serve) or Databricks model serving configuration.&lt;/P&gt;&lt;P&gt;However, if you're serving locally or managing the model server yourself (e.g., using MLflow + Docker), you can manually specify the worker type using Gunicorn flags.&lt;/P&gt;&lt;P&gt;Example (Manual MLflow Serve):&lt;BR /&gt;gunicorn -b 0.0.0.0:5000 -w 4 --worker-class gevent mlflow.pyfunc.scoring_server.wsgi:app&lt;/P&gt;&lt;P&gt;This way you can serve your MLflow model with gevent workers explicitly.&lt;/P&gt;</description>
    <pubDate>Sun, 17 Aug 2025 13:48:16 GMT</pubDate>
    <dc:creator>WiliamRosa</dc:creator>
    <dc:date>2025-08-17T13:48:16Z</dc:date>
    <item>
      <title>[ERROR] Worker (pid:11) was sent code 132 When deploying a Custom Model in serving</title>
      <link>https://community.databricks.com/t5/machine-learning/error-worker-pid-11-was-sent-code-132-when-deploying-a-custom/m-p/126804#M4173</link>
      <description>&lt;P&gt;Hi, I've been developing a custom model with &lt;SPAN&gt;mlflow&lt;/SPAN&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;pyfunc&lt;/SPAN&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;PythonModel. Among other libs, I use ANNOY. While trying to serve the model as an endpoint in "serving", After a few fixes my model worked fine as well the endpoin call.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Altough, I tried update it, no big deal, but i didn's start the serving point again, it keeps showing the error:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;[ERROR] Worker (pid:11) was sent code 132&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It tries to change worker e nothing happens. Even if I backup the older model, that works, the same error. AFter many changes and testing, I notice that ine thing is different from the working one from the fails.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Fails have : "Using worker: sync"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Working has "Using worker: gevent"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;How to I specifiy to use "gevent" working when starting an serving.??&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;thank you&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 13:29:48 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/error-worker-pid-11-was-sent-code-132-when-deploying-a-custom/m-p/126804#M4173</guid>
      <dc:creator>Junqueira</dc:creator>
      <dc:date>2025-07-29T13:29:48Z</dc:date>
    </item>
    <item>
      <title>Re: [ERROR] Worker (pid:11) was sent code 132 When deploying a Custom Model in serving</title>
      <link>https://community.databricks.com/t5/machine-learning/error-worker-pid-11-was-sent-code-132-when-deploying-a-custom/m-p/128657#M4222</link>
      <description>&lt;P&gt;Great observation! The difference between Using worker: sync and Using worker: gevent typically refers to the worker class used by Gunicorn, the web server behind many MLflow model deployments (like in Databricks model serving or other MLflow-compatible environments).&lt;/P&gt;&lt;P&gt;The error:&lt;/P&gt;&lt;P&gt;[ERROR] Worker (pid:11) was sent code 132&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;...often indicates a crash during model loading or execution, and differences in worker type (sync vs gevent) can affect how threads and concurrency are handled — which matters a lot when you're using libraries like ANNOY, which might rely on file descriptors or multithreading.&lt;/P&gt;&lt;P&gt;- Solution: Force the model serving to use the gevent worker&lt;/P&gt;&lt;P&gt;MLflow doesn't let you directly set the Gunicorn worker type via the Python API (e.g., mlflow.models.serve) or Databricks model serving configuration.&lt;/P&gt;&lt;P&gt;However, if you're serving locally or managing the model server yourself (e.g., using MLflow + Docker), you can manually specify the worker type using Gunicorn flags.&lt;/P&gt;&lt;P&gt;Example (Manual MLflow Serve):&lt;BR /&gt;gunicorn -b 0.0.0.0:5000 -w 4 --worker-class gevent mlflow.pyfunc.scoring_server.wsgi:app&lt;/P&gt;&lt;P&gt;This way you can serve your MLflow model with gevent workers explicitly.&lt;/P&gt;</description>
      <pubDate>Sun, 17 Aug 2025 13:48:16 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/error-worker-pid-11-was-sent-code-132-when-deploying-a-custom/m-p/128657#M4222</guid>
      <dc:creator>WiliamRosa</dc:creator>
      <dc:date>2025-08-17T13:48:16Z</dc:date>
    </item>
  </channel>
</rss>

