Using local fs location for gateway. should be changed to be a shared location across nodes – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Using local fs location for gateway. should be changed to be a shared location across nodes ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories and repository-azure.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “using local fs location for gateway; should be changed to be a shared location across nodes” classname is FsRepository.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     public FsRepository(RepositoryName name; RepositorySettings repositorySettings; ThreadPool threadPool; IndexShardRepository indexShardRepository) throws IOException {
        super(name.getName(); repositorySettings; indexShardRepository);
        File locationFile;
        String location = repositorySettings.settings().get("location"; componentSettings.get("location"));
        if (location == null) {
            logger.warn("using local fs location for gateway; should be changed to be a shared location across nodes");
            throw new RepositoryException(name.name(); "missing location");
        } else {
            locationFile = new File(location);
        }
        blobStore = new FsBlobStore(componentSettings; threadPool; locationFile);




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content