You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@unomi.apache.org by "Michele Riva (JIRA)" <ji...@apache.org> on 2019/07/09 12:59:00 UTC

[jira] [Updated] (UNOMI-237) 204 status code when under high traffic

     [ https://issues.apache.org/jira/browse/UNOMI-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michele Riva updated UNOMI-237:
-------------------------------
    Affects Version/s: 1.4.0

> 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
>    Affects Versions: 1.4.0
>            Reporter: Michele Riva
>            Priority: Minor
>
> 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)