The downside of that isolation is that the storage plugin configuration of the primary cluster is lost.
If you connect DIRECTLY to the drill-bit rather than via zookeeper, then that drill-bit will be the foreman of your queries. For small data sets, the foreman will not involve any other drill-bits. — David On Jun 5, 2015, at 9:18 AM, Jim Bates <jba...@maprtech.com> wrote: > Thinking along the same lines. I'm in the middle of testing that now. I'll > let you know. > > On Fri, Jun 5, 2015 at 11:16 AM, Andries Engelbrecht < > aengelbre...@maprtech.com> wrote: > >> Only option I can think of now is to take a single drillbit out of the >> cluster and spin it up as it’s own drill cluster. >> SHutdown drillbit >> edit drill-override.conf with new cluster id >> Bring it up as it’s own cluster >> >> I have not tested it myself though, and also your big cluster is missing a >> drillbit then. >> >> Hopefully someone has a more elegant solution. >> >> —Andries >> >> >> On Jun 5, 2015, at 7:31 AM, Jim Bates <jba...@maprtech.com> wrote: >> >>> Is there a way to re-write the plan for a query and force it to use only >> a >>> specific drill bit for troubleshooting purposes? They way I would >> normally >>> do this is to just shut all the drill bits down but one. As drill gets >>> placed more and more into a production environment this becomes >> problematic >>> and I find disrupting drill to look a specific issue is a nogo. >>> >>> Anyone done something like this? >> >>
