Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <CAHxLZBWcAQtbxTqRh_OEE5GzGMNb9R+uOfj4wRA8FHGxOE=WTw@mail.gmail.com>
References: <CAN5cbe6J1Pszy702tWQ2muu5K58hvCizyTRVhMQhdz98WKpz2w@mail.gmail.com>
 <CA+RK=_BDXmV1Hoxyqya52FmH6jbYOfXC9jdzNZ+=9_3Epm9LVw@mail.gmail.com> <CAHxLZBWcAQtbxTqRh_OEE5GzGMNb9R+uOfj4wRA8FHGxOE=WTw@mail.gmail.com>
From: Andrew Purtell <apurtell@apache.org>
Date: Wed, 29 Jun 2016 14:31:33 -0700
Message-ID: <CA+RK=_C6ya1oUyPU-h+kJnyeW_gRzf+0HNWYawy93ZDQkbYmPg@mail.gmail.com>
Subject: Re: [DISCUSS] issue trackers and recent stability of issues.apache/jira
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a113a9efa97c2930536717c8f
archived-at: Wed, 29 Jun 2016 21:32:17 -0000

--001a113a9efa97c2930536717c8f
Content-Type: text/plain; charset=UTF-8

From what I've been able to glean on #asfinfra JIRA is leaking threads
until in an unusable state, at which point it gets rebooted.
Troubleshooting tools cause additional outages by freezing the JVM while
collecting thread traces for hundreds of threads. ASF is trying to engage
Atlassian support to figure it out. Looks like a JIRA bug.


On Wed, Jun 29, 2016 at 2:20 PM, Mikhail Antonov <olorinbant@gmail.com>
wrote:

> Anyone knows ASF Infra / ASF Board position on it? Why is ASF jira not
> stable enough - is it matter or insufficient hardware, no people supporting
> it or ...?
>
> I probably missed some discussions around this matter in the past.
>
> -Mikhail
>
> On Wed, Jun 29, 2016 at 2:06 PM, Andrew Purtell <apurtell@apache.org>
> wrote:
>
> > JIRA identifiers in commits are essential for just about everything I do
> > with HBase release management, maintenance, and operational support. I'm
> > not opposed to switching to something else but then our backstory is
> split
> > over (at least) two sources, without ease of cross-linking references.
> >
> >
> > On Wed, Jun 29, 2016 at 1:06 PM, Sean Busbey <busbey@apache.org> wrote:
> >
> > > Heya folks,
> > >
> > > ASF hosted JIRA has had a rough go of things over the last few months.
> > > Between the spam attacks impacting both availability and our usage
> > > patterns and whatever has been causing the brown outs over the last
> > > two days, things are impacting at least _my_ ability to make use of
> > > the time I have available for the project.
> > >
> > > There are other options available to us as a project; no ASF policy
> > > requires us to use any particular issue tracker or even an ASF hosted
> > > issue tracker at all.
> > >
> > > Before I go through the effort to figure out what our requirements
> > > would be for a third party solutions (in terms of user load,
> > > persistence of messages, etc), what's our community temperature on
> > > this issue? Do we have the stomach for a transition?
> > >
> > > -
> > > busbey
> > >
> >
> >
> >
> > --
> > Best regards,
> >
> >    - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
>
>
> --
> Thanks,
> Michael Antonov
>


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

--001a113a9efa97c2930536717c8f--