[
https://issues.apache.org/jira/browse/PHOENIX-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299385#comment-14299385
]
Hudson commented on PHOENIX-1596:
---------------------------------
SUCCESS: Integrated in Phoenix-master #575 (See
[https://builds.apache.org/job/Phoenix-master/575/])
PHOENIX-1596 Turning tracing on results in region server crash (samarth.jain:
rev a1baf2aca955551099f1e21086cfca752776cce0)
* phoenix-core/src/main/java/org/apache/phoenix/trace/util/Tracing.java
* phoenix-core/src/main/java/org/apache/phoenix/hbase/index/Indexer.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/BaseScannerRegionObserver.java
> Turning tracing on causes region servers to crash
> -------------------------------------------------
>
> Key: PHOENIX-1596
> URL: https://issues.apache.org/jira/browse/PHOENIX-1596
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.3, 4.2.3
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Fix For: 5.0.0, 4.3, 4.2.3
>
> Attachments: PHOENIX-1596.patch, PHOENIX-1596_v2.patch
>
>
> After setting trace collection frequency to always by setting the following
> in hbase-site.xml, I noticed that it created way too many traces in the trace
> table.
> <property>
> <name>phoenix.trace.frequency</name>
> <value>always</value>
> </property>
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 1283 |
> +------------------------------------------+
> 1 row selected (1.104 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 4051 |
> +------------------------------------------+
> 1 row selected (1.058 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 10668 |
> +------------------------------------------+
> 1 row selected (1.105 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 11361 |
> +------------------------------------------+
> 1 row selected (1.046 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 193119 |
> +------------------------------------------+
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 1283 |
> +------------------------------------------+
> 1 row selected (1.104 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 4051 |
> +------------------------------------------+
> 1 row selected (1.058 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 10668 |
> +------------------------------------------+
> 1 row selected (1.105 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 11361 |
> +------------------------------------------+
> 1 row selected (1.046 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> +------------------------------------------+
> | COUNT(1) |
> +------------------------------------------+
> | 193119 |
> +------------------------------------------+
> 1 row selected (6.737 seconds)
> 0: jdbc:phoenix:localhost> select count (*) from system.tracing_stats;
> 15/01/19 17:26:57 WARN client.HConnectionManager$HConnectionImplementation:
> This client just lost it's session with ZooKeeper, closing it. It will be
> recreated next time someone needs it
> Even though the only query that was being executed was the select count(*) to
> get the number of rows in the trace table, it ended up creating way too many
> traces than I had expected.
> On my mac, it in fact ended up killing the local hbase cluster altogether!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
