fd9d4de31d
We had two different, incompatible-with-each-other, and both individually broken, partial implementations of resizing logic. There's the original pre-etcd resize, and then the etcd resize, and neither works, but there's conflicts between the ways they don't work. No attempt to fix this is likely to yield decent results, so instead, we yank them both out entirely, so if we decide to implement resizing (which we will) we won't be confused by stray code pertaining to resizing that's not really hooked up to anything. We're leaving the resize messages in protobuf to avoid renumbering protobuf messages. We rename some of our message types to UNUSED0, etcetera, so that any code still using the old names won't compile, to make sure we get rid of it, but we can't just drop the numbers without breaking rolling restart. The Resize_AddNode tests are removed not just because we don't have resizing, but because they were completely broken anyway and never worked at all. But there's no reason to fix them because they exist to fix the functionality we didn't have and are now removing the vestigial remains of. We also drop the one usage of the AddNode function of Noder, because it was used only by one test code fragment that was creatincg clusters, and that can be done more correctly. There were no other call sites at all. We mark the monitorAntiEntropy function to be ignored by code coverage because it's not actually being covered. There's a separate ticket for removing that entirely. |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .gitignore | ||
| Caddyfile | ||
| Dockerfile | ||
| Makefile | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| tslint.json | ||
| yarn.lock | ||
Connecting to a standalone Pilosa instance
Lattice can run independently (with e.g. yarn start; see below), connecting to any Pilosa instance. Pilosa must be started with the allowed-origins configuration parameter set to communicate with the UI.
CLI: pilosa server --handler.allowed-origins http://localhost:3000
You will need to update the lattice.config.js file and set the hostname and port of your pilosa server, otherwise it will use the browser url. The default pilosa server is localhost:10101
If you will be consistently working in the repo, it may be useful to locally ignore changes to this file to prevent accidental commits by using:
git update-index --assume-unchanged src/lattice.config.js
yarn start
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
Embedding Lattice within Pilosa
Lattice can be embedded within the Pilosa binary, so the UI is fully accessible directly from the server, reducing operational complexity.
If additional build dependencies yarn (brew install yarn and brew upgrade yarn perhaps) and statik (make install-statik) are available on your system, running make generate-statik before make install should produce a Pilosa binary with Lattice embedded. For up to date instructions, check the Pilosa README.