The requested article has expired, and is no longer available. Any related articles, and user comments are shown below.
© 2020 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without permission.Tokyo Stock Exchange resumes trading after technical outage
By Yuri Kageyama TOKYO©2024 GPlusMedia Inc.
10 Comments
Login to comment
theFu
Had to look up "bourse" - never heard or seen that term used anywhere. Appears to be the correct use in the article.
A number of large computing systems had failures this week. Many were traced back to MS-Azure Active Directory faults. Trading platforms don't use AD, I don't believe.
Extremely low-latency systems like world exchanges deploy are amazing systems. Bet a bunch of people will be testing the failover processes and code this weekend.
Eppee
Isn't it the French for exchange ?
Sh1mon M4sada
...it was only a few weeks ago that the LDP was trying to position Osaka as an international financial centre. Better beef up redundancy etc.
TARA TAN KITAOKA
What a joke. Where are the apologies ???.
bokuda
They won't tell. Japan is famous for it's institutionalized obscurity.
Cricky
And the number of people effected? less then the number of reporters on the scene.
darknuts
That's a suprising statistic. Japanese should invest more in their own economy.
bokuda
They only talk about "machine one" and "machine two", Did the other 348 machines had a hardware problem also?
theFu
Seriously doubt it was a hardware failure. On systems like that, all the hardware is redundant AND there is a backup system also with redundant everything. All networking is setup redundant as well. Where I worked, we'd use 6 network connections for each basic server. Something in HA would have 12 connections to redundant switches, redundant storage connections to redundant storage and each card internal to the server would be specifically located so that redundant internal buses would be used.
In short, it was a software issue, probably just a misconfiguration.
The fact that this happened meant it wasn't tested after the last modification "somewhere" in the chain. On systems like this, there will be records of who did what, when, exactly along with the 3 levels of approvals from management chains above. They would normally spend weeks planning any changes, reviewing the steps, and probably testing the changes on identically configured systems.