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

Hi Benoy,

Yes, many users have been reporting errors interacting with ASF JIRA today.
The good folks at ASF INFRA are aware of the issue and are looking into it.

--
Aaron T. Myers
Software Engineer, Cloudera

On Thu, Aug 9, 2012 at 4:10 PM, Benoy Antony <[EMAIL PROTECTED]> 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
>

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 <[EMAIL PROTECTED]> 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
>

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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>

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 <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>
>

Just as Robert Evans mentioned, I found that Jira issue was getting created
even though there was an error message.
It seems I created several duplicate jiras . I cannot delete them.

If someone with administrative privileges can delete the following
duplicate jiras, that will be great .

MAPREDUCE-4527, 4528, 4529, 4530, 4531, 4532 , 4537, 4540 , 4541 ,  4542,
4543, 4544, 4545 ,  4546 ,4547

Sorry for this trouble.

Thanks ,

Benoy

On Thu, Aug 9, 2012 at 4:33 PM, Steve Loughran <[EMAIL PROTECTED]>wrote:

> 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 <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
> >>>
> >
>

Please include MAPREDUCE-4526 also as it is also in a weird sate.

On Thu, Aug 9, 2012 at 4:37 PM, Benoy Antony <[EMAIL PROTECTED]> wrote:

> Just as Robert Evans mentioned, I found that Jira issue was getting
> created even though there was an error message.
> It seems I created several duplicate jiras . I cannot delete them.
>
> If someone with administrative privileges can delete the following
> duplicate jiras, that will be great .
>
> MAPREDUCE-4527, 4528, 4529, 4530, 4531, 4532 , 4537, 4540 , 4541 ,  4542,
> 4543, 4544, 4545 ,  4546 ,4547
>
> Sorry for this trouble.
>
> Thanks ,
>
> Benoy
>
> On Thu, Aug 9, 2012 at 4:33 PM, Steve Loughran <[EMAIL PROTECTED]>wrote:
>
>> 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 <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>> >>>
>> >
>>
>
>

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" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>
>

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 [EMAIL PROTECTED] in my Inbox.
This shows benefit when JIRA is down.

Cheers

On Sat, Aug 11, 2012 at 7:14 PM, Jun Ping Du <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> 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 <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
> >>>
> >
>

Thanks Ted. Those are very good suggestions as backup solutions when JIRA is down.
Besides alleviating the impact of JIRA downtime as you mentioned above, do we think of some way to keep JIRA system highly available? It is a little embarrassing that we deliver all kinds of HA systems to rest of world, but we suffering from this. :(

----- Original Message -----
From: "Ted Yu" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Sent: Sunday, August 12, 2012 12:17:36 PM
Subject: Re: Cannot create a new Jira issue for MapReduce

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 [EMAIL PROTECTED] in my Inbox.
This shows benefit when JIRA is down.

Cheers

On Sat, Aug 11, 2012 at 7:14 PM, Jun Ping Du <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> 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 <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
> >>>
> >
>