rootdir_geo_replication
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
rootdir_geo_replication [2022/02/07 15:20] yves |
rootdir_geo_replication [2023/11/21 16:15] (current) chris |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Root directories and geo-replication ===== | ===== Root directories and geo-replication ===== | ||
| - | Cloud providers typically offers different geographical data centers, and during setup you can point ti any one of them. When you want to offer global access to WSI data then, you can have data stored in multiple zones. | + | Cloud providers typically offer different geographical data centers. During setup you can point to any one of these. Then when you want to offer global access to WSI data, you can store the data in multiple zones. |
| {{ ::rootdir_scenarios1.png?nolink&400 |}} | {{ ::rootdir_scenarios1.png?nolink&400 |}} | ||
| Line 7: | Line 7: | ||
| The different instances of PMA.core in these zones can share a single database, yet the mounting points of the root directories can refer to different endpoints in different locales. | The different instances of PMA.core in these zones can share a single database, yet the mounting points of the root directories can refer to different endpoints in different locales. | ||
| - | Any time the end-user requests a particular slide from a particular location, PMA.core automatically selects the storage location closest to the accessed node. | + | Any time an end-user requests a particular slide from a particular location, PMA.core automatically selects the storage location closest to the accessed node. |
| + | See also [[settings_instances|Instance settings]]. | ||
rootdir_geo_replication.1644236434.txt.gz · Last modified: 2022/02/07 15:20 by yves
