sunby opened a new issue #11768:
URL: https://github.com/apache/pulsar/issues/11768
**Describe the bug**
I start a pulasr standalone using docker-compose and produce some messages.
Then run `docker-compose down ` and `docker-compose up -d`. Pulsar container
failed to start.
**To Reproduce**
Steps to reproduce the behavior:
1. docker-compose up -d
2. produce messages
3. docker-compose down
4. docker-compose up -d
4. See error
**Expected behavior**
pulsar container restarts successfully
docker-compose.yaml
```
pulsar:
container_name: milvus-pulsar
image: apachepulsar/pulsar:2.6.1
volumes:
- ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/pulsar:/pulsar/data
command: >
/bin/sh -c "
echo "" >> /pulsar/conf/standalone.conf && \
echo "maxMessageSize=104857600" >>
/pulsar/conf/standalone.conf && \
echo "" >> /pulsar/conf/standalone.conf && \
echo "nettyMaxFrameSizeBytes=104857600" >>
/pulsar/conf/standalone.conf && \
sed -i
's/^defaultRetentionTimeInMinutes=.*/defaultRetentionTimeInMinutes=10080/'
/pulsar/conf/broker.conf && \
bin/pulsar standalone"
```
log:
[pulsar-08-25.log](https://github.com/apache/pulsar/files/7043797/pulsar-08-25.log)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
