hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers
Date Wed, 15 Apr 2015 00:55:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495481#comment-14495481

Sangjin Lee commented on YARN-3051:

Yeah, that's another part where I'm a bit confused why we allow the same identifier across
clusters but not across apps. One step back, assume I develop the my framework YTS v2 integration,
due to the constraint of unique entity identifier across apps, I need to carefully define
entity identifier. By doing this, in most cases, the entity identifier is unique across cluster,
thought the assumption of single cluster may break something in the scenario of multiple clusters.
For example, in cluster_1, we will have application_1 and in cluster_2, we will have application_1
too. Having cluster_id can uniquely identify which application_1 it is. I'm just wondering
using cluster_1 to distinguish more than one entities is a rare case if we force users to
define unique entity identifiers across apps, and it sounds more like the cross cluster problem
of this framework. Thoughts?

I agree. In reality, entity id's will be designed such that they are unique (even across clusters).

Want to loop in [~gtCarrera9] and [~vrushalic]. Guys, would it be a non-trivial requirement
to enforce uniqueness of (cluster id, entity type, entity id) when it comes to storage?

> [Storage abstraction] Create backing storage read interface for ATS readers
> ---------------------------------------------------------------------------
>                 Key: YARN-3051
>                 URL: https://issues.apache.org/jira/browse/YARN-3051
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
>         Attachments: YARN-3051_temp.patch
> Per design in YARN-2928, create backing storage read interface that can be implemented
by multiple backing storage implementations.

This message was sent by Atlassian JIRA

View raw message