EasySearch FAQ: A Practical Guide to Domestic Search Engine Adoption

1. Product Overview: Lightweight Search Engine

Q1: What is EasySearch and what are its technical characteristics?

Answer: INFINI EasySearch is a distributed search‑oriented database built on Apache Lucene, derived from Elasticsearch 7.10.2 (the last fully open‑source version). The installation package is under 55 MB and focuses on search‑scenario optimization.

It keeps the product simple and easy to use. Deep kernel optimizations fix many upstream issues, increase cluster throughput by 40‑70 %, and greatly improve disk‑compression efficiency while maintaining full API compatibility and achieving better resource utilization.

Q2: Is EasySearch really more lightweight than Elasticsearch?

Answer: Yes, it is genuinely more lightweight.

EasySearch reduces installation package size, memory consumption, startup time, and overall resource usage.

On identical hardware, memory and CPU usage are typically 10‑30 % lower than Elasticsearch, startup speed improves markedly, and disk storage efficiency rises by 20‑40 %. These optimizations make EasySearch especially suitable for resource‑constrained environments and large‑scale deployments.

Q3: Which Elasticsearch use cases can EasySearch replace?

Answer: EasySearch can replace Elasticsearch in almost all scenarios.

Supported use cases include log analysis, full‑text search, real‑time analytics, business search, monitoring alerts, and knowledge graphs. Full API compatibility ensures existing client code, query syntax, and index structures migrate seamlessly with zero code changes.

Whether it is an ELK log‑analysis stack, an e‑commerce search system, or an enterprise knowledge base, EasySearch can directly replace the original Elasticsearch.

Q4: Does EasySearch support OpenSearch? Can it be deployed in a mixed environment?

Answer: In practice, OpenSearch adoption in China is limited. Mixed deployment is possible but must be aligned with concrete business scenarios.

Q5: How to shut down EasySearch safely? What should operators watch for?

Answer: Use kill -15 (SIGTERM) for graceful shutdown to avoid the abrupt termination caused by kill -9 (unless absolutely necessary).

SIGTERM triggers the graceful shutdown process: completing in‑flight requests, flushing memory to disk, and closing network connections to ensure data integrity.

Before shutting down, verify cluster status to ensure no critical operations are running, back up important data, configure process monitoring for abnormal exit alerts, and confirm the process has fully stopped via ps and port checks.

Q6: How does EasySearch perform on domestic ARM CPUs? Is stability guaranteed?

Answer: EasySearch fully supports ARM architectures, with dedicated optimizations for Kunpeng and Feiteng CPUs. Performance on ARM is essentially on par with x86 platforms.

It has passed compatibility certifications on domestic operating systems such as Galaxy Kylin and UnionTech UOS, and can handle petabyte‑scale data, providing stable search services for finance, telecom, and manufacturing sectors.

The source code is fully自主可控 (self‑controlled), and technical support is responsive, ensuring long‑term sustainability in国产化 (domestic) environments.

2. Compatibility Analysis: Substitution Feasibility

Q3: Which Elasticsearch scenarios can EasySearch replace?

EasySearch is applicable to virtually all Elasticsearch use cases, including log analysis, full‑text search, real‑time analytics, business search, monitoring alerts, and knowledge graphs. It maintains complete API compatibility, allowing existing client code, query statements, and index structures to migrate without modification.

3. Operations Management: Production‑Environment Practices

Q5: How to safely shut down EasySearch? Operational considerations?

Use kill -15 (SIGTERM) for graceful shutdown, avoiding kill -9 unless necessary. SIGTERM ensures in‑flight requests finish, memory flushes to disk, and network connections close, preserving data integrity.

Before shutdown, check cluster health, back up critical data, set up recovery mechanisms, and monitor processes to alert on abnormal exits. Verify complete termination via ps and port checks.

Q6: Performance and stability on domestic ARM CPUs

EasySearch fully supports ARM CPUs, with specific optimizations for Kunpeng and Feiteng. Performance on ARM matches that on x86, and it has passed certifications on Galaxy Kylin and UnionTech UOS, handling PB‑level data for finance, telecom, and manufacturing workloads.

4. Typical Scenarios: Migration and Selection

Scenario 1: Elasticsearch Domesticization

Standard migration workflow from an existing ES cluster to EasySearch:

Assess current cluster size and configuration.

Deploy EasySearch in parallel for functional verification.

Migrate data via snapshot restore or real‑time sync tools.

Switch application connection strings to the new cluster.

Perform targeted tuning based on workload characteristics.

The entire process requires zero code changes, ensuring business continuity.

Scenario 2: New Project Technology Selection

For new projects, especially within domestic enterprises, EasySearch offers clear advantages:

No new skill learning required – full ES API compatibility.

Better performance on the same hardware.

Free open‑source license reduces licensing costs.

Localized Chinese tokenization, pinyin search, and simplified‑traditional conversion.

Self‑controlled source code avoids vendor lock‑in.

5. Performance Tuning: Production Optimization

Deployment Optimization Points

EasySearch supports Docker‑Compose for rapid deployment, simplifying installation and environment standardization.

Production deployment requires system parameter tuning: allocate CPU, memory, and storage wisely; configure cluster topology and network policies.

Use INFINI Console for comprehensive cluster monitoring and multi‑dimensional alerts (health, disk space, response time, node failures). Adjust JVM parameters, index settings, and shard strategies based on workload to fully exploit performance potential.

Domestic Adaptation Strategies

EasySearch has undergone extensive domestic adaptation testing, supporting major domestic operating systems and ARM CPUs.

It provides security and compliance features such as TLS encryption, disk encryption, LDAP authentication, and full audit logging to meet financial and governmental regulations.

Chinese language processing is locally optimized, offering pinyin search, simplified‑traditional conversion, and named‑entity recognition for superior Chinese search experiences.

Summary

EasySearch, as a domestically‑oriented Elasticsearch replacement, demonstrates clear advantages in technical compatibility, performance, and cost control.

Through lightweight design and kernel optimizations, it delivers an advanced yet economically feasible search engine solution. Under the push of the 信创 (information technology innovation) policy, EasySearch provides enterprises with a practical path toward technology autonomy and control.

Reference Resources

Official documentation: https://docs.infinilabs.com/easysearch/

Product page: https://infinilabs.cn/products/easysearch/

Installation guide: https://docs.infinilabs.com/easysearch/main/docs/getting-started/install/

Docker deployment: https://docs.infinilabs.com/easysearch/main/docs/getting-started/install/docker-compose/

Easysearch IK field‑level dictionary dynamic update practice

Logstash 9.X sync write to EasySearch common issues and solutions

Fatal error in thread [main] during EasySearch deployment – troubleshooting

How to scientifically introduce an Elasticsearch domestic replacement in a bid

Video: Cloud‑based CentOS 7 EasySearch deployment

Vector search with EasySearch: theory to practice

Indexing Stanford GloVe vectors in EasySearch for semantic search

High‑availability EasySearch cluster setup on Ubuntu multi‑node guide

Introduction and deployment guide for EasySearch as an Elasticsearch domestic replacement

Reader comments: “Are there domestic Elasticsearch alternatives? The policy now restricts ES usage…”