You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.
The text was updated successfully, but these errors were encountered:
linghengqian
changed the title
Documentation for ShardingSphere Agent may simplify things
Documentation for ShardingSphere Agent may can simplify things
Sep 12, 2022
Yes, modifying start.sh is a bit fiddly, especially in a container environment.
We should consider a way to quickly control whether to start the agent or not.
Since I don't really want to manage multiple PRs at the same time, I usually don't work on issues in parallel. For this current issue, I will submit a PR shortly.
Question
For English only, other languages will not accept.
Before asking a question, make sure you have:
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.
Configure the absolute path of shardingsphere-agent.jar to the start.sh startup script of shardingsphere proxy.
is required.start.sh
is very tedious work, and javaagent can be configured in the environment variableJVM_OPTS
. This should be similar to-javaagent /xxxxx/agent/shardingsphere-agent.jar
. As mentioned in Support (or document how to bundle/use) custom Java Agents cloudfoundry/java-buildpack#555 (comment), requires modificationstart.sh
complicates things. Refer to https://shardingsphere.apache.org/document/5.2.0/en/user-manual/shardingsphere-proxy/startup/docker/ .The text was updated successfully, but these errors were encountered: