Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Mesos integration tests fail in the current master branch.
1. BindException on ManagerName
The root cause is MesosRemoteManager tries to initiate an instance of RemoteManager, but the ManagerName was already bounded by RemoteManagerFactory.
We need to fix this failure for 0.14 release. I'm attaching the error messages below.
Caused by: org.apache.reef.tang.exceptions.BindException: Attempt to re-bind named parameter org.apache.reef.wake.remote.RemoteConfiguration$ManagerName. Old value was [REEF_LAUNCHER] new value is [MESOS_EXECUTOR] at org.apache.reef.tang.implementation.java.InjectorImpl.bindVolatileParameterNoCopy(InjectorImpl.java:717) at org.apache.reef.tang.implementation.java.InjectorImpl.bindVolatileParameter(InjectorImpl.java:689) at org.apache.reef.wake.remote.DefaultRemoteManagerFactory.getInstance(DefaultRemoteManagerFactory.java:154) at org.apache.reef.runtime.mesos.util.MesosRemoteManager.<init>(MesosRemoteManager.java:44) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.apache.reef.tang.implementation.java.InjectorImpl.injectFromPlan(InjectorImpl.java:637) ... 15 more
- Related Issue:
REEF-991Remove deprecated RangeTcpPortProvider.Default and DefaultRemoteManagerImplementation constructor
2. Missing Runtime Identifier to Mesos Runtime.
- Related Issue:
REEF-983Add Runtime Identifier to the EvaluatorDescriptor
3. BindException on TempFileCreator.
- Related Issue:
REEF-1013C# Evaluator does not work on HDInsight
Attachments
Issue Links
- links to