简体   繁体   English

Opendaylight可扩展性

[英]Opendaylight scalability

We are using Nitrogen-SR3 version of Opendaylight. 我们正在使用Nitrogen-SR3版本的Opendaylight。 We want to support more NEs, and during our testing observed "Shards" missing. 我们希望支持更多的NE,并且在我们的测试中发现“碎片”丢失了。 While analyzing this issue we noticed Shards are missing as LevelDB is not acknowledging the writes as it is very busy. 在分析此问题时,我们注意到Shards丢失了,因为LevelDB由于非常忙而没有确认写入。 We came across Cassandra plugin for "Akka" persistence, will it be a good idea to use Cassandra instead of LevelDB so that we can scale better. 我们遇到了用于“ Akka”持久性的Cassandra插件,使用Cassandra代替LevelDB是一个好主意,以便我们可以更好地扩展。

Please advice us whether there are any production deployment with Cassandra plugin for Akka persistence. 请告知我们是否有用于Cassandra持久性的Cassandra插件的任何生产部署。

Of course you can use whatever plugin suits your environment and needs. 当然,您可以使用适合您的环境和需求的任何插件。 I'm not aware of anyone using Cassandra. 我不知道有人在使用Cassandra。 LevelDB is suitable as a default as it's simple and doesn't require any external server. LevelDB非常简单,不需要任何外部服务器,因此适合作为默认值。 It seems to work fine for most use cases even though akka doesn't recommend it for production. 即使akka不推荐将其用于生产,它似乎在大多数用例中都可以正常工作。

I assume you're probably hitting the (dreaded) circuit-breaker timeout in akka when the plugin response isn't timely which can happen with a slow disk or saturation. 我认为当插件响应不及时时(如果磁盘速度慢或饱和可能会发生),您很可能在akka中遇到了(可怕的)断路器超时。 The default timeout is 5 sec but is configurable (check the akka persistence docs). 默认超时为5秒,但可以配置(请参阅akka持久性文档)。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM