AFAICT, the metrics from titan is pretty coarse and not useful. I initially
thought it would be useful to know the behavior but its junk IMO.

On Mon, Apr 27, 2015 at 2:05 AM, pavan kumar kolamuri (JIRA) <
[email protected]> wrote:

>
>     [
> https://issues.apache.org/jira/browse/FALCON-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513759#comment-14513759
> ]
>
> pavan kumar kolamuri commented on FALCON-676:
> ---------------------------------------------
>
> [~ajayyadava] I have applied this patch and run , titan metrics are coming
> in both application.log and metric.log , please check if i am missing
> something and if possible we should avoid this since titan metric logs are
> huge.
>
> > Enable metrics for Titan
> > ------------------------
> >
> >                 Key: FALCON-676
> >                 URL: https://issues.apache.org/jira/browse/FALCON-676
> >             Project: Falcon
> >          Issue Type: Sub-task
> >          Components: metrics
> >    Affects Versions: 0.6
> >            Reporter: Venkatesh Seetharam
> >            Assignee: Ajay Yadava
> >             Fix For: 0.7
> >
> >         Attachments: FALCON-676-v1.patch, FALCON-676-v2.patch,
> FALCON-676-v3.patch, FALCON-676.patch
> >
> >
> > http://s3.thinkaurelius.com/docs/titan/0.5.0/monitoring.html
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>



-- 
Regards,
Venkatesh

“Perfection (in design) is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.”
- Antoine de Saint-Exupéry

Reply via email to