From yarn-issues-return-158024-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Nov 16 08:03:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8B949180670 for ; Fri, 16 Nov 2018 08:03:04 +0100 (CET) Received: (qmail 77701 invoked by uid 500); 16 Nov 2018 07:03:03 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 77680 invoked by uid 99); 16 Nov 2018 07:03:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Nov 2018 07:03:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3B780C05DD for ; Fri, 16 Nov 2018 07:03:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.801 X-Spam-Level: X-Spam-Status: No, score=-109.801 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id DQO8NUu6M1z6 for ; Fri, 16 Nov 2018 07:03:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 9C64C623C7 for ; Fri, 16 Nov 2018 07:03:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 07242E1013 for ; Fri, 16 Nov 2018 07:03:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A3C7E21E7E for ; Fri, 16 Nov 2018 07:03:00 +0000 (UTC) Date: Fri, 16 Nov 2018 07:03:00 +0000 (UTC) From: "Sushil Ks (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-9016) DocumentStore as a backend for ATSv2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-9016?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Sushil Ks updated YARN-9016: ---------------------------- Description:=20 h1. Document Store for ATSv2 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The Document Store f= or ATSv2 is a framework for plugging in any Document Store Vendor as a back= end for ATSv2 i.e Azure CosmosDB , MongoDB, ElasticSearch etc. * Supports multiple Document Store Vendors like CosmosDB, ElasticSearch, M= ongoDB etc by just adding new configurations properties and writing Documen= t Store reader and writer clients. * Currently has support for CosmosDB. * All writes are Async and buffered, latest document would be flushed to t= he store either if the document buffer gets full or periodically at every f= lush interval in background without adding any additional latency to the ru= nning jobs.. * All the REST API's of Timeline Reader Server are supported. h4. =C2=A0 *How to enable?* Add the flowing properties under *yarn-site.xml* {code:java} yarn.timeline-service.writer.class</name> org.apache.hadoop.yarn.server.timelineservice.storage.documentstore= .DocumentStoreTimelineWriterImpl yarn.timeline-service.reader.class</name> or= g.apache.hadoop.yarn.server.timelineservice.storage.documentstore.DocumentS= toreTimelineReaderImpl =20 yarn.timeline-service.documentstore.db-name =20 YOUR_DATABASE_NAME = =20 {code} h3. *Creating DB and Collections for storing documents* =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 This is similar to HBase *TimelineSchemaCreator* the following command = needs to be executed once for setting up the database and collections for s= toring documents. {code:java} hadoop org.apache.hadoop.yarn.server.timelineservice.documentstore.Document= StoreCollectionCreator {code} h3. =C2=A0*Azure CosmosDB*=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0To use Azure CosmosDB as a DocumentStore for ATS= v2, the additional properties under *yarn-site.xml* is required.. {code:java} =C2=A0=20 yarn.timeline-service.store-type=C2=A0=20 COSMOS_DB yarn.timeline-service.cosmos-db.endpoint http://YOUR_AZURE_COSMOS_DB_URL:443/ yarn.timeline-service.cosmos-db.masterkey YOUR_AZURE_COSMOS_DB_MASTER_KEY_CREDENTIAL {code} =C2=A0 =C2=A0 *Testing locally* =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 In order to test the Azur= e CosmosDB as a DocumentStore locally, install the emulator from [here|http= s://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator]=C2=A0and start= it locally. Set the endpoint and master key under *yarn-site.xml*=C2=A0as = mentioned above and run any example job like DistributedShell etc. Later yo= u can check the data explorer UI of Azure CosmosDB locally to query the doc= uments or even launch the=C2=A0*TimelineReader* locally and fetch/query the= data from REST API's.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 was: h1. Document Store for ATSv2 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The Document Store f= or ATSv2 is a framework for plugging in any Document Store as a backend for= ATSv2 i.e Azure CosmosDB , MongoDB, ElasticSearch etc. * Supports multiple Document Store Vendors like CosmosDB, ElasticSearch, M= ongoDB etc by just adding new configurations properties and writing Documen= t Store reader and writer clients. * Currently has support for CosmosDB. * All writes are Async and buffered, latest document would be flushed to t= he store either if the document buffer gets full or periodically at every f= lush interval in background without adding any additional latency to the ru= nning jobs.. * All the REST API's of Timeline Reader Server are supported. h4. =C2=A0 *How to enable?* Add the flowing properties under *yarn-site.xml* {code:java} yarn.timeline-service.writer.class org.apache.hadoop.yarn.server.timelineservice.storage.documentstore= .DocumentStoreTimelineWriterImpl yarn.timeline-service.reader.class org.a= pache.hadoop.yarn.server.timelineservice.storage.documentstore.DocumentStor= eTimelineReaderImpl =20 yarn.timeline-service.documentstore.db-name =20 YOUR_DATABASE_NAME = =20 {code} h3. *Creating DB and Collections for storing documents* =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 This is similar to HBase *TimelineSchemaCreator* the following command = needs to be executed once for setting up the database and collections for s= toring documents. {code:java} hadoop org.apache.hadoop.yarn.server.timelineservice.documentstore.Document= StoreCollectionCreator {code} h3. =C2=A0*Azure CosmosDB*=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0To use Azure CosmosDB as a DocumentStore for ATS= v2, the additional properties under *yarn-site.xml* is required.. {code:java} =C2=A0=20 yarn.timeline-service.store-type=C2=A0=20 COSMOS_DB yarn.timeline-service.cosmos-db.endpoint http://YOUR_AZURE_COSMOS_DB_URL:443/ yarn.timeline-service.cosmos-db.masterkey YOUR_AZURE_COSMOS_DB_MASTER_KEY_CREDENTIAL {code} =C2=A0 =C2=A0 *Testing locally* =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 In order to test the Azur= e CosmosDB as a DocumentStore locally, install the emulator from [here|http= s://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator]=C2=A0and start= it locally. Set the endpoint and master key under *yarn-site.xml*=C2=A0as = mentioned above and run any example job like DistributedShell etc. Later yo= u can check the data explorer UI of Azure CosmosDB locally to query the doc= uments or even launch the=C2=A0*TimelineReader* locally and fetch/query the= data from REST API's.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 > DocumentStore as a backend for ATSv2 > ------------------------------------ > > Key: YARN-9016 > URL: https://issues.apache.org/jira/browse/YARN-9016 > Project: Hadoop YARN > Issue Type: New Feature > Components: ATSv2 > Reporter: Sushil Ks > Assignee: Sushil Ks > Priority: Major > Attachments: YARN-9016.001.patch > > > h1. Document Store for ATSv2 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The Document Store= for ATSv2 is a framework for plugging in any Document Store Vendor as a ba= ckend for ATSv2 i.e Azure CosmosDB , MongoDB, ElasticSearch etc. > * Supports multiple Document Store Vendors like CosmosDB, ElasticSearch,= MongoDB etc by just adding new configurations properties and writing Docum= ent Store reader and writer clients. > * Currently has support for CosmosDB. > * All writes are Async and buffered, latest document would be flushed to= the store either if the document buffer gets full or periodically at every= flush interval in background without adding any additional latency to the = running jobs.. > * All the REST API's of Timeline Reader Server are supported. > h4. =C2=A0 > *How to enable?* > Add the flowing properties under *yarn-site.xml* > {code:java} > > > yarn.timeline-service.writer.class</name> > org.apache.hadoop.yarn.server.timelineservice.storage.documentsto= re.DocumentStoreTimelineWriterImpl > > > yarn.timeline-service.reader.class</name> = org.apache.hadoop.yarn.server.timelineservice.storage.documentstore.Documen= tStoreTimelineReaderImpl > > =20 > yarn.timeline-service.documentstore.db-name =20 > YOUR_DATABASE_NAME = =20 > {code} > h3. *Creating DB and Collections for storing documents* > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 This is similar to HBase *TimelineSchemaCreator* the following command = needs to be executed once for setting up the database and collections for s= toring documents. > {code:java} > hadoop org.apache.hadoop.yarn.server.timelineservice.documentstore.Docume= ntStoreCollectionCreator > {code} > h3. =C2=A0*Azure CosmosDB*=C2=A0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0To use Azure CosmosDB as a DocumentStore for A= TSv2, the additional properties under *yarn-site.xml* is required.. > {code:java} > > =C2=A0=20 > yarn.timeline-service.store-type=C2=A0=20 > COSMOS_DB > > > yarn.timeline-service.cosmos-db.endpoint > http://YOUR_AZURE_COSMOS_DB_URL:443/ > > > yarn.timeline-service.cosmos-db.masterkey > YOUR_AZURE_COSMOS_DB_MASTER_KEY_CREDENTIAL > > {code} > =C2=A0 > =C2=A0 *Testing locally* > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 In order to test the Az= ure CosmosDB as a DocumentStore locally, install the emulator from [here|ht= tps://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator]=C2=A0and sta= rt it locally. Set the endpoint and master key under *yarn-site.xml*=C2=A0a= s mentioned above and run any example job like DistributedShell etc. Later = you can check the data explorer UI of Azure CosmosDB locally to query the d= ocuments or even launch the=C2=A0*TimelineReader* locally and fetch/query t= he data from REST API's.=C2=A0 =C2=A0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 > =C2=A0 =C2=A0 =C2=A0=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org