search

danielcheng007 / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

trepctl status -name stack #680

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
1. To which tool/application/daemon will this feature apply?

trepctl

2. Describe the feature in general

In case of an OFFLINE:ERROR, a status call, which would allow to quickly see 
the whole stack trace.

3. Describe the feature interface

If Replicator is OFFLINE:ERROR, currenty status call may provide not enough 
information. Eg.:

$ trepctl status
...
pendingExceptionMessage: java.lang.Integer cannot be cast to java.sql.Timestamp
...

In this case, the stack trace call would print the whole stack trace of the 
exception:

$ trepctl status -name stack

java.lang.ClassCastException: java.lang.Integer cannot be cast to 
java.sql.Timestamp
    at com.continuent.tungsten.replicator.applier.MySQLDrizzleApplier.setObject(MySQLDrizzleApplier.java:342)
    at com.continuent.tungsten.replicator.applier.JdbcApplier.bindColumnValues(JdbcApplier.java:540)
    at com.continuent.tungsten.replicator.applier.JdbcApplier.applyOneRowChangePrepared(JdbcApplier.java:1005)
    at com.continuent.tungsten.replicator.applier.JdbcApplier.applyRowChangeData(JdbcApplier.java:1234)
    at com.continuent.tungsten.replicator.applier.JdbcApplier.apply(JdbcApplier.java:1327)
    at com.continuent.tungsten.replicator.applier.ApplierWrapper.apply(ApplierWrapper.java:101)
    at com.continuent.tungsten.replicator.pipeline.SingleThreadStageTask.apply(SingleThreadStageTask.java:706)
    at com.continuent.tungsten.replicator.pipeline.SingleThreadStageTask.runTask(SingleThreadStageTask.java:484)
    at com.continuent.tungsten.replicator.pipeline.SingleThreadStageTask.run(SingleThreadStageTask.java:169)
    at java.lang.Thread.run(Unknown Source)

4. Give an idea (if applicable) of a possible implementation

The exception needs to be remember in the error state and then printed out.

5. Describe pros and cons of this feature.

5a. Why the world will be a better place with this feature.

This would eliminate the need to open up and scan the trepsvc.log each time a 
more difficult error comes up.

5b. What hardship will the human race have to endure if this feature is
implemented.

More commands to know of.

6. Notes

This will make troubleshooting quicker.

Original issue reported on code.google.com by linas.vi...@continuent.com on 23 Aug 2013 at 12:28

GoogleCodeExporter commented 9 years ago 
Actually, what would help immensely, in addition to the stack trace, is an 
optional view of the THL fragment being processed.
Although it is possible to get the THL using "thl list -seqno xxx", when the 
THL contains thousand of fragments, we are unable to determine what exactly was 
being processed, and we need to guess.

So, in addition to stack trace, I would like to see the processed thl record

Suggestions:

(a)
trepctl status -name stack
trepctl status -name failed-thl

(b)
trepctl status -name error-info
(which contains all the above)

Original comment by g.maxia on 23 Aug 2013 at 12:42

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 26 Aug 2013 at 1:54

GoogleCodeExporter commented 9 years ago 
There won't be a 2.1.3.

Original comment by linas.vi...@continuent.com on 17 Sep 2013 at 10:13

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 18 Dec 2013 at 1:38

GoogleCodeExporter commented 9 years ago 
Unscheduling. Should be brought in to future releases as strategic planning 
dictates.

Original comment by linas.vi...@continuent.com on 2 May 2014 at 6:52