[ 
https://issues.apache.org/jira/browse/IMPALA-13628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907520#comment-17907520
 ] 

ASF subversion and git services commented on IMPALA-13628:
----------------------------------------------------------

Commit 0bbd2b684ddc7dcf8b6c16f1f7c6fab15291f782 in impala's branch 
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=0bbd2b684 ]

IMPALA-13628: Use impala::Thread in PeriodicCounterUpdater

This patch change the thread in PeriodicCounterUpdater from
boost::thread to impala:Thread. Using impala::Thread and
impala::Thread::Create will make both instance_>update_thread_ and
system_instance_>update_thread_ observable through '/threadz' page in
WebUI.

Replaced all boost include with std in periodic-counter-updater.h.

Testing:
- Run test_tpcds_queries.py and confirm the is no abnormality observed.
- Confirm that both 'periodic-counter-updater' and
  'periodic-system-counter-updater' shows up in '/threadz' page.

Change-Id: I0b04fe7818726832c520425ee29c9732cc100cb2
Reviewed-on: http://gerrit.cloudera.org:8080/22246
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> PeriodicCounterUpdater should use impala::Thread
> ------------------------------------------------
>
>                 Key: IMPALA-13628
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13628
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Minor
>             Fix For: Impala 4.5.0
>
>
> Using impala::Thread and impala::Thread::Create will make both 
> instance_->update_thread_ and system_instance_->update_thread_ observable 
> through '/threadz' page in WebUI.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to