Efrat19 opened a new pull request, #27637:
URL: https://github.com/apache/flink/pull/27637

   ## What is the purpose of the change
   
   We are hitting docker build issues when multiple tests are building otel 
from a dockerfile in parallel. While it could be addressed by a resource lock, 
we realized we could actually use the prebuilt image with a mounted output 
directory instead of building from dockerfile. It is also the 
[recommended](https://docs.docker.com/engine/storage/drivers/\#copying-makes-containers-efficient)
 approach by docker to use volumes for writable locations, to avoid 
copy-on-write bottlenecks 
   
   
   ## Brief change log
   
   - Prebuilt otel image with a mounted output directory instead of building 
from dockerfile.
   
   ## Verifying this change
   
   Please make sure both new and modified tests in this PR follow [the 
conventions for tests defined in our code quality 
guide](https://flink.apache.org/how-to-contribute/code-style-and-quality-common/#7-testing).
   
   *(Please pick either of the following options)*
   
   This change is already covered by existing tests, such as:
    - `org.apache.flink.metrics.otel.OpenTelemetryMetricReporterITCase`
    - `org.apache.flink.traces.otel.OpenTelemetryTraceReporterITCase`
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no 
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


-- 
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