Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8DEFB2009D9 for ; Wed, 18 May 2016 06:57:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8C622160A24; Wed, 18 May 2016 04:57:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D6929160A09 for ; Wed, 18 May 2016 06:57:13 +0200 (CEST) Received: (qmail 6052 invoked by uid 500); 18 May 2016 04:57:13 -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 6006 invoked by uid 99); 18 May 2016 04:57:12 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 May 2016 04:57:12 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CC84C2C14E1 for ; Wed, 18 May 2016 04:57:12 +0000 (UTC) Date: Wed, 18 May 2016 04:57:12 +0000 (UTC) From: "Sangjin Lee (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-5109) timestamps are stored unencoded causing parse errors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 18 May 2016 04:57:14 -0000 Sangjin Lee created YARN-5109: --------------------------------- Summary: timestamps are stored unencoded causing parse errors Key: YARN-5109 URL: https://issues.apache.org/jira/browse/YARN-5109 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Affects Versions: YARN-2928 Reporter: Sangjin Lee Priority: Blocker When we store timestamps (for example as part of the row key or part of the column name for an event), the bytes are used as is without any encoding. If the byte value happens to contain a separator character we use (e.g. "!" or "="), it causes a parse failure when we read it. I came across this while looking into this error in the timeline reader: {noformat} 2016-05-17 21:28:38,643 WARN org.apache.hadoop.yarn.server.timelineservice.storage.common.TimelineStorageUtils: incorrectly formatted column name: it will be discarded {noformat} I traced the data that was causing this, and the column name (for the event) was the following: {noformat} i:e!YARN_RM_CONTAINER_CREATED=\x7F\xFF\xFE\xABDY=\x99=YARN_CONTAINER_ALLOCATED_HOST {noformat} Note that the column name is supposed to be of the format (event id)=(timestamp)=(event info key). However, observe the timestamp portion: {noformat} \x7F\xFF\xFE\xABDY=\x99 {noformat} The presence of the separator ("=") causes the parse error. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org