mirror of
https://github.com/hanzoai/s3.git
synced 2026-11-03 03:07:41 +00:00
zooqueen
dd74d3e6d6
hanzoai/s3 was an AGPL-3.0 MinIO fork whose network-copyleft blocks embedding
and reselling as a managed service. Replace it wholesale with a fork of
SeaweedFS (github.com/seaweedfs/seaweedfs, Apache-2.0, Go) which ships a
built-in S3 gateway + Filer.
- License: AGPL-3.0 -> Apache-2.0 (upstream LICENSE kept verbatim, incl.
"Copyright 2025 Chris Lu"); NOTICE added crediting SeaweedFS. No AGPL/BUSL/
SSPL/GPL or enterprise ("ee") files remain.
- Module: go.mod path set to github.com/hanzoai/s3 with a self-replace
(replace github.com/seaweedfs/seaweedfs => ./) so the ~1800 internal Go files
keep their upstream import paths with zero churn. Internal identifiers and
import paths are intentionally NOT renamed.
- CLI rebrand: the binary is built as `s3` (was `weed`); root usage, per-command
help/usage/flag strings, shell autocomplete program name, and the product name
in CLI output now read "Hanzo S3" / `s3`. Users never see `weed`.
(e.g. `s3 server`, `s3 filer`, `s3 master`, `s3 volume`, `s3 s3`, `s3 mount`.)
- Build: `make` (or `go build -o s3 ./weed`) builds the `s3` binary green;
`cmd/weed-db` and `cmd/weed-sql` also build; `go vet ./weed/command/` clean.
- README/LLM.md rewritten for Hanzo S3; AGENTS.md/CLAUDE.md symlinks preserved.
- Dropped a 33MB prebuilt Mach-O `stress` binary upstream had committed; `.gitignore`
updated to ignore the `s3` build output.
44 lines
1.2 KiB
Go
44 lines
1.2 KiB
Go
package pub_balancer
|
|
|
|
/*
|
|
Sequence of operations to ensure ordering
|
|
|
|
Assuming Publisher P10 is publishing to Topic Partition TP10, and Subscriber S10 is subscribing to Topic TP10.
|
|
After splitting Topic TP10 into Topic Partition TP11 and Topic Partition TP21,
|
|
Publisher P11 is publishing to Topic Partition TP11, and Publisher P21 is publishing to Topic Partition TP21.
|
|
Subscriber S12 is subscribing to Topic Partition TP11, and Subscriber S21 is subscribing to Topic Partition TP21.
|
|
|
|
(The last digit is ephoch generation number, which is increasing when the topic partitioning is changed.)
|
|
|
|
The diagram is as follows:
|
|
P10 -> TP10 -> S10
|
|
||
|
|
\/
|
|
P11 -> TP11 -> S11
|
|
P21 -> TP21 -> S21
|
|
|
|
The following is the sequence of events:
|
|
1. Create Topic Partition TP11 and TP21
|
|
2. Close Publisher(s) P10
|
|
3. Close Subscriber(s) S10
|
|
4. Close Topic Partition TP10
|
|
5. Start Publisher P11, P21
|
|
6. Start Subscriber S11, S21
|
|
|
|
The dependency is as follows:
|
|
2 => 3 => 4
|
|
| |
|
|
v v
|
|
1 => (5 | 6)
|
|
|
|
And also:
|
|
2 => 5
|
|
3 => 6
|
|
|
|
For brokers:
|
|
1. Close all publishers for a topic partition
|
|
2. Close all subscribers for a topic partition
|
|
3. Close the topic partition
|
|
|
|
*/
|