[
https://issues.apache.org/jira/browse/PHOENIX-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331100#comment-15331100
]
Pranavan commented on PHOENIX-2166:
-----------------------------------
Hi Mujtaba Chohan
Shall we go for a lock based solution? Then at a time only one can proceed.
(The original requirement needs no concurrency for this particular case)
> Prevent writing to tracing table when tracing data collected
> ------------------------------------------------------------
>
> Key: PHOENIX-2166
> URL: https://issues.apache.org/jira/browse/PHOENIX-2166
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 4.5.0
> Reporter: Mujtaba Chohan
> Labels: gsoc2016, tracing
>
> When tracing is turned ON, trace table grows at fast pace and is filled with
> the following traces which should not be present:
> {code}
> Executing UPSERT INTO SYSTEM.TRACING_STATS (trace_id, ...
> Writing mutation batch for table: SYSTEM.TRACING_STATS ...
> and so on
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
