change to use databendlabs

README.md

@@ -19,7 +19,7 @@
 
 This project intends to improve raft as the next-generation consensus protocol for distributed data storage systems (SQL, NoSQL, KV, Streaming, Graph ... or maybe something more exotic).
 
-Currently, openraft is the consensus engine of meta-service cluster in [databend](https://github.com/datafuselabs/databend).
+Currently, openraft is the consensus engine of meta-service cluster in [databend](https://github.com/databendlabs/databend).
 
 
 - 🚀 **Get started**:
@@ -143,7 +143,7 @@ For benchmark detail, go to the [./cluster_benchmark](./cluster_benchmark) folde
 
 # Who use it
 
-- [Databend](https://github.com/datafuselabs/databend) - The Next-Gen Cloud [Data+AI] Analytics
+- [Databend](https://github.com/databendlabs/databend) - The Next-Gen Cloud [Data+AI] Analytics
 - [CnosDB](https://github.com/cnosdb/cnosdb) - A cloud-native open source distributed time series database.
 - [yuyang0/rrqlite](https://github.com/yuyang0/rrqlite) - A rust implementation of [rqlite](https://github.com/rqlite/rqlite).
 - [raymondshe/matchengine-raft](https://github.com/raymondshe/matchengine-raft) - A example to demonstrate how openraft persists snapshots/logs to disk.

book.toml

@@ -1,5 +1,5 @@
 [book]
-authors = ["datafuselabs"]
+authors = ["databendlabs"]
 language = "en"
 multilingual = false
 src = "guide/src"

openraft/src/docs/getting_started/getting-started.md

@@ -230,7 +230,7 @@ To receive and handle these requests, there should be a server endpoint for each
 When the server receives a Raft RPC, it simply passes it to its `raft` instance and replies with the returned result:
 [Mem KV Server](https://github.com/databendlabs/openraft/blob/main/examples/raft-kv-memstore/src/network/raft.rs).
 
-For a real-world implementation, you may want to use [Tonic gRPC](https://github.com/hyperium/tonic) to handle gRPC-based communication between Raft nodes. The [databend-meta](https://github.com/datafuselabs/databend/blob/6603392a958ba8593b1f4b01410bebedd484c6a9/metasrv/src/network.rs#L89) project provides an excellent real-world example of a Tonic gRPC-based Raft network implementation.
+For a real-world implementation, you may want to use [Tonic gRPC](https://github.com/hyperium/tonic) to handle gRPC-based communication between Raft nodes. The [databend-meta](https://github.com/databendlabs/databend/blob/6603392a958ba8593b1f4b01410bebedd484c6a9/metasrv/src/network.rs#L89) project provides an excellent real-world example of a Tonic gRPC-based Raft network implementation.
 
 
 ### Implement [`RaftNetworkFactory`].

openraft/src/engine/engine_impl.rs

@@ -660,7 +660,7 @@ where C: RaftTypeConfig
     /// Check if a raft node is in a state that allows to initialize.
     ///
     /// It is allowed to initialize only when `last_log_id.is_none()` and `vote==(term=0,
-    /// node_id=0)`. See: [Conditions for initialization](https://datafuselabs.github.io/openraft/cluster-formation.html#conditions-for-initialization)
+    /// node_id=0)`. See: [Conditions for initialization](https://databendlabs.github.io/openraft/cluster-formation.html#conditions-for-initialization)
     fn check_initialize(&self) -> Result<(), NotAllowed<C>> {
         if !self.state.is_initialized() {
             return Ok(());