Hi Alex,
Right, I can add Mesos sources to include path... But I cannot inherit from
MesosAllocator since it has private constructor. I will think about this,
maybe I really can reuse existing allocator implementation w/o subclassing.
I plan to send all protobufs which come with specific event to
The MesosAllocator class is just a wrapper for any actor-based allocator. I
think you actually want to subclass HierarchicalAllocatorProcess and pass
it as template parameter to MesosAllocator. But consider preferring
composition over inheritance
Hi Dariia,
interesting! I think you can actually subclass the Hierarchical allocator,
but you need access to Mesos sources (quick check of your code hints you
need it nevertheless since you build unbundled Mesos).
What protobufs do you plan to send to your Go server? Allocator maintains a
list
Hi Alex,
My task was to create allocator which produces information about all
protobufs it receives to Kafka (prior to actual resources allocation). Here
is the implementation: https://github.com/stealthly/alligator. I had to
copy-paste Hierarchical allocator from Mesos sources since
Dariia,
what Mesos version are you using? The ability to write and and use custom
allocator modules without hacking on Mesos source code has just landed in
Mesos (means will be available in 0.23 release) with docs being updated
right now (here https://reviews.apache.org/r/34545/ is the RR request
Hello,
I need to write custom Allocation module, but I don't see a possibility to
load it dynamically using --modules command line argument.
This is the allocation module creation in master/main:
allocator::Allocator* allocator = new allocator::HierarchicalDRFAllocator();
(so it is just
