Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0033945
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Retail Modules] StoreServerminorhave not tried2016-09-12 10:542016-10-18 17:52
ReportermtaalView Statuspublic 
Assigned ToAugustoMauch 
PrioritynormalResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget VersionRR17Q1
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0033945: When a channel is blocked allow the user to pick/select blocked changesets and execute them directly

DescriptionIf a replication error occurs then a replication channel gets blocked until it is resolved.

This blockage will stop other replication in the same channel. This while other changes might not be related to the blocked changesets and can be executed independently.


http://wiki.openbravo.com/wiki/Projects:Symmetric_DS_Working_With_Blocked_Channels [^]
Steps To Reproduce.
Proposed SolutionProvide a solution where the system/application admin can pick and choose data-change-sets to be applied even in case of channel blockage. The idea is to use a separate channel for this.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0090665)
AugustoMauch (administrator)
2016-10-18 11:47

Hey Martin,

Could you describe a use case for this? I am not sure it is a good idea to implement a mechanism to work around the block, when most of the times the channel is blocked for a good reason.

If people were to use that mechanism, we could get to have many blocks in the same logical channel (the original plus the one that comes after working around the original). I think it would be better to improve the ways to monitor/fix blocks than to work around them.
(0090675)
AugustoMauch (administrator)
2016-10-18 17:52

This functionality is already available using the Table Reload functionality

- Issue History
Date Modified Username Field Change
2016-09-12 10:54 mtaal New Issue
2016-09-12 10:54 mtaal Assigned To => AugustoMauch
2016-09-12 10:54 mtaal OBNetwork customer => No
2016-09-12 10:54 mtaal Triggers an Emergency Pack => No
2016-09-12 11:04 mtaal Description Updated View Revisions
2016-10-18 11:47 AugustoMauch Note Added: 0090665
2016-10-18 11:47 AugustoMauch Status new => feedback
2016-10-18 17:52 AugustoMauch Note Added: 0090675
2016-10-18 17:52 AugustoMauch Status feedback => closed
2016-10-18 17:52 AugustoMauch Resolution open => no change required


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker