Recommend ZK for Pulsar standalone

[visortelle]

✅ Contribution Checklist

• I read the contribution guide
• I updated the versioned docs

---

• Recommend considering using ZooKeeper for Pulsar standalone. RocksDB metadata store sometimes doesn't work after restarting a container: Bookie handle is not available - ledger=22 - operation=Failed to read entry - entry=0 pulsar#20985 (comment)
• Changed argument order for chown command because it didn't work on MacOS

[merlimat]

According to the issue it doesn't look to be a RocksDB metadata issue, rather a BK bug

[merlimat]

I don't think it's a good idea to recommend not to use a default setting. If we have a bug in default configuration, we must fix it. If it cannot be fixed, we will have to change the defaults.

[visortelle]

It would be the best solution. @lhotari 's concern was that:

it would have to be documented since many might be using old versions and wondering about the resolution.
The problem in changing the default is that it would break existing "deployments" with data

[lhotari]

I don't think it's a good idea to recommend not to use a default setting. If we have a bug in default configuration, we must fix it. If it cannot be fixed, we will have to change the defaults.

@merlimat I agree. Since we cannot change already released versions and users are hitting problems, I think it's worth documenting the workaround until there's a better solution. It seems that there isn't a nice way to solve this problem.

[lhotari]

I'll merge this PR with the current content. We can come back to this later once there's a better resolution.

[visortelle]

@merlimat you're right. I removed the mention of the wrong tracking issue.

I'm a little confused about the different problems I encountered with Pulsar standalone. The issue with RocksDB I have:
apache/pulsar#15896 (comment)

Error generating ledger id: org.apache.pulsar.metadata.api.MetadataStoreException: org.rocksdb.RocksDBException: TimedOut(LockTimeout)

I had an app that concurrently created 2 tenants, a few namespaces, and about 15 topics with roughly 50 partitions in total and created a single producer and consumer for each topic.

The problem was fixed after I started to create resources sequentially.

I can share a docker image with the app where the issue can be reproduced if it makes sense.
Note: Now it creates about 60 topics with roughly 210 partitions. It has quite a small load for each topic:

[lhotari]

I made a separate commit 96cdbf2 for fixing the chown

[lhotari]

LGTM, although as discussed there isn't a good solution and it's better to have the workaround documented.