[
https://issues.apache.org/jira/browse/GEODE-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Bawaskar updated GEODE-3874:
------------------------------------
Description:
We need to provide ability to users to re-deploy async event listeners.
I envision the following workflow to accomplish this:
- User deploys a jar file with the latest implementation of the
AsyncEventListener
- User then issues the following gfsh command: {{alter async-event-queue
--set-async-event-listerner="classname"}} Which should end up replacing the
current instance of the async event listener with a new instance of the given
classname.
was:
We should add a new {{alter async-event-queue}} gfsh command that will allow
users to change the following attributes on the AsyncEventQueue:
- batch size
- batch time interval
- maximum queue memory
Attributes changed with this command should only be reflected in cluster
configuration. We will require users to do a rolling re-start of the servers
for the new settings to take effect.
> alter async event listener
> --------------------------
>
> Key: GEODE-3874
> URL: https://issues.apache.org/jira/browse/GEODE-3874
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh
> Reporter: Swapnil Bawaskar
>
> We need to provide ability to users to re-deploy async event listeners.
> I envision the following workflow to accomplish this:
> - User deploys a jar file with the latest implementation of the
> AsyncEventListener
> - User then issues the following gfsh command: {{alter async-event-queue
> --set-async-event-listerner="classname"}} Which should end up replacing the
> current instance of the async event listener with a new instance of the given
> classname.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
