Re: [druid-dev] any reason to still keep overlord as separate node?
The only issue that I can think of is that in some (super large) clusters,
the coordinator and overlord can both be pretty demanding in terms of
memory and it helps for scalability to have them be separate. But this is
not the common case - most clusters are smaller or medium sized. So it
makes sense for the default to be combining them. I would support a patch
that changed the defaults and updated the docs accordingly.
Btw, since we are trying to migrate the dev mailing list to Apache, please
cross post this sort of thing with dev@xxxxxxxxxxxxxxxx, or even only post
to that list.
On Sat, Mar 31, 2018 at 9:42 AM, Prashant Deva <prashant.deva@xxxxxxxxx>
> i feel atleast the documentation should be written to assume that
> overlord+coordinator is the default config and separate overlord is the
> 'legacy' one.
> is there any actual issues holding keeping overlord as separate node?
> You received this message because you are subscribed to the Google Groups
> "Druid Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to druid-development+unsubscribe@xxxxxxxxxxxxxxxx.
> To post to this group, send email to druid-development@xxxxxxxxxxxxxxxx.
> To view this discussion on the web visit https://groups.google.com/d/ms
> For more options, visit https://groups.google.com/d/optout.