meilisearch/MeiliSearch

Meilisearch x Azure: current incompatibilities

Open

#4,402 opened on Feb 12, 2024

View on GitHub
 (17 comments) (3 reactions) (1 assignee)Rust (20,887 stars) (733 forks)batch import
bughelp wantedimpacts docsneeds more info

Description

Following this conversation: https://github.com/meilisearch/documentation/issues/2622

Steps to reproduce: https://github.com/meilisearch/documentation/issues/2622#issuecomment-1935458159 Related to this conversation: https://github.com/meilisearch/meilisearch/issues/4123

We need to investigate and understand why Meilisearch works on AWS, DO (etc..) but not on Azure.

Pinging @meilisearch/docs-team here since it's related to an issue on your side

Contributor guide

Tech stack
rust
Domain
cloud
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Meilisearch architectureFamiliarity with Azure and AWS deployment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Start by reproducing the issue using the steps in https://github.com/meilisearch/documentation/issues/2622#issuecomment 1935458159. Then, compare the behavior on AWS and Azure to identify differences in network configuration, DNS resolution, or resource availability. Focus on the Meilisearch HTTP server configuration and cloud provider network policy differences. Check the related issue https://github.com/meilisearch/meilisearch/issues/4123 for prior context.