Sponsors SeaweedFS via Patreon https://www.patreon.com/seaweedfs

Describe the bug
README#Installation-guide Step 3 contains command:
go get github.com/chrislusf/seaweedfs/weed

It builds weed here without compiler errors, but weed binary panicing same as in #1058 :

panic: /debug/requests is already registered. You ma

Looks like the error code in braft::Status is mapped as error codes in the C++ standard. For example, I saw this in closure_queue.cpp:

(*it)->status().set_error(EPERM, "leader stepped down");

Similar logic is scattered around the code base.

I am wondering whether we have any documentation for all the possible error codes (i.e. the mapping)?

As described on the latter part of leo-project/leofs#1156 (comment),

You are right. it's best practice to take the backup whenever the cluster topology changes.

This should be documented and also we have to mention that users should take the backup whenever the records in S3 related table (users, endpoints, buckets) change.

Problem description
Documentation for ScalingPolicy.byDataRate does not clearly indicate whether targetKBps uses units of 1000 bytes or 1024 bytes.

Problem location
Pravega client, ScalingPolicy.java

Suggestions for an improvement
Determine the units used and update the documentation.

Best I can tell, all executables produce 0 as a Linux exit code, regardless how wrongly they were invoked. That's a problem, e.g. when attempting to run the gateway as a systemd.service.

Specific use case: storj-gateway.service runs gateway_xxx_yyy --config-dir does-not-exist. Systemd happily reports that everything is fine -- which of course it is not, but it cannot tell unless the exit co

I'm currently testing the 1.0.1 release and discovered that the --wq-threads options isn't documented anywhere.
The only information I was able to find is in the commit log (c84b4fc1021df87bba161b758fb068a4333b9ad6).

"If the option isn't passed, sheep uses unlimited queues but it is highly dicouraged for stable and high IOPS."

It would be great to add something about this option. Moreover t

Not sure if it's worth adding to the documentation but I found I had to add the following to the end of the fstab command otherwise the system would not boot cleanly.

,x-systemd.mount-timeout=30,_netdev

The line in fstab now looks like

mfsmount /mnt/mymnt fuse mfssubfolder=mydir,allow_other,x-systemd.mount-timeout=30,_netdev

I think it was trying to mount mooseFS before it had fini

The latest sizing recommendation is that bluestore DB partitions should not be smaller then 4% of the size of the data partition. We should consider this in our default deployments, maybe even check if this recommendation is not met.

Messages like 'You can audit file to make sure file integrity' are currently in two files, so importing constants seems like an easy way to edit them in two places at once. JS communities leaders in React/Redux also seem to like using constants in general, so we should probably consider using them in additional situations [like for numbers](https://e

collections can be assigned a number of handlers/processors, who can

• perform data encryption
• manage document TTL (retention policy)
• manage document accessibility

in, general, this is to make collections a common mechanism to perform some actions on group of documents. the set of actions must be extendable and it must be possible to develop and register new handlers/processors