Hoskinson Is Reassured By Cardano’s “Self-Healing”
Key Points:
- Charles Hoskinson, CEO of Input Output, it is difficult to determine the precise reason of the Cardano node issue due to its temporary nature.
- Block generation was impacted for two to five minutes, briefly throwing the chain out of sync when the afflicted nodes rebooted.
- Hoskinson blamed “emergent bugs,” adding that quirks of this type can sometimes arise in distributed systems due to their global framework.
According to Charles Hoskinson, CEO of Input Output, it is difficult to determine the precise reason of the Cardano node issue due to its temporary nature.
He did, however, emphasize that the network handled the outage exactly as it was intended to. He also commended the IO team and Stake Pool Operators (SPOs) for cooperating to resolve the problem.
“Sh*t always breaks Sunday morning, or Monday morning, late at night when everyone is sleeping. That’s just the way things work.
The long and short is that it seems to be a transient issue.”
A “transient anomaly” on January 22 caused 50% of Cardano nodes to disconnect and then resume.
Block generation was impacted for two to five minutes, briefly throwing the chain out of sync when the afflicted nodes rebooted. There was a brief period of network breakdown, but Hoskinson described it as “self-healing” in recovery.
Initial IO studies revealed no obvious root cause. The IO CEO has now added to this, stating that it would be challenging to recreate the identical circumstances that caused the anomaly because a number of factors were probably converging to cause it.
“It’s probably a collection of things that happened at the same time, which means the reproducibility is unlikely.”
Hoskinson expands on the details
In the course of further investigations, the call error was identified, but the triggering event has yet to be determined, said Hoskinson.
Expanding on this, Hoskinson blamed “emergent bugs,” adding that quirks of this type can sometimes arise in distributed systems due to their global framework.
“The problem is that distributed systems sometimes create what is called emergent bugs. So locally, it’s not reproducible, but a collection of things create a collective global state that, for some reason, triggers something and the whole system basically stops for some people.”
These “once in a five-year” glitches sometimes cannot be figured out. Sometimes they can be resolved, but “you never want to drive yourself nuts over it,” said Hoskinson.
DISCLAIMER: The Information on this website is provided as general market commentary and does not constitute investment advice. We encourage you to do your research before investing.
Join us to keep track of news: https://linktr.ee/coincu
Website: coincu.com
Annie
Coincu News
Author
News
Hoskinson Is Reassured By Cardano’s “Self-Healing”
Key Points:
- Charles Hoskinson, CEO of Input Output, it is difficult to determine the precise reason of the Cardano node issue due to its temporary nature.
- Block generation was impacted for two to five minutes, briefly throwing the chain out of sync when the afflicted nodes rebooted.
- Hoskinson blamed “emergent bugs,” adding that quirks of this type can sometimes arise in distributed systems due to their global framework.
According to Charles Hoskinson, CEO of Input Output, it is difficult to determine the precise reason of the Cardano node issue due to its temporary nature.
He did, however, emphasize that the network handled the outage exactly as it was intended to. He also commended the IO team and Stake Pool Operators (SPOs) for cooperating to resolve the problem.
“Sh*t always breaks Sunday morning, or Monday morning, late at night when everyone is sleeping. That’s just the way things work.
The long and short is that it seems to be a transient issue.”
A “transient anomaly” on January 22 caused 50% of Cardano nodes to disconnect and then resume.
Block generation was impacted for two to five minutes, briefly throwing the chain out of sync when the afflicted nodes rebooted. There was a brief period of network breakdown, but Hoskinson described it as “self-healing” in recovery.
Initial IO studies revealed no obvious root cause. The IO CEO has now added to this, stating that it would be challenging to recreate the identical circumstances that caused the anomaly because a number of factors were probably converging to cause it.
“It’s probably a collection of things that happened at the same time, which means the reproducibility is unlikely.”
Hoskinson expands on the details
In the course of further investigations, the call error was identified, but the triggering event has yet to be determined, said Hoskinson.
Expanding on this, Hoskinson blamed “emergent bugs,” adding that quirks of this type can sometimes arise in distributed systems due to their global framework.
“The problem is that distributed systems sometimes create what is called emergent bugs. So locally, it’s not reproducible, but a collection of things create a collective global state that, for some reason, triggers something and the whole system basically stops for some people.”
These “once in a five-year” glitches sometimes cannot be figured out. Sometimes they can be resolved, but “you never want to drive yourself nuts over it,” said Hoskinson.
DISCLAIMER: The Information on this website is provided as general market commentary and does not constitute investment advice. We encourage you to do your research before investing.
Join us to keep track of news: https://linktr.ee/coincu
Website: coincu.com
Annie
Coincu News
Other Posts
Related Posts
News
The Bitcoin Epic Satoshi Of The 4th Halving Was Auctioned For Over $2.1 Million
News
Hong Kong Crypto ETFs Of HashKey And Bosera Completed Subscription To Launch On April 30
News
