Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0.0-alpha-1, 2.0.0
-
None
-
Reviewed
Description
HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, the upgrade to 4.x is not trivial and would take time. It might not worth to keep it in this state, so would be better to remove it.
Of course it doesn't mean tracing would be useless, just that in this form the use of HTrace 3.2 might not add any value to the project and fixing it would be far too much effort.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Based on the decision of the community we keep htrace now and update version
Attachments
Attachments
Issue Links
- breaks
-
HBASE-19371 Running WALPerformanceEvaluation against asyncfswal throws exceptions
- Closed
- is duplicated by
-
HBASE-14451 Move on to htrace-4.0.1 (from htrace-3.2.0) and tell a couple of good trace stories
- Closed
- is related to
-
HBASE-18895 Implement changes eliminated during HTrace update
- Closed
-
PHOENIX-4090 Remove HTrace based tracing
- Open
-
HBASE-20246 Remove the spark module
- Closed
- relates to
-
HBASE-19372 Remove the Span object in SyncFuture as it is useless now
- Closed
-
HBASE-14451 Move on to htrace-4.0.1 (from htrace-3.2.0) and tell a couple of good trace stories
- Closed