Re: [PR] [SPARK-29397][core] Extend plugin interface to include the driver. [spark]

["Madhukar525722 (via GitHub)" <gi...@apache.org>]

Madhukar525722 commented on PR #26170:
URL: https://github.com/apache/spark/pull/26170#issuecomment-2819455084

   Hi @vanzin @HyukjinKwon 
   There is a statement
   When a Spark plugin provides an executor plugin, this method will be called during the initialization of the executor process. It will block executor initialization until it returns.
   
   When I see the implementation of Executor.scala , I think it gets started and send heartbeater.start(), then only plugin gets loaded. Which implies that Executor instance is getting started and sending acknowledgement to the driver, then executor plugin init is getting triggered.
   Could you please confirm and rectify the statement, and could you please guide me through to approach my use case, where I want to intercept the spark.executor.memory conf provided by the user and modify it.


-- 
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: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org