【客户端更新】【Prysm】v1.3.0 20210224

大家好,我们很荣幸宣布v1.3.0. 这个版本包括对运行多个验证人密钥的节点的重要性能提升。在Pyrmont测试网上,Prysmatic Labs运行着包括大量验证人密钥的Prysm验证人节点。

在这种规模运行时,我们发现在slash保护数据库查找的效率低下,这个问题比较难找到,因为只在不够强大的硬件上才会出现,并且30分钟后最终消失。有一篇关于这个问题的文章: When a Solution Is Right In Front of You | rauljordan.

:rotating_light: 回滚至 v1.2.x :rotating_light:

与许多修改一样,这次需要进行数据库迁移。这种情况下Prysm在为已有数据编制索引。如果你出于任何原因要回滚,请务必取消设置数据库中的迁移,以便在将来向前滚动至v1.3.0+时再次迁移。

如果需要回滚到v1.2.x,则必须运行验证人数据库反向迁移,请参阅此处的完整说明: Upgrading and downgrading Prysm | Prysm.

显著变化

  • Signficant improvements to slashing protection lookups #8460
    /healthz formatting #8472
  • Updated go-ethereum dependency. This no longer causes prysm to have ipv4 addresses in ipv6 mapped addresses for discovery packets. #8490
  • Implemented more eth2api methods #8476 #8456
  • Logging improvements #8330 #8457

Hello @everyone, we are proud to announce v1.3.0 of Prysm. This release includes important performance improvements for operators running a lot of validator keys. In the Pyrmont Testnet, Prysmatic Labs runs Prysm validators with a large volume of validating keys.
When operating at this scale, we have observed some inefficiencies in slashing protection db lookups. This issue was particularly difficult to pinpoint as it was only reproducible on less powerful hardware
and the symptoms eventually resolved after about 30 minutes. an article
about this issue can be seen here When a Solution Is Right In Front of You | rauljordan.

When a Solution Is Right In Front of You | rauljordan.

:rotating_light: Rolling back to v1.2.x :rotating_light:

As with many schema changes, there is a database migration required. In this case, Prysm is populating an
index with existing data. If you need to rollback for any reason, it is important to unset the migration
in the database so that the migration will occur again when you roll forward to 1.3.0+ in the future.

If you need to rollback to v1.2.x, you must run the validator database reverse migration.
See full instructions here Upgrading and downgrading Prysm | Prysm.

Notable changes

  • Signficant improvements to slashing protection lookups #8460
    /healthz formatting #8472
  • Updated go-ethereum dependency. This no longer causes prysm to have ipv4 addresses in ipv6 mapped addresses for discovery packets. #8490
  • Implemented more eth2api methods #8476 #8456
  • Logging improvements #8330 #8457