Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

twitter.com

Post reply on HN
Print view View original

161–170 of 260 posts

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#161

Post by IncRnd »

MandieD wrote: post #108
planb wrote: post #100

Earlier quoted context omitted.

We will probably bite the sour apple (not sure if this is correct English but you’ll get the meaning even if it’s not) and switch to the data center edition which is still on prem but costs approximately twice as much.

A bit from the Boom Chicago show I saw in Amsterdam around 2004: “The Dutch expression ‘bite the sour apple’ means the same thing as ‘bite the bullet’ - Americans are obsessed with guns, and the Netherlands is full of shitty food.”

> Americans are obsessed with guns, and the Netherlands is full of shitty food.

"Bite the Bullet" is a phrase from an Englishman, Rudyard Kipling, in his first novel, "The Light That Failed". It's believed to have come from the other English idioms, "to bite the cartridge" and "chew a bullet", which date back to 1891 and at least 1796. [1]

[1] https://en.wikipedia.org/wiki/Bite_the_bullet

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#162

Post by znpy »

deergomoo wrote: post #136
breakingcups wrote: post #101

Earlier quoted context omitted.

It's insane. Since they've all but killed off on-premise Jira and Confluence, they've been spamming me regularly trying to convince me to "upgrade" to the cloud. Eventually I gave in and replied to them asking two simple questions. One is that we've had many bad reports from partners that Jira Cloud is incredibly slow, even when compared to the already underperforming Jira Server and I wonder what their performance g…

> Jira Cloud is incredibly slow I haven’t used Jira Cloud in any great depth, but I did play around with it as part of trialling the free plan and was amused that you could quite easily come across warnings to backup your installation and consult your system administrator before proceeding…how exactly do I do that for a cloud service? Doesn’t exactly inspire confidence. At my last job we used Bitbucket Cloud and that…

> I haven’t used Jira Cloud in any great depth.

I have. It's painfully slow.

But slowness isn't really the problem, the problem is that it's unpredictable.

I wait for the interface to be fully loaded, so I click on a text box and i start typing. Then FU--ING something takes the focus to some other element in the web page and now i'm typing random shortcuts (like reassigning tickets, changing status or whatever).

It's painfully slow but the real problem is that it's unpredictable in its behaviour.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#163

Post by joshuaissac »

bobnamob wrote: post #146
crawl_soever wrote: post #134

Earlier quoted context omitted.

What are disconnected customers going to do? Surely they won't cut off the entire US military and DoD by terminating that cash cow of on premises.

They’re still offering on-prem for airgapped usecases afaik. It’s just become a “contact us” pricing plan

It is not a "contact us" pricing plan. The Data Center prices are publicly available on their website. It is more than twice as expensive as the Server offering, but still substantially cheaper than Cloud for the same number of users.

And it is the exact same software as Server with some extras enabled like support for multiple nodes, so upgrading to it is as simple as pasting in a new product key.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#164

Post by mrits »

Nextgrid wrote: post #26

I bet they screwed up royally, deleted some data and are down to either rebuilding it from logs, caches or other side-effects, or using data recovery software on the storage drives (which might involve third-party companies). I can't see many other reasons why this should take 2 weeks.

A few years ago I depended on Vertica (snowflae/clickhouse) type database.

When a node went down there was no hope of ever coming back up unless you shut the other nodes down as well. While this was going down of course none of our ingress data was being inserted so it built a queue. When we turned things back on the queue would overload vertica again and we had to repeat the whole thing.

Fortunately for us we only stored analytic type data on vertica where customers usually were only interested in the last few hours anyways. So we ended up deleting all historical data and just reprocessing it over months while occasionally prioritizing customers that complained.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#166

Post by BFLpL0QNek »

laurent92 wrote: post #42
Nextgrid wrote: post #26

I bet they screwed up royally, deleted some data and are down to either rebuilding it from logs, caches or other side-effects, or using data recovery software on the storage drives (which might involve third-party companies). I can't see many other reasons why this should take 2 weeks.

Let me bet: Rebuilding from Jira email notifications. Yes, the diffs in the notifications.

Not much on this on the internet.

Gray•Duffy, LLP Settles Two Massive International Data Loss Claims Arising From Computer Server Failures

Arc Touch, Inc. vs. Atlassian PTY, Ltd

http://m.grayduffylaw.com/?url=https%3A%2F%2Fgrayduffylaw.co...

https://www.theregister.com/2012/05/09/atlassian_cloud_stora...

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#167

Post by jrib »

Nextgrid wrote: post #26

I bet they screwed up royally, deleted some data and are down to either rebuilding it from logs, caches or other side-effects, or using data recovery software on the storage drives (which might involve third-party companies). I can't see many other reasons why this should take 2 weeks.

this is a scary thought. I need to start being more aggressive about backing things up that are "in the cloud."

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#168

Post by floatinglotus »

Atlassian does not care about individual customers. They are purely driven by numbers. I listened to a presentation by one of their founders a long time ago where he admitted that statistics and number management was part of their DNA. They don’t think about the customer’s name, maybe this is right, maybe not.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#169

Post by tiahura »

raffraffraff wrote: post #155
m0llusk wrote: post #112

Earlier quoted context omitted.

If you are not regularly testing restores then you don't have backups.

I'd say this is the answer. I remember a situation where we had a near miss with data loss (replica failed and master had a bad disk). We didn't want to put the production database under extra load by taking a live backup while it was handling all production traffic, so we restored a backup. But it was "bad". Tried the one before it, and the one before that. Apparently they were busted for over a month due to a confi…

Went through that once in the mid- late 90’s. Each restore and test took hours, so 3-4 attempts took 2 days - with me sleeping, crying and praying in a conference room.

Re: Atlassian: We estimate the rebuilding effort to last for up to 2 more weeks

#170

Post by WorldMaker »

nvr219 wrote: post #87
WorldMaker wrote: post #65

Earlier quoted context omitted.

Microsoft Planner is included in most Microsoft 365 plans. Pretty much if you've got Teams, you've got Planner (and you can just add Planner as Tab in a Teams channel). At this point it has surprising feature parity with Trello.

Last time I checked (a few months ago), Planner still could not be backed up. Like, at all. If someone went in and deleted a whole bucket you can't recover it, not natively, and not with third party. So that's a big fat no from me.

I seem to recall dumping Planner to JSON easily enough. I don't know if you can easily restore directly from its JSON, but the JSON was nice enough to work on for what little I needed to do with it.

My current employer shut off Trello and forced us over to Jira and is threatening to disable Planner, so I'm "not allowed" to rely on Planner enough day-to-day so it's possible it is either better or worse than I remember it being in that department. But this Jira outage has me reevaluating, and they haven't turned off Planner yet.

Post reply on HN