fix crazy amounts of logging when coordinator loses leadership

There's a count that is also given.

On Mon, Nov 24, 2014 at 10:26 AM, xvrl <notifications@github.com> wrote:

> In
> server/src/main/java/io/druid/server/coordinator/helper/DruidCoordinatorRuleRunner.java:
>
> > @@ -99,13 +104,20 @@ public DruidCoordinatorRuntimeParams run(DruidCoordinatorRuntimeParams params)
> >        }
> >
> >        if (!foundMatchingRule) {
> > -        log.makeAlert("Unable to find a matching rule!")
> > -           .addData("dataSource", segment.getDataSource())
> > -           .addData("segment", segment.getIdentifier())
> > -           .emit();
> > +        if (segmentsWithMissingRules.size() < MAX_MISSING_RULES) {
> > +          segmentsWithMissingRules.add(segment.getIdentifier());
> > +        }
> > +        missingRules++;
>
> what happens when we exceed MAX_MISSING_RULES, do we just ignore those?
> Might make sense to indicate there are x more missing?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/metamx/druid/pull/899/files#r20810518>.
>