How are sandboxes used in Azure Data Explorer?
A sandbox is only used for a single run, isn’t shared across multiple runs, and is disposed of once that run completes. Sandboxes are lazily initialized on a node, the first time a query requires a sandbox for its execution. This means that the first execution of a plugin that uses sandboxes on a node will include a short warm-up period.
How are sandboxes used in a query operator?
A sandboxed query operator may use one or more sandboxes for its execution. A sandbox is only used for a single run, isn’t shared across multiple runs, and is disposed of once that run completes. Sandboxes are lazily initialized on a node, the first time a query requires a sandbox for its execution.
How big does a sandbox need to be?
The required packages (images) for running the sandboxes are deployed to each of the Data Engine’s nodes, and require dedicated SSD space to run. The estimated size is 20 GB, that is roughly 2.5% the SSD capacity of a D14_v2 VM, for example, or 0.7% the SSD capacity of a L16_v1 VM.
Why is sandbox blocked from spawning child processes?
Child processes: The sandbox is blocked from spawning child processes. The resources used with sandbox depend not only on the size of the data being processed as part of the request, but also on the logic that runs in the sandbox, and the implementation of libraries being used by it.
What kind of Sandbox is used in Kusto?
Kusto’s Data Engine service can run sandboxes for specific flows that need secure isolation. Examples of these flows are user-defined scripts that run using the Python plugin or the R plugin. To run these sandboxes, Kusto uses an evolved version of Microsoft’s Drawbridge project.
How to run an executable file in a sandbox?
Copy an executable file (and any other files needed to run the application) from the host and paste them into the Windows Sandbox window. Run the executable file or installer inside the sandbox. When you’re finished experimenting, close the sandbox.