Project

General

Profile

Bug #12752

Datasources plugin scheduler problems after updating/deleting a datasource

Added by Ilan COSTA about 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
N/A
Assignee:
-
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
49

Description

plugin version : rudder-plugin-datasources-4.3-1.3-SNAPSHOT.rpkg

When updating some parameters in a datasource (for exemple jsonpath, update trigger, ...), the execution of this datasource is twice or more. It's hard to reproduce, but if you change settings multiple times the problem occure.

I notice that it happen when both "update periodically" and "update when a policy update start" trigger are configured.

Restarting jetty doesn't solve the problem if the datasource is still present.

You can see logs in attachement for more details.

Notice : At this time the datasource was delete but still in execution.
[2018-06-06 16:38:02] DEBUG datasources - Stopping data source with id 'cmdb-debug'
[2018-06-06 16:38:02] TRACE datasources - The datasource with id 'cmdb-debug' is disabled. Not scheduling future runs for it.
[2018-06-06 16:38:02] DEBUG datasources - Data source 'cmdb-debug' (cmdb-debug) udpated
[2018-06-06 16:38:10] DEBUG datasources - Stopping data source with id 'cmdb-debug'

Restarting jetty after deleting the datasource stop this execution.

We already have similar problem when deleting a datasource here https://www.rudder-project.org/redmine//issues/10677

Thank you


Files

ds-debug.log (41 KB) ds-debug.log Ilan COSTA, 2018-06-06 17:02

Related issues

Related to Datasources - Bug #10677: Datasources plugin call continuously datasource url even after deleteReleasedNicolas CHARLESActions
#1

Updated by Félix DALLIDET about 2 years ago

  • File deleted (ds-debug.log)
#2

Updated by Ilan COSTA about 2 years ago

The log file

#3

Updated by Benoît PECCATTE about 2 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 52
#4

Updated by François ARMAND about 2 years ago

  • Related to Bug #10677: Datasources plugin call continuously datasource url even after delete added
#5

Updated by Vincent MEMBRÉ almost 2 years ago

  • Project changed from Rudder to 54
  • Category deleted (71)
  • Target version set to 433
  • Priority changed from 52 to 50
#6

Updated by Vincent MEMBRÉ almost 2 years ago

  • Project changed from 54 to Datasources
  • Target version changed from 433 to 4.1-1.3
  • Priority changed from 50 to 49

Also available in: Atom PDF