Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ArangoError: filesystem full when there's PLENTY of space on mount #8113

Closed
parekhnikunj opened this issue Feb 5, 2019 · 3 comments
Closed
Labels

Comments

@parekhnikunj
Copy link

My Environment

  • ArangoDB Version: 3.3.19
  • Storage Engine: RocksDB
  • Deployment Mode: Single Server
  • Deployment Strategy: Manual Start
  • Configuration: EC2
  • Infrastructure: AWS
  • Operating System: Linux ip-172-20-6-177.us-west-2.compute.internal 4.14.72-73.55.amzn2.x86_64 Changes to the README.md file #1 SMP Thu Sep 27 23:37:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  • Total RAM in your machine: 8GB
  • Disks in use: 4.2GB out of 56 GB SSD
  • Used Package: No idea

Component, Query & Data

Affected feature:

{"message":"filesystem full","name":"ArangoError","stack":"ArangoError: filesystem full\n at new ArangoError (/usr/src/app/node_modules/arangojs/lib/async/error.js:71:21)\n at Object.resolve (/usr/src/app/node_modules/arangojs/lib/async/connection.js:243:32)\n at _hosts.(anonymous function) (/usr/src/app/node_modules/arangojs/lib/async/connection.js:122:26)\n at IncomingMessage.res.on (/usr/src/app/node_modules/arangojs/lib/async/util/request.node.js:48:21)\n at IncomingMessage.emit (events.js:185:15)\n at endReadableNT (_stream_readable.js:1106:12)\n at process._tickCallback (internal/process/next_tick.js:178:19)","code":500}

AQL query (if applicable):

AQL explain (if applicable):

Dataset:

Small 100-200 bytes JSON documents

Size of your Dataset on disk:

4.2 GB

Replication Factor & Number of Shards (Cluster only):

Steps to reproduce

  1. Send following query:
curl --request POST \ --url <endpoint>:8529  \ --header 'content-type: application/json' \ --header 'x-google-token: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJodHRwczovL2N0ei5uei9pZCI6IjYyMzUzZGYzLTc4M2QtNDg2NC1hZDAxLWVlYmMxN2ZjYWZjZSIsImlzcyI6Imh0dHBzOi8vY2lpdGl6ZW4uYXV0aDAuY29tLyIsInN1YiI6ImF1dGgwfDViZTQ5NTdmZWMzMTIzMjBmNTYyMzZhNCIsImF1ZCI6WyJodHRwczovL2FwaS5kZXYuY2lpdGl6ZW4ubmV0Il0sImlhdCI6MTU0OTMyNDE1OCwiZXhwIjoxNTQ5NDEwNTU4LCJhenAiOiJmRmlTTjgyTG13VHl5MWFxM3R6RGR3WWlLeFE4SXJSNSIsInNjb3BlIjoib3BlbmlkIHByb2ZpbGUiLCJndHkiOiJwYXNzd29yZCJ9.sPHwzEb9myFPOY9V2m82nud_Y83g2frpUgQHqy85AXQ' \ --data '{ "foo": "bar" }' ```
--

__Problem__:


__Expected result__:

No ArangoError and above object getting inserted into DB
@ObiWahn
Copy link
Contributor

ObiWahn commented Feb 5, 2019

Please use df -i to make sure you do not have exhausted all available inodes.

@OmarAyo
Copy link
Contributor

OmarAyo commented Feb 11, 2019

Hi @parekhnikunj,

Just sending a quick followup, are you still facing this issue ? if yes please provide the output of df -i

Thanks,

@parekhnikunj
Copy link
Author

parekhnikunj commented Feb 11, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants