[
https://issues.apache.org/jira/browse/UNOMI-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882138#comment-16882138
]
Michele Riva commented on UNOMI-237:
------------------------------------
Hi, at the moment I am not able to share some logs for that particular problem,
I'll try by stressing out the system while listening the Karaf logs.
Which kind of tuning would you suggest on ElasticSearch?
> 204 status code when under high traffic
> ---------------------------------------
>
> Key: UNOMI-237
> URL: https://issues.apache.org/jira/browse/UNOMI-237
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Affects Versions: 1.4.0
> Reporter: Michele Riva
> Priority: Major
>
> Hi all,
> I've noticed that after spawning 10.000/20.000 consecutive POST requests to
> /cxs/profiles/create, Unomi begins to return a 204 status code and the
> profile can not be created.
> I've acted adding a retry strategy on my client, but obviously it slows down
> the system.
> Seems that Unomi can not handle an huge amount of consecutive/concurrent
> requests without an event broker (Kafka/Redis/Rabbit) before it... is there a
> way to guarantee that it will work under high traffic without a broker
> handling the request queue for it?
> thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
