[
https://issues.apache.org/jira/browse/ARTEMIS-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537408#comment-17537408
]
Gary Tully commented on ARTEMIS-3832:
-------------------------------------
personally, I think a container image the used a simple jar and embedded broker
with properties config is the way to go. It does not make sense to me that an
image would need to go through the bare metal getting started path of artemis
create etc.
The existing embedded broker has some sensible defaults that can be build on.
There is still some work to complete to cover all the bases with properties
config, RBAC still looks odd... but I think it has promise.
> artemis create - Add option to configure address-full-policy
> ------------------------------------------------------------
>
> Key: ARTEMIS-3832
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3832
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 2.22.0
> Reporter: Claus Ibsen
> Priority: Major
>
> When trying out Artemis such as via a docker image, then you often run on
> limited disk space - for example I have 20gb assigned for docker.
> However Artemis may notice that its low on disk, and then go into blocking
> mode.
> It would be good if you can configure these options when creating the broker,
> especially as you use a docker file to create the image (no official release
> in docker hub etc).
> Then you can set these options via EXTRA_ARGS in the dockerfile.
> BTW: its the max-disk-usage that triggered my artemis to go into blocking
> mode, because it had detected that there was only 3gb disk left. However when
> you use Artemis for demos/examples/development, then IMHO it would be great
> if Artemis could be easily configured for such use-cases.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
