Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7265CD465 for ; Sun, 12 Aug 2012 04:18:16 +0000 (UTC) Received: (qmail 18024 invoked by uid 500); 12 Aug 2012 04:18:14 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 16355 invoked by uid 500); 12 Aug 2012 04:18:04 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 16288 invoked by uid 99); 12 Aug 2012 04:18:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 12 Aug 2012 04:18:02 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.212.170 as permitted sender) Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com) (209.85.212.170) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 12 Aug 2012 04:17:56 +0000 Received: by wibhq12 with SMTP id hq12so2029879wib.5 for ; Sat, 11 Aug 2012 21:17:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V4kMcezuLirvu9ILLGRyZXGer4mqlPx2I0G6YDDYN/Y=; b=OTzJFSw4hauEet87xkzACHdMfqpWbtJDPhZdVyUiMSSsjy8SR7XtdncMPYCIaeYIUT tmUz6ICqQa84JyWkI5dyuNzf8fABOAQ3PcwBatW3hqCTSuay3+nP6xqeNzwYKdeJVCgv 8FirLGrthr949rHalxug1JNGedymopJ/u6RmQEnElTXdcDwD0OYMkPge49g4JvOyvuQR vlR8DvzocnmXzoXh6MXoizeKKxczXhYLUeEYMJ/gVcQDUMfl55KPNX4A0210Z+bEA5p5 PbF6SizP2+gzxwbshww8EbgtuLDUawot3WL5AxIA5wI3yWxOSK6pB28ylG9Q5AVY16Mk 6Ppw== MIME-Version: 1.0 Received: by 10.216.234.231 with SMTP id s81mr4425088weq.34.1344745056069; Sat, 11 Aug 2012 21:17:36 -0700 (PDT) Received: by 10.216.28.202 with HTTP; Sat, 11 Aug 2012 21:17:36 -0700 (PDT) In-Reply-To: <227017361.24644533.1344737679843.JavaMail.root@vmware.com> References: <227017361.24644533.1344737679843.JavaMail.root@vmware.com> Date: Sat, 11 Aug 2012 21:17:36 -0700 Message-ID: Subject: Re: Cannot create a new Jira issue for MapReduce From: Ted Yu To: mapreduce-dev@hadoop.apache.org Cc: hdfs-dev@hadoop.apache.org, common-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd4d94c6168c104c709dbb0 --000e0cd4d94c6168c104c709dbb0 Content-Type: text/plain; charset=ISO-8859-1 I made some suggestions to hbase dev mailing list a few weeks ago. The following suggestion is about hbase development which can be extrapolated to other Apache projects. People can continue discussion through dev mailing list when JIRA is down. When JIRA comes back up, transcript of such discussion can be posted back on related issues. Use of https://reviews.apache.org is encouraged. The review board wasn't affected by JIRA downtime. Running test suite by contributors and committers is encouraged which alleviates the burden on Hadoop QA. Goal for the above suggestions is for alleviating the impact of JIRA down time. BTW I have kept notifications from issues@hbase.apache.org in my Inbox. This shows benefit when JIRA is down. Cheers On Sat, Aug 11, 2012 at 7:14 PM, Jun Ping Du wrote: > Yes. I saw JIRA is in maintenance now and the schedule is as below: > > Host Name Service Entry Time Author Comment Start Time > End Time Type Duration Downtime ID Trigger ID > Actions > ull.zones.apache.org Issues - JIRA - General 2012-08-11 19:06:08 > danielsh Migrating to a different physical host 2012-08-11 19:06:08 > 2012-08-13 19:06:08 Fixed 2d 0h 0m 0s 1663 N/A > Delete/Cancel This Scheduled Downtime Entry > > Looks like it will take 2 days to migrate to a different host. As JIRA is > a key component to dev process in community, do we think of some ways to > lower the maintenance overhead? > > > Thanks, > > Junping > > ----- Original Message ----- > From: "Steve Loughran" > To: mapreduce-dev@hadoop.apache.org > Sent: Friday, August 10, 2012 7:33:04 AM > Subject: Re: Cannot create a new Jira issue for MapReduce > > There's been disk problems w/ Jira recently. Githubs been playing up > this morning to. Time to put away the dev tools and get powerpoint out > instead > > On 9 August 2012 13:38, Robert Evans wrote: > > It is a bit worse then that though. I found that it did create the JIRA, > > but it is in a bad state where you cannot put it in patch available or > > close it. So we may need to do some cleanup of these JIRAs later. > > > > --Bobby > > > > On 8/9/12 3:19 PM, "Ted Yu" wrote: > > > >>This has been reported by HBase developers as well. > >> > >>See https://issues.apache.org/jira/browse/INFRA-5131 > >> > >>On Thu, Aug 9, 2012 at 1:10 PM, Benoy Antony wrote: > >> > >>> Hi, > >>> > >>> I am getting the following error when I try to create a Jira issue. > >>> > >>> Error creating issue: com.atlassian.jira.util.RuntimeIOException: > >>> java.io.IOException: read past EOF > >>> > >>> Anyone else face the same problem ? > >>> > >>> Thanks , > >>> Benoy > >>> > > > --000e0cd4d94c6168c104c709dbb0--