neo4j-documentation / neo4j-documentation/knowledge-base

Comments on the "Number of open files" page

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
26
Forks
43
PR merge metrics
No merged PRs in 30d

Description

Hi,
I have some comments/suggestions for the "Number of open files" page.

  1. There are currently two pages with similar titles:

    The first one is deprecated and no longer works on RHEL-like distributions. Ideally, it should contain a pointer to the new one.

    The second page states that it's applicable for versions 3.{3,4,5} but it applies to 4.x as well.

  2. On both pages, the configuration for Debian systems seems incorrect. It suggests adding the following to `/etc/security/limits.conf.

    neo4j  soft  nofile  40000
    neo4j  hard  nofile  40000
    

    However, the syntax in the /etc/security/limits.conf file states that the user name should come first, so for most users, neo4j should be something else. A wildcard (*) could also work. (See a Stack Overflow answer on the topic).

  3. The characters denoting smaller than, <=, are interpreted as a ligature and are rendered as a leftwards arrow, . Maybe it's easiest to just use the Unicode instead.

Gabor

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the two linked KB pages, especially the deprecated Number of open files page and the Linux variant. Verify the Neo4j version coverage, Debian limits.conf example, and rendering of <=, then update the documentation so the old page points to the new one and both pages show correct, readable guidance.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
documentation, operating-systems
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.