Skip to content

Commit 1583995

Browse files
committed
Scale: Fix image URLs s/Discourse/GitHub/
1 parent 7aac0f4 commit 1583995

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

docs/admin/clustering/scale/auto.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ One of the unique features of CrateDB is that it is a multi-model distributed SQ
1717

1818
CrateDB's fully managed solution comes with a REST API which enables you to automate a lot of tasks. As CrateDB is world famous for its, highly scalable architecture, one of those tasks could be to scale a cluster out (horizontally) when needed, during a peak, for example, and back when possible to reduce costs.
1919

20-
![CrateDB-Scaling-Process|690x389](https://global.discourse-cdn.com/flex020/uploads/crate/original/2X/a/a10f95850f05a064ce022b4ccca45131c1c481cd.png){w=690px align=center}
20+
![CrateDB-Scaling-Process|690x389](https://github.com/user-attachments/assets/f9ba40ff-4cee-45f5-8bfb-d4125c037ea0){w=690px align=center}
2121

2222
This small blog shows how you can use the API to scale out and scale back a cluster when needed.
2323

docs/admin/clustering/scale/demand.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ INSERT INTO test (ts) VALUES ('2022-11-18'), ('2022-11-19');
4040
```
4141

4242
The shards will initially look like this:
43-
![image|690x167](https://global.discourse-cdn.com/flex020/uploads/crate/original/1X/ac18a9cb507201d8e54771e320501f4aaac0eb16.png)
43+
![Image](https://github.com/user-attachments/assets/045f66fc-4134-4363-a37a-711a449c43d5)
4444

4545
## Before deploying extra nodes
4646

@@ -128,7 +128,7 @@ INSERT INTO test (ts) VALUES
128128

129129
We can see that data from before the event stays on the baseline nodes while data for the days of the event gets distributed over all nodes:
130130

131-
![image|690x220](https://global.discourse-cdn.com/flex020/uploads/crate/original/1X/b1c1a1ac42ac3d0eb644529e57c4b9c49eae2e87.png)
131+
![Image](https://github.com/user-attachments/assets/b0f294a4-ff2b-4b84-8a34-aa782cb5a300)
132132

133133
The same can be checked programmatically with this query:
134134

@@ -164,7 +164,7 @@ Let’s confirm it:
164164
INSERT INTO test (ts) VALUES ('2022-12-19'), ('2022-12-20');
165165
```
166166

167-
![image|690x73](https://global.discourse-cdn.com/flex020/uploads/crate/original/1X/72b9f0bd28fb88402ea951f9f8a9a15c7c491ad2.png)
167+
![image|690x73]
168168

169169
When we are ready to decommission the temporary nodes, we need to move the data collected during the days of the event.
170170

0 commit comments

Comments
 (0)