Sentinel v2.0.0-alpha Release Notes

Release Date: 2023-02-28 // over 3 years ago
  • 🏗 This is the first preview version of nouveau Sentinel 2.0, bringing the building blocks and basic implementation of traffic routing and load balancing.

    🔋 Features / Enhancements

    • ➕ Add building blocks and basic implementation of traffic routing and load balancing (#3024)
    • ➕ Add data-source extension for OpenSergo fault-tolerance spec (#2842)
    • ➕ Add default circuit breaker rule support (#2232)
    • 👍 Refine throttling control behavior of FlowRule: improve accuracy and support maxQps > 1000 (#2951)
    • ⚡️ Update metrics name for better monitor selection in JMX MetricBeanWriter extension (#2976)

    🐛 Bug Fixes

    • 🛠 Fix NPE bug in LogSlot#entry when recording rule ID (#2980)
    • 🛠 Fix the bug that error occurs in JMX metrics exporter when resource name contains '*' (#2992)
    • 🛠 Fix thread-blocked problem of EtcdDataSource (#2991)
    • 🛠 Fix potential connection leak bug when closing NacosDataSource (#2962)

    Dashboard

    • ➕ Add simple Dockerfile for Sentinel dashboard (#2970)

    Dependencies

    • ⬆️ Upgrade curator-recipes to 5.1.0 to fix API change for ZooKeeper data-source (#2963)

Previous changes from v1.8.6

  • 🚀 This release ships with a few enhancements and bug fixes.

    🔧 Furthermore, Sentinel OpenSergo data-source has been beta-available (com.alibaba.csp:sentinel-datasource-opensergo:0.1.0-beta), which enables developers to configure Sentinel rules with OpenSergo fault-tolerance CRD in a unified way (under Kubernetes, with OpenSergo control plane).

    🔋 Features / Enhancements

    • ➕ Add id field in Rule entity and record rule ID in block log (#2853)

    🐛 Bug Fixes

    • 🛠 Fix Dubbo SPI path bug in Dubbo 3.x adapter (#2822)
    • 🛠 Fix the bug that SpiLoader#closeResources may not record the exception when error occurs (#2890)

    Dashboard

    • 👌 Improve IP validation in SentinelApiClient and rule controllers

    Thanks for all contributors: @AlbumenJ, @hongpy, @icodening, @PepoRobert, @sczyh30, @ZhongJinHacker