edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Created] (QUARKS-189) Undesirable metric op injection
Date Thu, 26 May 2016 21:25:12 GMT
Dale LaBossiere created QUARKS-189:

             Summary: Undesirable metric op injection
                 Key: QUARKS-189
                 URL: https://issues.apache.org/jira/browse/QUARKS-189
             Project: Quarks
          Issue Type: Bug
          Components: Runtime
            Reporter: Dale LaBossiere
            Priority: Minor

Manually added CounterOp or RateMeter oplets result in desirable additional CounterOp (and
StreamScope) injection in the DevelopmentProvider.  e.g.

poll -> pipe(new CounterOp) /* Metrics.counter(stream) */ -> sink

results in

poll -> CounterOp -> StreamScope -> the-manual-CounterOp -> CounterOp -> StreamScope
-> sink

The injection code doesn't recognize that a counter op is already present - i.e., it treats
the manual CounterOp (or a manual RateMeter) as any other oplet, resulting in injecting a
CounterOp between it and the poll / sink.

As it turns out, the manual CounterOp/RateMeter is included in the "counter metrics" retrieved
by the Console and used for tuple-count info, so the additional injections aren't really needed...
and they look odd in the Console because you see a sequence of 5 small rectangles... because
the Console renders all metric ops as small rectangles whether they're injected or not.  Of
course, one of the StreamScope injections is needed.

This message was sent by Atlassian JIRA

View raw message