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 77DED200C4E for ; Thu, 23 Mar 2017 01:19:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 766CF160B86; Thu, 23 Mar 2017 00:19:46 +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 BA26E160B91 for ; Thu, 23 Mar 2017 01:19:45 +0100 (CET) Received: (qmail 12253 invoked by uid 500); 23 Mar 2017 00:19:44 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 12233 invoked by uid 99); 23 Mar 2017 00:19:44 -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; Thu, 23 Mar 2017 00:19:44 +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 7C62BC0FEE for ; Thu, 23 Mar 2017 00:19:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -98.549 X-Spam-Level: X-Spam-Status: No, score=-98.549 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 8egfIkRc0urS for ; Thu, 23 Mar 2017 00:19:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1D9CB5FCD6 for ; Thu, 23 Mar 2017 00:19:43 +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 01648E0559 for ; Thu, 23 Mar 2017 00:19:42 +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 B2546254EA for ; Thu, 23 Mar 2017 00:19:41 +0000 (UTC) Date: Thu, 23 Mar 2017 00:19:41 +0000 (UTC) From: "Alejandro Fernandez (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-20505) Changes needed to handle AMBARI-19623 in EU/RU scenario MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 23 Mar 2017 00:19:46 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937438#comment-15937438 ] Alejandro Fernandez commented on AMBARI-20505: ---------------------------------------------- Pushed to trunk, commit ca2c83582e135bb5410b62775292a780e68757eb STILL NEED TO COMMIT TO branch-2.5 after the RC candidate is done and the 2.5 release is done. > Changes needed to handle AMBARI-19623 in EU/RU scenario > ------------------------------------------------------- > > Key: AMBARI-20505 > URL: https://issues.apache.org/jira/browse/AMBARI-20505 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: trunk, 2.5.0 > Reporter: Ayub Khan > Assignee: Vishal Suvagia > Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20505_branch2.5.patch, AMBARI-20505.patch, AMBARI-20505_trunk.patch > > > Currently zookeeper connect/session timeout values for atlas are set to 200/400 ms respectively which are very low and not practical/recommended values. Due to this atlas startup fails more frequently. > The jira is set recommended values for zookeeper timeout configuration. > {noformat} > atlas.kafka.zookeeper.connection.timeout.ms=30000 > atlas.kafka.zookeeper.session.timeout.ms=60000 > atlas.audit.zookeeper.session.timeout.ms=60000 > {noformat} > As per the comment by [~afernandez] in the below link, these changes has to be handled in EU/RU scenario. > https://issues.apache.org/jira/browse/AMBARI-19623?focusedCommentId=15830880&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15830880 -- This message was sent by Atlassian JIRA (v6.3.15#6346)