reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Inglis <>
Subject Re: Questions on REEF .NET Driver execution
Date Thu, 08 Mar 2018 20:04:46 GMT
Chenxi and I also talked offline -- and I wanted to reflect those
discussions to the dev alias.

So with his changes, he is using the HelloREEF example to test the Azure
batch runtime. If he changes HelloREEF back to local runtime, it works. So
its only when running with AzureBatch that this happens. Because this works
with the local runtime, I think we can rule out any missing dll
dependencies (as this change does add Azure SDK dlls to the project from
what I understand).

So the other possibility is the current working folder and how the paths
are handled -- maybe these are different for the runtime? Like local does
something different than what AzureBatch does with setting up the

Chenxi was going to look into this area.

On Thu, Mar 8, 2018 at 11:34 AM, Markus Weimer <> wrote:

> On Wed, Mar 7, 2018 at 11:08 PM, Chenxi Zhao <
>> wrote:
> > I notice that in .NET, Client is submitting to the java bridge classes.
> > E.g. YarnBootstrapREEFLauncher and LocalClient. In these launchers, they
> > are binding Driver configuration like ON_DRIVER_STARTED to .NET side
> driver
> > code through JNI call
> > reef/blob/master/lang/java/reef-bridge-java/src/main/
> java/org/apache/reef/
> > javabridge/
> >
> > Could some one help me understand how java bridge finds the dll that
> > contains those natives calls in local/Yarn runtime?
> >
> IIRC, we are asking YARN to launch `Driver.exe` which in turn depends on
> that DLL. That exe launches both the JVM and the CLR in-process and wires
> it all up. Doug would know better :)
> Markus

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message