| 0 |
Current and proposed deployment of Openlibrary hardware. NA means the machine does not exist. |
0 |
Current and proposed deployment of Openlibrary hardware. NA means the machine does not exist. |
| ... |
|
... |
|
| 9 |
<tr><td>Wiki-beta</td><td>WWW apps for production and staging, plus mercurial repo, plus some development stuff</td><td>WWW app, production only. I guess the hg repo can stay.</td></tr> |
9 |
<tr><td>Wiki-beta</td><td>WWW apps for production and staging, plus mercurial repo, plus some development stuff</td><td>WWW app, production only. I guess the hg repo can stay.</td></tr> |
| 10 |
<tr><td>ia311530</td><td>Development</td><td>Bibliographic solr primary, bibliographic search API backup</td></tr> |
10 |
<tr><td>ia311530</td><td>Development</td><td>Bibliographic solr web primary, bibliographic search API backup</td></tr> |
| 11 |
<tr><td>ia311538</td><td>Development, pdregistry solr</td><td>Bibliographic solr backup, bibliographic search API primary</td></tr> |
11 |
<tr><td>ia311538</td><td>Development, pdregistry solr</td><td>Bibliographic web solr backup, bibliographic search API primary</td></tr> |
| 12 |
<tr><td>Apollonius</td><td>Development</td><td>Upgrade hardware and use for postgres database</td></tr> |
12 |
<tr><td>Apollonius</td><td>Development</td><td>Upgrade hardware and use for postgres database</td></tr> |
| ... |
|
... |
|
| 33 |
|
33 |
|
| 34 |
6. I also propose running the bibliographic search API on the backup for the main solr server and vice versa, i.e. when both servers are up we would handle API and web requests on separate machines. That is because of the potentially higher level of API traffic which on the other hand would be less cpu-intensive (since we don't facet API results in the current design). |
34 |
6. I also propose running the bibliographic search API on the backup for the main solr server and vice versa, i.e. when both servers are up we would handle API and web requests on separate machines. That is because of the potentially higher level of API traffic which on the other hand would be less cpu-intensive (since we don't facet API results in the current design). Note that web and API search indexes are the same, so there would be just one solr on each box despite it being used for two sort-of-different services. |
| 35 |
|
35 |
|
| 36 |
7. In the event that a black box really does fail unrecoverably, it can be replaced with a red box. |
36 |
7. In the event that a black box really does fail unrecoverably, it can be replaced with a red box. |
| 37 |
|
37 |
|
| 38 |
8. This number of machines is getting large enough to start needing more serious automatic management than we currently have. That's outside the scope of this page. Also not addressed is remote replication, which we also ought to think about. |
38 |
8. This number of machines is getting large enough to start needing more serious automatic management than we currently have. That's outside the scope of this page. Also not addressed is remote replication, which we also ought to think about. |
|
