Here is an example:
hive --service llap --instances 1 --args "-XX:+UseG1GC
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000" --cache
48000m --executors 8 --iothreads 8 --size 180000m --xmx 128000m --loglevel
INFO --javaHome /usr/jdk64/jdk1.8.0_77/
This would generate a "run.sh" script which can be run to start LLAP. This
would open up 8000 port that you have mentioned in the machine where LLAP
daemon is started.
~Rajesh.B
On Mon, Dec 26, 2016 at 10:37 AM, 김동원 <eastcirc...@gmail.com> wrote:
> I want my IntelliJ to attach to the running LLAP damons by adding the
> following JVM option (for a debugging purpose):
> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000
>
> Where is the right place to append the line?
>
> My previous attempt was as follows :
> - Before executing “hive --service llap …”, I modified
> ${hive-binary-dist}/scripts/llap/bin/llap-daemon-env.sh to modify
> LLAP_DAEMON_OPTS.
> - What I found, however, is that
> ${hive-binary-dist}/scripts/llap/bin/llapDaemon.sh
> refers to ${LLAP_DAEMON_CONF_DIR}/llap-daemon-env.sh, not
> ${LLAP_DAEMON_BIN_HOME}
> - I also tried to locate llap-daemon-env.sh under ${hive-binary-dost}/conf
> but found that LlapServiceDriver doesn’t copy that file under
> LLAP_DAEMON_CONF_DIR.
> - I had to modify ${hive-binary-dist}/scripts/llap/bin/llapDaemon.sh to
> load llap-daemon-env.sh properly by making it refer to
> ${LLAP_DAEMON_BIN_HOME}/llap-daemon-env.sh instead of
> ${LLAP_DAEMON_CONF_DIR}/llap-daemon-env.sh.
>
> - eastcircle
