jnturton commented on issue #2790: URL: https://github.com/apache/drill/issues/2790#issuecomment-1500890060
Here's a relevant discussion from the Drill mailing list. Also consider a single-node Drill cluster (with a ZooKeeper) using [the distributed mode Docker Compose scripts here](https://github.com/apache/drill/tree/master/distribution/docker-cluster-mode). Subject: Re: Running drill in background in embedded mode From: James Turton <dz...@apache.org> Date: 2022/07/19, 07:28 To: u...@drill.apache.org, Prabhakar Bhosale <bhosale....@gmail.com> Well if we're playing with hacks... 😄 nohup drill-embedded -f <(sleep infinity) > /dev/null That needs a shell smart enough to do process substitution and avoids what I guess was busy wait loop in sqlline's input reader that you ran into. Back to being boring and responsible: are you sure you want to run Drill this way? It would be a lot more natural to launch a standalone Drillbit with drillbit.sh, having started a ZooKeeper somewhere beforehand. On 2022/07/19 05:30, Prabhakar Bhosale wrote: > Hi Luoc, > When I run the drill in embedded mode as foreground process, the %CPU does > not go beyond 1%. for java process. Please let me know if you need any > additional information. thx > > Regards > Prabhakar > > On Tue, Jul 19, 2022 at 6:57 AM luoc <l...@apache.org> wrote: > >> Hi, >> >> What is the cost of the CPU if you are running in a front process? >> >>> On Jul 18, 2022, at 14:51, Prabhakar Bhosale <bhosale....@gmail.com> >> wrote: >>> Hi Team, >>> I am trying to run drill in embedded mode as background process with >> below >>> command >>> nohup sh drill-embedded >/dev/null 2>&1 & >>> >>> My observation is that it takes too much CPU. After starting drill by >> above >>> command the output of top command against java process shows %CPU >> anything >>> between 150 to 175%. >>> >>> So any recommended way to run drill in embedded mode in background? >> thanks >>> REgards >>> Prabhakar >> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@drill.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org