This is an automated email from the ASF dual-hosted git repository.

ButterBright pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git


The following commit(s) were added to refs/heads/master by this push:
     new dd72494d7af Release Apache SkyWalking BanyanDB 0.10.3 (#853)
dd72494d7af is described below

commit dd72494d7af2ef8861716ba5366eb8d617827f2f
Author: Huang Youliang <[email protected]>
AuthorDate: Sat Jun 20 11:41:03 2026 +0800

    Release Apache SkyWalking BanyanDB 0.10.3 (#853)
---
 .../index.md                                       | 35 +++++++++++++++++++
 content/quickstart-docker.sh                       |  2 +-
 data/docs.yml                                      |  6 ++--
 data/releases.yml                                  | 40 +++++++++++-----------
 4 files changed, 59 insertions(+), 24 deletions(-)

diff --git a/content/events/release-apache-skywalking-banyandb-0-10-3/index.md 
b/content/events/release-apache-skywalking-banyandb-0-10-3/index.md
new file mode 100644
index 00000000000..b890fd9e46e
--- /dev/null
+++ b/content/events/release-apache-skywalking-banyandb-0-10-3/index.md
@@ -0,0 +1,35 @@
+---
+title: Release Apache SkyWalking BanyanDB 0.10.3
+date: 2026-06-20
+author: SkyWalking Team
+---
+
+SkyWalking BanyanDB 0.10.3 is released. Go to [downloads](/downloads) page to 
find release tars.
+
+### Bug Fixes
+
+- Persist segment end time in per-segment metadata so boundaries don't shift 
across restarts or config changes.
+- Fix flaky on-disk integration tests caused by Ginkgo v2 random container 
shuffling closing gRPC connections prematurely.
+- ui: fix query editor refresh/reset behavior and BydbQL keyword highlighting.
+- Fix flaky `file_snapshot` subtest in measure/stream/trace by waiting until 
every introduced mem part has been flushed to disk, instead of only checking 
the latest snapshot creator.
+- Fix flaky `TestCollectWithPartialClosedSegments` by raising 
`SegmentIdleTimeout` so wall-clock variance on slow CI does not mark still-open 
segments as idle.
+- Fix FODC lifecycle cache poisoning where transient `InspectAll` failures 
were cached for 10 minutes and masked liaison recovery; raise FODC agent and 
proxy timeouts from 10s to 40s.
+- Fix FODC `/cluster/lifecycle` dropping zero-valued group fields (e.g. 
`replicas=0`, `close=false`) under `encoding/json` + `omitempty`; switch to 
`protojson` so all fields are emitted (nil nested messages serialize as `null`).
+- Fix trace `block_writer` panic on out-of-order timestamps within the same 
traceID, which dropped one trace-write batch per panic in multi-agent 
SkyWalking deployments. Spans of a single trace originate from 
independently-clocked services, and trace storage is organized by traceID 
rather than timestamp, so per-traceID timestamp monotonicity is not a writer 
invariant.
+- Fix nil-pointer panic on cold-tier data nodes when FODC `InspectAll` raced 
with idle-segment cleanup.
+- Add `GroupLifecycleInfo.errors` to surface per-group collection failures 
from FODC `InspectAll` instead of silently dropping the affected node entry.
+- Fix `CollectDataInfo` and `CollectLiaisonInfo` not handling 
`CATALOG_PROPERTY` groups.
+- Close BanyanDB merge write-path durability gap that allowed torn parts to be 
created by a crash between data write and metadata commit. Metadata files 
(`metadata.json` for trace/measure/stream, `manifest.json` for sidx, plus 
`traceID.filter` and `tag.type`) now go through a new `WriteAtomic` (write-tmp 
+ fsync + rename + fsync-dir) sequence; data writers (`seqWriter.Close`, 
`localFileSystem.Write`) now propagate fdatasync errors instead of silently 
dropping them. `mustOpenFilePart` / ` [...]
+- Fix lifecycle migration where the receiving node could create segments 
shorter than the configured `SegmentInterval`.
+- Fail fast on incompatible storage version at boot. Previously the server 
would start in a degraded `SERVING` state with affected groups un-loaded 
because the property schema-registry retry loop swallowed the 
version-incompatibility panic. Compatible versions are listed in 
`banyand/internal/storage/versions.yml`.
+- Release bluge index writers on segment rotation so `analysisWorker` pools 
sized from `GOMAXPROCS` don't accumulate across rotations. Two layered defects 
kept the existing idle-segment reclaim path from running: `segmentIdleTimeout` 
defaulted to `0` (which disabled the 10-minute reclaim ticker), and `incRef` 
refreshed `lastAccessed` on every rotation tick so `closeIdleSegments` never 
observed an idle segment. Defaults to `time.Hour`, moves the `lastAccessed` 
bump to real read/write call [...]
+- Fix incorrect counts and missing trace fields in the lifecycle migration 
report.
+- Fix trace query identity-tag projection: when `trace_id`/`span_id` are 
explicitly projected, reconstruct them from span identity at response build 
time instead of requesting them as stored tags, and preserve tag order with 
null-filled per-span value alignment in the distributed trace result iterator.
+- Fix FODC proxy corrupting Prometheus metric types. The agent dropped the `# 
TYPE` line while parsing banyandb `/metrics`, the `StreamMetrics` proto carried 
no type field, and the proxy guessed the type from a name-suffix heuristic — 
downgrading counters to gauge, mislabeling `_count`-suffixed counters as 
histograms, and splitting summaries into two conflicting `# TYPE` lines. 
Capture the type with the Prometheus `expfmt` parser, store it in the flight 
recorder, thread it through a new  [...]
+- Trace storage metrics now expose the `storage` sub-scope, matching the 
`stream_storage_*` naming. The `StorageMetricsFactory` for trace switched from 
the root `trace` scope to `trace.storage`, so per-segment inverted-index 
metrics (`inverted_index_total_updates`, `inverted_index_total_doc_count`, 
`inverted_index_total_term_searchers_started`) are now emitted as 
`banyandb_trace_storage_*` instead of `banyandb_trace_*`, aligning the 
dashboard query names. Other trace metrics (`trace_tst_ [...]
+- Fix FODC agent labeling metrics with `node_role="ROLE_UNSPECIFIED"`. The 
agent resolved the node role exactly once at startup via a single 
`GetCurrentNode` poll whose endpoint retries spanned only ~1s; when the sibling 
lifecycle/banyandb gRPC server was not yet listening (`connect: cannot assign 
requested address`) the role fell back to `ROLE_UNSPECIFIED` permanently, so 
most nodes never reported their real `ROLE_DATA`/`ROLE_LIAISON`. Retry the 
initial node-role resolution with exponen [...]
+
+### Chores
+
+- Regenerate expired TLS test certificate with 100-year validity.
+- Set Ginkgo `--repeat` to 0 in the flaky-test workflow so the hourly run 
completes within the 50-minute timeout.
diff --git a/content/quickstart-docker.sh b/content/quickstart-docker.sh
index ce860067cc4..1b37d333aea 100644
--- a/content/quickstart-docker.sh
+++ b/content/quickstart-docker.sh
@@ -21,7 +21,7 @@ set -e
 SW_STORAGE=
 
 SW_VERSION=${SW_VERSION:-10.4.0}
-SW_BANYANDB_VERSION=${SW_BANYANDB_VERSION:-0.10.2}
+SW_BANYANDB_VERSION=${SW_BANYANDB_VERSION:-0.10.3}
 
 usage() {
   echo "Usage: quickstart-docker.sh [-f]"
diff --git a/data/docs.yml b/data/docs.yml
index 4ce32f92f6f..509a67b0491 100644
--- a/data/docs.yml
+++ b/data/docs.yml
@@ -369,9 +369,9 @@
         - version: Latest
           link: /docs/skywalking-banyandb/latest/readme/
           commitId: dda5b5edfda8d90996f37fcb713d8b1035739dd4
-        - version: v0.10.2
-          link: /docs/skywalking-banyandb/v0.10.2/readme/
-          commitId: 55c6007c2fde1637a53deac1a6dfd27e987ba4db
+        - version: v0.10.3
+          link: /docs/skywalking-banyandb/v0.10.3/readme/
+          commitId: 951e00e85b47b46cdabbe3d14e5be4a02b50dd29
     - name: BanyanDB Client Proto
       icon: banyan-db
       description: Protocol definitions in Protobuf/gRPC for BanyanDB clients
diff --git a/data/releases.yml b/data/releases.yml
index dcc16ac17c7..66e3b3873db 100644
--- a/data/releases.yml
+++ b/data/releases.yml
@@ -785,48 +785,48 @@
       icon: banyan-db
       description: The BanyanDB Server
       source:
-        - version: v0.10.2
-          date: May. 6th, 2026
+        - version: v0.10.3
+          date: Jun. 20th, 2026
           downloadLink:
             - name: src
-              link: 
https://www.apache.org/dyn/closer.cgi/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-src.tgz
+              link: 
https://www.apache.org/dyn/closer.cgi/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-src.tgz
             - name: asc
-              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-src.tgz.asc
+              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-src.tgz.asc
             - name: sha512
-              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-src.tgz.sha512
+              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-src.tgz.sha512
       distribution:
-        - version: v0.10.2
-          date: May. 6th, 2026
+        - version: v0.10.3
+          date: Jun. 20th, 2026
           downloadLink:
             - name: tar
-              link: 
https://www.apache.org/dyn/closer.cgi/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-banyand.tgz
+              link: 
https://www.apache.org/dyn/closer.cgi/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-banyand.tgz
             - name: asc
-              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-banyand.tgz.asc
+              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-banyand.tgz.asc
             - name: sha512
-              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-banyand.tgz.sha512
+              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-banyand.tgz.sha512
     - name: BanyanDB Command Line Tool(bydbctl)
       icon: banyan-db
       description: The BanyanDB Command Line Tool, which provides the ability 
to manage BanyanDB.
       source:
-        - version: v0.10.2
-          date: May. 6th, 2026
+        - version: v0.10.3
+          date: Jun. 20th, 2026
           downloadLink:
             - name: src
-              link: 
https://www.apache.org/dyn/closer.cgi/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-src.tgz
+              link: 
https://www.apache.org/dyn/closer.cgi/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-src.tgz
             - name: asc
-              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-src.tgz.asc
+              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-src.tgz.asc
             - name: sha512
-              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-src.tgz.sha512
+              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-src.tgz.sha512
       distribution:
-        - version: v0.10.2
-          date: May. 6th, 2026
+        - version: v0.10.3
+          date: Jun. 20th, 2026
           downloadLink:
             - name: tar
-              link: 
https://www.apache.org/dyn/closer.cgi/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-bydbctl.tgz
+              link: 
https://www.apache.org/dyn/closer.cgi/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-bydbctl.tgz
             - name: asc
-              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-bydbctl.tgz.asc
+              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-bydbctl.tgz.asc
             - name: sha512
-              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.2/skywalking-banyandb-0.10.2-bydbctl.tgz.sha512
+              link: 
https://downloads.apache.org/skywalking/banyandb/0.10.3/skywalking-banyandb-0.10.3-bydbctl.tgz.sha512
     - name: BanyanDB Java Client
       icon: banyan-db
       description: The client implementation for SkyWalking BanyanDB in Java

Reply via email to