Remote storage become 1GB after re-login

MFYDev commented 1 month ago

Have you read a contributing guide?

[X] I have read CONTRIBUTING.md
[X] I have searched the existing issues and didn't find any that were similar
[X] I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

deploy the latest version, create a vault, login
see the remote storage is 1TB which is correct
log out of the vault
log in again
remote storage become 1GB

Expected Behavior

remote storage should always be the 1TB

Steps To Reproduce

deploy the latest version, create a vault, login
see the remote storage is 1TB which is correct
log out of the vault
log in again
remote storage become 1GB

Environment

- OS: Docker Compose remote ubuntu with Windows latest beta client
- Version:prod

Anything else?

No response

MFYDev commented 1 month ago

Forgot to add, delete the local data folder and relogin, the remote storage become 1GB

mighty-sponge commented 1 month ago

Hi, I tried following your steps and I failed to detect the change of remote storage from 1TB to 1GB. I did login/logout, delete local and even minio data. As a result, I always got 1TB of remote storage.

To better understand the issue, please try again on the latest current beta (v0.41.39-beta) and also do a git pull of the current main branch. If that doesn't help, please describe in detail the steps to reproduce the problem and if you changed the .env file, specify which values.

chiyi4488 commented 1 month ago

Hello @mighty-sponge,

My current .env setting is: ANY_SYNC_FILENODE_DEFAULT_LIMIT=1099511627776

As I understand it, this should be setting the limit to 1TB, but my Anytype shows only 1GB for Remote Storage. Am I misunderstanding the configuration?

By the way, my any-sync was deployed with the stable version just yesterday.

lslvxy commented 1 month ago

Hello @mighty-sponge,

My current .env setting is: ANY_SYNC_FILENODE_DEFAULT_LIMIT=1099511627776

As I understand it, this should be setting the limit to 1TB, but my Anytype shows only 1GB for Remote Storage. Am I misunderstanding the configuration?

By the way, my any-sync was deployed with the stable version just yesterday.

Same as me

fb929 commented 3 weeks ago

So I also cannot reproduce this. my versions:

any-sync-dockercompose - v5.0.3

any-sync-* server versions:

$ docker-compose ps --format "{{.Image}}"
ghcr.io/anyproto/any-sync-consensusnode:v0.1.7
ghcr.io/anyproto/any-sync-coordinator:v0.3.26
ghcr.io/anyproto/any-sync-filenode:v0.6.5
ghcr.io/anyproto/any-sync-node:v0.3.34
ghcr.io/anyproto/any-sync-node:v0.3.34
ghcr.io/anyproto/any-sync-node:v0.3.34
minio/minio:RELEASE.2024-07-04T14-25-45Z
mongo:7.0.2
ghcr.io/anyproto/any-sync-tools:latest
redis/redis-stack-server:7.2.0-v6

client version - 0.42.3 (macos)

fb929 commented 3 weeks ago

Forgot to add, delete the local data folder and relogin, the remote storage become 1GB

@MFYDev what exactly do you mean? Which specific folder are you deleting?

MARTINrichard05 commented 3 days ago

I get the same thing. I install the server using the getting started instructions, i create a space, then, log out, log in, and the limit goes to 1gb

fb929 commented 2 days ago

I get the same thing. I install the server using the getting started instructions, i create a space, then, log out, log in, and the limit goes to 1gb

Could you please send the versions of any-sync-dockercompose and the configuration parameters?

Please provide the output of the following commands:

docker-compose ps --no-trunc
cat .env.override
cat docker-compose.override.yml

MARTINrichard05 commented 2 days ago

the container list :

e352345dc7e0   ghcr.io/anyproto/any-sync-node:v0.3.34               "/bin/sh -c '/bin/an…"   24 hours ago   Up 24 hours             443/tcp, 0.0.0.0:1002->1002/tcp, :::1002->1002/tcp, 0.0.0.0:1012->1012/udp, :::1012->1012/udp, 0.0.0.0:8002->8000/tcp, :::8002->8000/tcp, 0.0.0.0:8082->8080/tcp, :::8082->8080/tcp   any-sync-dockercompose-any-sync-node-2-1
c21e7771d879   ghcr.io/anyproto/any-sync-consensusnode:v0.1.7       "/bin/sh -c '/bin/an…"   24 hours ago   Up 24 hours             443/tcp, 8080/tcp, 0.0.0.0:1006->1006/tcp, :::1006->1006/tcp, 0.0.0.0:1016->1016/udp, :::1016->1016/udp, 0.0.0.0:8006->8000/tcp, :::8006->8000/tcp                                    any-sync-dockercompose-any-sync-consensusnode-1
14a54fa68fb3   ghcr.io/anyproto/any-sync-filenode:v0.7.2            "/bin/any-sync-filen…"   24 hours ago   Up 24 hours             443/tcp, 8080/tcp, 0.0.0.0:1005->1005/tcp, :::1005->1005/tcp, 0.0.0.0:1015->1015/udp, :::1015->1015/udp, 0.0.0.0:8004->8000/tcp, :::8004->8000/tcp                                    any-sync-dockercompose-any-sync-filenode-1
eee22d4cbf86   ghcr.io/anyproto/any-sync-node:v0.3.34               "/bin/sh -c '/bin/an…"   24 hours ago   Up 24 hours             443/tcp, 0.0.0.0:1003->1003/tcp, :::1003->1003/tcp, 0.0.0.0:1013->1013/udp, :::1013->1013/udp, 0.0.0.0:8003->8000/tcp, :::8003->8000/tcp, 0.0.0.0:8083->8080/tcp, :::8083->8080/tcp   any-sync-dockercompose-any-sync-node-3-1
7054c9d6f36e   ghcr.io/anyproto/any-sync-node:v0.3.34               "/bin/sh -c '/bin/an…"   24 hours ago   Up 24 hours             443/tcp, 0.0.0.0:1001->1001/tcp, :::1001->1001/tcp, 0.0.0.0:1011->1011/udp, :::1011->1011/udp, 0.0.0.0:8001->8000/tcp, :::8001->8000/tcp, 0.0.0.0:8081->8080/tcp, :::8081->8080/tcp   any-sync-dockercompose-any-sync-node-1-1
2aefa8b9da7d   ghcr.io/anyproto/any-sync-coordinator:v0.3.26        "/bin/any-sync-coord…"   24 hours ago   Up 24 hours             443/tcp, 8080/tcp, 0.0.0.0:1004->1004/tcp, :::1004->1004/tcp, 0.0.0.0:1014->1014/udp, :::1014->1014/udp, 0.0.0.0:8005->8000/tcp, :::8005->8000/tcp                                    any-sync-dockercompose-any-sync-coordinator-1
12065f5b4724   mongo:4.4.29                                         "docker-entrypoint.s…"   24 hours ago   Up 24 hours (healthy)   0.0.0.0:27001->27001/tcp, :::27001->27001/tcp, 27017/tcp                                                                                                                              any-sync-dockercompose-mongo-1-1
877cb5afa9e7   redis/redis-stack-server:7.2.0-v6                    "redis-server --port…"   24 hours ago   Up 24 hours (healthy)   0.0.0.0:6379->6379/tcp, :::6379->6379/tcp                                                                                                                                             any-sync-dockercompose-redis-1
fc29d17329a9   minio/minio:RELEASE.2024-07-04T14-25-45Z             "/usr/bin/docker-ent…"   24 hours ago   Up 24 hours (healthy)   0.0.0.0:9000-9001->9000-9001/tcp, :::9000-9001->9000-9001/tcp                                                                                                                         any-sync-dockercompose-minio-1

richou@server:~/any-sync-dockercompose$ cat .env.override
EXTERNAL_LISTEN_HOSTS=192.168.1.180
MONGO_VERSION=4.4.29
STORAGE_DIR="/mnt/ssd/anytype_data"

richou@server:~/any-sync-dockercompose$ cat docker-compose.override.yml
services:
  mongo-1:
    healthcheck:
      test: echo "rs.initiate({_id:'${MONGO_REPLICA_SET}',members:[{_id:0,host:\"mongo-1:${MONGO_1_PORT}\"}]}).ok || rs.status().ok" | mongo --port ${MONGO_1_PORT} --quiet

fb929 commented 2 days ago

And can You also show a video from the client please? a full cycle: create a new vault, show the limit and sync status, log out and log in again, and show the limit and sync status again.

anyproto / any-sync-dockercompose