kocolosk commented on issue #3603:
URL: https://github.com/apache/couchdb/issues/3603#issuecomment-906754022


   Intriguing! I think I figured it out. The difference is that the `couchdb:3` 
container is configured without any node name and is not running in distributed 
mode. In that mode trying to monitor the remote Clouseau process triggers a 
badarg error:
   
   ```
   # /opt/couchdb/erts-9.3.3.14/bin/erl -boot 
/opt/couchdb/releases/3.1.1/start_clean
   Erlang/OTP 20 [erts-9.3.3.14] [source] [64-bit] [smp:8:8] [ds:8:8:10] 
[async-threads:10] [hipe] [kernel-poll:false]
   
   Eshell V9.3.3.14  (abort with ^G)
   1> erlang:monitor(process, {main, '[email protected]'}).
   ** exception error: bad argument
        in function  monitor/2
           called as monitor(process,{main,'[email protected]'})
   ```
   
   whereas in dev mode we are running a CouchDB Erlang node and the behavior 
changes to deliver a 'DOWN` message to the mailbox:
   
   ```
   # /opt/couchdb/erts-9.3.3.14/bin/erl -boot 
/opt/couchdb/releases/3.1.1/start_clean -name [email protected]
   Erlang/OTP 20 [erts-9.3.3.14] [source] [64-bit] [smp:8:8] [ds:8:8:10] 
[async-threads:10] [hipe] [kernel-poll:false]
   
   Eshell V9.3.3.14  (abort with ^G)
   ([email protected])1> erlang:monitor(process, {main, '[email protected]'}).
   #Ref<0.2127152124.2865758209.248364>
   ([email protected])2> receive M -> M end.
   {'DOWN',#Ref<0.2127152124.2865758209.248364>,process,
           {main,'[email protected]'},
           noconnection}
   ([email protected])3> 
   ```
   
   Not sure offhand what the right fix is here. Seems like we ought to be able 
to run gracefully without the Erlang distribution, although it's news to me 
that the Docker image is configured that way.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to