[
https://issues.apache.org/jira/browse/SOLR-11031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-11031:
-------------------------------------
Attachment: SOLR-11031.patch
Updated patch:
* use {{TriggerListener}} API instead of {{TriggerAction}} - this way we can
report more details and also report exceptions from all stages of event
processing.
* capture details of responses collected by execute plan into separate fields
for easier searching.
TODO: decide what to do about default trigger configurations - previously they
all included {{LogPlanAction}} so that the computed and executed plan was
logged. Now we would have to configure a default listener instead, which makes
it a bit unwieldy to update the listener configuration afterwards - basically,
after creating a trigger users would have to explicitly remove this listener if
not needed.
> Implement LogPlanAction for autoscaling
> ---------------------------------------
>
> Key: SOLR-11031
> URL: https://issues.apache.org/jira/browse/SOLR-11031
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Andrzej Bialecki
> Labels: autoscaling
> Fix For: master (8.0), 7.1
>
> Attachments: SOLR-11031.patch, SOLR-11031.patch
>
>
> The LogPlanAction should be used to persist events, computed plans and
> execution results to the .system collection by default. We can use this
> information later for analysis as well as to surface hints & history in the
> Admin UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
