- [+] expand all
- GETTING STARTED
- Introduction
- Vespa Overview
- Getting Started
- Quick Start
- Vespa API and Interfaces
- Use case: Shopping
- Use case: Question-Answering
- DOCUMENTS AND SCHEMAS
- Documents
- Schemas
- Parent/Child
- READS AND WRITES
- Reads and Writes
- /document/v1
- Visiting
- Vespa Feeding Client API
- Feed using Hadoop, Pig, Oozie
- Indexing
- Document API
- Document Processing
- Annotations API
- QUERIES
- Query API
- Vespa Query Language
- Grouping Information in Results
- Federation
- Query Profiles
- Geo Search
- Predicate Fields
- Streaming Search
- RANKING AND ML MODELS
- Ranking Introduction
- Rank Features and Expressions
- Multivalue Query Operators
- Tensor User Guide
- Phased Ranking
- Ranking With TensorFlow Models
- Ranking With ONNX Models
- Ranking With XGBoost Models
- Ranking With LightGBM Models
- Stateless model evaluation
- Text Ranking
- Ranking With BM25
- Ranking With nativeRank
- LINGUISTICS AND TEXT PROCESSING
- Linguistics in Vespa
- Query Rewriting
- DEVELOPING APPLICATIONS AND PLUGINS
- Developer Guide
- Application Packages
- Application Testing
- Java Serving Container
- Container Components
- Container Component Types
- Request-Response Processing
- Searcher Development
- Document Processor Development
- Developing Web Service Applications
- Component Injection
- Chained Components
- Building OSGi Bundles
- OSGi Bundle Maven Plugin
- Versioning in the Container
- Using ZooKeeper
- CONFIGURATION
- Configuration Intro
- Deploy API
- HTTP Config API
- Config API
- Developing Config Model Plugins
- RESULT FORMATS
- Document Summaries
- Search Result Renderers
- Page Templates
- THE CONTENT LAYER
- Elastic Vespa
- Proton
- Content Nodes and States
- Consistency Model
- Distribution Algorithm
- Buckets
- State API
- PERFORMANCE AND TUNING
- Serving Sizing Guide
- Feed Sizing Guide
- Sizing Examples
- Document Attributes
- Benchmarking
- Profiling the Search Container
- Container Tuning
- Rate-Limiting Search Requests
- OPERATIONS AND PROCEDURES
- Live Vespa upgrade procedure
- Administrative Procedures
- Vespa Command-line Tools
- Vespa Metrics
- Log Files
- Files, Processes and Ports
- Inspecting Vespa Java Services
- Docker Containers in Production
- Securing a Vespa installation
- CONFIGURATION REFERENCE
- Application Package Reference
- Schema Reference
- Services Configuration (services.xml)
- Indexing Language
- Custom Configuration File Reference
- RANKING REFERENCE
- Ranking Expressions
- Tensor Evaluation Reference
- nativeRank Reference
- Rank Feature Reference
- String Segment Match
- Rank Feature Configuration
- Rank Types
- Stateless Model Reference
- QUERIES AND RESULTS REFERENCE
- Query API Reference
- Query Language Reference
- Simple Query Language Reference
- Select Reference
- Grouping Reference
- Sorting Reference
- Query Profile Reference
- Semantic Rule Language Reference
- Default JSON Result Format
- Page Templates Syntax
- DOCUMENT FORMAT AND LANGUAGES REFERENCE
- Document JSON Format
- Document Field Path Syntax
- Document Selector Language
- ABOUT THIS SITE
- Documentation Conventions
- Contributing to Vespa
hosts.xml
hosts.xml is a configuration file in an application package. Elements:
hosts host [name] aliasThe purpose of hosts.xml is to add aliases for real hostnames to self-defined aliases. The aliases are used in services.xml to map service instances to hosts. It is only needed when deploying to multiple hosts.
host
Subelements:
Example:
<?xml version="1.0" encoding="utf-8" ?> <hosts> <host name="myserver0.mydomain.com"> <alias>SEARCH0</alias> <alias>CONTAINER0</alias> </host> <host name="myserver1.mydomain.com"> <alias>SEARCH1</alias> <alias>CONTAINER1</alias> </host> </hosts>
alias
Alias used in services.xml to refer to the host.