Skip to content

Full text search engine powering Alexandria.org - the open search engine.

License

Notifications You must be signed in to change notification settings

alexandria-org/alexandria

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Alexandria.org

  1. Coding Rules
  2. Full text indexes
  3. Hash table

Build instructions with docker

  1. Checkout repo WINDOWS USERS: You need to run 'git config --global core.autocrlf false' before checking out the repository
git clone git@github.com:alexandria-org/alexandria.git
  1. Build docker image
docker build . -t alexandria
  1. Run container
docker container run --name alexandria -v ${PWD}:/alexandria -it -d alexandria
  1. Attach to container.
docker exec -it alexandria /bin/bash
  1. Navigate to directory
cd /alexandria
  1. Initialize docker
scripts/init-docker.sh
  1. Configure with cmake
mkdir build; cd build; cmake ..
  1. Build all
make -j4
  1. Run test suite
./run_tests

How to build manually (not recommended)

  1. Configure the system (Tested on Ubuntu 20.04)
# Will alter your system and install dependencies with apt.
./scripts/install-deps.sh

# Will download and build zlib, aws-lambda-cpp and aws-sdk-cpp will only alter the local directory.
./scripts/build-deps.sh
  1. Build with cmake
mkdir build
cd build

cmake .. -DCMAKE_BUILD_TYPE=Debug
or
cmake .. -DCMAKE_BUILD_TYPE=Release

make -j24
  1. Download test data to local server. To run the test suite you need to install nginx and pre-download all the data: Configure local nginx test data server

  2. Create output directories. Note, this will create a bunch of directories in the /mnt so make sure you don't have anything there.

./scripts/prepare-output-dirs.sh
  1. Run the test suite
cd build
make run_tests -j24
./run_tests

Notes

On nodes with spinning disks we should turn off energy saving:

hdparm -B 255 /dev/sda

Debugging notes

Debugging scraper with gdb:

By default, gdb captures SIGPIPE of a process and pauses it. However, some program ignores SIGPIPE. So, the default behavour of gdb is not desired when debugging those program. To avoid gdb stopping in SIGPIPE, use the folloing command in gdb: handle SIGPIPE nostop noprint pass