spark applications information not updating in dr_elephant.log

Hi
spark applications information not updating in dr_elephant.log. i have attached FetcherConf.xml herewith.
i can able to see mapreduce jobs in dr-elephant dashboard but not spark & Tez.
find the more details.
[root@sjdcdlake06 app-conf]# spark-submit --version
Welcome to
____              __
/ /  ___ / /
\ / _ / _ `/ __/  '/
// .__/_,// //_\   version <IP_ADDRESS>.1.0.165-3
//
[root@sjdcdlake06 conf]# spark-defaults.conf
spark.eventLog.dir hdfs:///spark2-history/
Spark Application able to see on Job History Server UI. also i removed com.linkedin.drelephant.spark.fetchers.SparkFSFetcher from FetcherConf.xml file
fs.defaultFS=hdfs://snn in coresite.xml
can you please help here as what changes i need to made to see spark  jobs in dr-elephant dashboard.
FetcherConf.txt

@maheshjadhav4-github is Dr.Elephant able to fetch the application from YARN after completion?

yes , able to fetch Mapreduce application. not spark

Are completed Spark applications are available YARN API? If yes, then you can check the JobType if Spark JobType is added there. Can you also add the exception logs if there are any there in the logs, also check dr.log and logs/application.log

Now we can see spark applications in logs but throwing below error
12-17-2019 16:32:51 WARN  [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1576153735471_0144] into the retry list.
12-17-2019 16:32:51 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576153735471_0143
12-17-2019 16:32:51 ERROR [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : java.lang.IllegalArgumentException: java.net.UnknownHostException: null
at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:445)
at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:462)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.initialize(WebHdfsFileSystem.java:251)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3303)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3352)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3320)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:479)
at com.linkedin.drelephant.util.SparkUtils$class.fileSystemAndPathForEventLogDir(SparkUtils.scala:70)
at com.linkedin.drelephant.util.SparkUtils$.fileSystemAndPathForEventLogDir(SparkUtils.scala:312)

job type already mentioned in conf file. able to see spark app in spark-history web UI and yarn RM Web UI
cat JobTypeConf.xml |grep -i spark
Spark
spark
spark.app.id
but still spark app not showing in Dr elephant UI. now showing in log file with  below error.
12-17-2019 16:32:51 ERROR [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : java.lang.IllegalArgumentException: java.net.UnknownHostException: null

Seems like the value of spark.eventLog.dir in your Spark Conf is null, can you check?

Hi Shubham,
park.eventLog.dir is not empty . find the details below.
echo $SPARK_CONF_DIR
/usr/hdp/current/spark2-client/conf
pwd
/usr/hdp/current/spark2-client/conf
cat spark-defaults.conf |grep -i event
spark.eventLog.dir hdfs:///spark2-history/
spark.eventLog.enabled true
Find the FetcherConf.xml file attached here.
FetcherConfformat.txt

Find the latest error for spark application
12-18-2019 13:04:30 WARN  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1576577790943_0006] into the retry list.
12-18-2019 13:04:30 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Retry queue size is 239
12-18-2019 13:04:30 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576577790943_0003
12-18-2019 13:04:30 ERROR [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : java.lang.IllegalArgumentException: java.net.UnknownHostException: null
at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:445)
at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:462)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.initialize(WebHdfsFileSystem.java:251)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3303)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3352)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3320)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:479)
at com.linkedin.drelephant.util.SparkUtils$class.fileSystemAndPathForEventLogDir(SparkUtils.scala:70)
at com.linkedin.drelephant.util.SparkUtils$.fileSystemAndPathForEventLogDir(SparkUtils.scala:312)
at org.apache.spark.deploy.history.SparkFSFetcher.doFetchData(SparkFSFetcher.scala:84)
at org.apache.spark.deploy.history.SparkFSFetcher$$anonfun$fetchData$1.apply(SparkFSFetcher.scala:74)
at org.apache.spark.deploy.history.SparkFSFetcher$$anonfun$fetchData$1.apply(SparkFSFetcher.scala:74)
at org.apache.spark.deploy.history.SparkFSFetcher$$anon$1.run(SparkFSFetcher.scala:78)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1710)
at com.linkedin.drelephant.security.HadoopSecurity.doAs(HadoopSecurity.java:109)
at org.apache.spark.deploy.history.SparkFSFetcher.doAsPrivilegedAction(SparkFSFetcher.scala:78)
at org.apache.spark.deploy.history.SparkFSFetcher.fetchData(SparkFSFetcher.scala:74)
at com.linkedin.drelephant.spark.fetchers.FSFetcher.fetchData(FSFetcher.scala:34)
at com.linkedin.drelephant.spark.fetchers.FSFetcher.fetchData(FSFetcher.scala:29)
at com.linkedin.drelephant.analysis.AnalyticJob.getAnalysis(AnalyticJob.java:247)
at com.linkedin.drelephant.ElephantRunner$ExecutorJob.run(ElephantRunner.java:175)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.UnknownHostException: null
... 29 more

Which branch have you forked out?

On looking at FetcherConf.xml I noticed that you haven't provided the value of the event_log_location_uri field.

Hi Shubham,
Thanks for the replay.
in my setup fs.defaultFS=hdfs://snn & Event log directory: hdfs://snn/spark2-history/
dfs.namenode.http-address.snn.nn1:50070=server1.com
dfs.namenode.http-address.snn.nn2:50070=server2.com
now let me know what should i put in below property ?
<event_log_location_uri>webhdfs://localhost:50070/spark2-history/</event_log_location_uri>
Note: all spark application are placed in /spark2-history/ hdfs path

Try:
<event_log_location_uri>webhdfs://server2.com:50070/spark2-history/</event_log_location_uri> considering server1.com:50070 is your primary NameNode.

Hi Shubham,
Thanks for the Replay.
I have update the mentioned property in FetcherConf.xml file. after that we ran two sample spark jobs. we are see now "INFO  [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576725381250_0035" message . apart from this no more info & not any warn or error message. means we fetch application info successfully but still not able to see jobs in Dr elephant dashboard UI.
Find below message in details in dr_elephant.log file.
12-19-2019 11:38:37 INFO  [Thread-6] com.linkedin.drelephant.ElephantRunner : Fetching analytic job list...
12-19-2019 11:38:37 INFO  [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Fetching recent finished application runs between last time:<PHONE_NUMBER>740, and current time:<PHONE_NUMBER>752
12-19-2019 11:38:37 INFO  [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : The succeeded apps URL is http://sjdcdlake03.ril.com:8088/ws/v1/cluster/apps?finalStatus=SUCCEEDED&finishedTimeBegin=1576735597740&finishedTimeEnd=1576735657752
12-19-2019 11:38:37 INFO  [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : The failed apps URL is http://sjdcdlake03.ril.com:8088/ws/v1/cluster/apps?finalStatus=FAILED&state=FINISHED&finishedTimeBegin=1576735597740&finishedTimeEnd=1576735657752
12-19-2019 11:38:37 INFO  [Thread-6] com.linkedin.drelephant.ElephantRunner : Job queue size is 1
12-19-2019 11:38:37 INFO  [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576725381250_0035
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Starting baseline computation
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Fetching jobs for which baseline metrics need to be computed
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Baseline computation complete
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Checking execution status
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Fetching the executions which were running
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Number of executions which were in running state: 0
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Fetching the list of executions completed since last iteration
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Number of executions completed since last iteration: 0
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Updating status of executions completed since last iteration
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Finished updating execution status
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Computing and updating fitness for completed executions
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Fetching completed executions whose fitness are yet to be computed
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Number of completed execution fetched for fitness computation: 0
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Execution metrics updated
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Checking which jobs need new parameter suggestion
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : None of the jobs need new parameter suggestion
12-19-2019 11:39:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Updating new parameter suggestion in database
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Starting baseline computation
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Fetching jobs for which baseline metrics need to be computed
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Baseline computation complete
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Checking execution status
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Fetching the executions which were running
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Number of executions which were in running state: 0
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Fetching the list of executions completed since last iteration
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Number of executions completed since last iteration: 0
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Updating status of executions completed since last iteration
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Finished updating execution status
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Computing and updating fitness for completed executions
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Fetching completed executions whose fitness are yet to be computed
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Number of completed execution fetched for fitness computation: 0
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Execution metrics updated
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Checking which jobs need new parameter suggestion
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : None of the jobs need new parameter suggestion
12-19-2019 11:41:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Updating new parameter suggestion in database
12-19-2019 11:41:37 INFO  [Thread-6] com.linkedin.drelephant.ElephantRunner : Fetching analytic job list...
12-19-2019 11:41:37 INFO  [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Fetching recent finished application runs between last time:<PHONE_NUMBER>771, and current time:<PHONE_NUMBER>781
12-19-2019 11:41:37 INFO  [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : The succeeded apps URL is http://sjdcdlake03.ril.com:8088/ws/v1/cluster/apps?finalStatus=SUCCEEDED&finishedTimeBegin=1576735777771&finishedTimeEnd=1576735837781
12-19-2019 11:41:37 INFO  [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : The failed apps URL is http://sjdcdlake03.ril.com:8088/ws/v1/cluster/apps?finalStatus=FAILED&state=FINISHED&finishedTimeBegin=1576735777771&finishedTimeEnd=1576735837781
12-19-2019 11:41:37 INFO  [Thread-6] com.linkedin.drelephant.ElephantRunner : Job queue size is 1
12-19-2019 11:41:37 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576725381250_0037
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Starting baseline computation
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Fetching jobs for which baseline metrics need to be computed
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Baseline computation complete
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Checking execution status
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Fetching the executions which were running
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Number of executions which were in running state: 0
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Fetching the list of executions completed since last iteration
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Number of executions completed since last iteration: 0
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Updating status of executions completed since last iteration
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Finished updating execution status
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Computing and updating fitness for completed executions
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Fetching completed executions whose fitness are yet to be computed
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Number of completed execution fetched for fitness computation: 0
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Execution metrics updated
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Checking which jobs need new parameter suggestion
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : None of the jobs need new parameter suggestion
12-19-2019 11:42:37 INFO  [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Updating new parameter suggestion in database
12-19-2019 11:42:37 INFO  [Thread-6]

Hi Shubham,
Thanks for the Replay.
I have update the mentioned property in FetcherConf.xml file. after that we ran two sample spark jobs. we are see now "INFO [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576725381250_0035" message . apart from this no more info & not any warn or error message. means we fetch application info successfully but still not able to see jobs in Dr elephant dashboard UI.
Find below message in details in dr_elephant.log file.
12-19-2019 11:38:37 INFO [Thread-6] com.linkedin.drelephant.ElephantRunner : Fetching analytic job list...
12-19-2019 11:38:37 INFO [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Fetching recent finished application runs between last time:<PHONE_NUMBER>740, and current time:<PHONE_NUMBER>752
12-19-2019 11:38:37 INFO [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : The succeeded apps URL is http://server1.com:8088/ws/v1/cluster/apps?finalStatus=SUCCEEDED&finishedTimeBegin=1576735597740&finishedTimeEnd=1576735657752
12-19-2019 11:38:37 INFO [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : The failed apps URL is http://server1.com:8088/ws/v1/cluster/apps?finalStatus=FAILED&state=FINISHED&finishedTimeBegin=1576735597740&finishedTimeEnd=1576735657752
12-19-2019 11:38:37 INFO [Thread-6] com.linkedin.drelephant.ElephantRunner : Job queue size is 1
12-19-2019 11:38:37 INFO [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576725381250_0035
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Starting baseline computation
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Fetching jobs for which baseline metrics need to be computed
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Baseline computation complete
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Checking execution status
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Fetching the executions which were running
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Number of executions which were in running state: 0
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Fetching the list of executions completed since last iteration
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Number of executions completed since last iteration: 0
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Updating status of executions completed since last iteration
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Finished updating execution status
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Computing and updating fitness for completed executions
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Fetching completed executions whose fitness are yet to be computed
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Number of completed execution fetched for fitness computation: 0
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Execution metrics updated
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Checking which jobs need new parameter suggestion
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : None of the jobs need new parameter suggestion
12-19-2019 11:39:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Updating new parameter suggestion in database
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Starting baseline computation
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Fetching jobs for which baseline metrics need to be computed
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Baseline computation complete
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Checking execution status
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Fetching the executions which were running
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Number of executions which were in running state: 0
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Fetching the list of executions completed since last iteration
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Number of executions completed since last iteration: 0
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Updating status of executions completed since last iteration
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Finished updating execution status
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Computing and updating fitness for completed executions
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Fetching completed executions whose fitness are yet to be computed
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Number of completed execution fetched for fitness computation: 0
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Execution metrics updated
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Checking which jobs need new parameter suggestion
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : None of the jobs need new parameter suggestion
12-19-2019 11:41:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Updating new parameter suggestion in database
12-19-2019 11:41:37 INFO [Thread-6] com.linkedin.drelephant.ElephantRunner : Fetching analytic job list...
12-19-2019 11:41:37 INFO [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Fetching recent finished application runs between last time:<PHONE_NUMBER>771, and current time:<PHONE_NUMBER>781
12-19-2019 11:41:37 INFO [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : The succeeded apps URL is http://server1.com:8088/ws/v1/cluster/apps?finalStatus=SUCCEEDED&finishedTimeBegin=1576735777771&finishedTimeEnd=1576735837781
12-19-2019 11:41:37 INFO [Thread-6] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : The failed apps URL is http://server1.com:8088/ws/v1/cluster/apps?finalStatus=FAILED&state=FINISHED&finishedTimeBegin=1576735777771&finishedTimeEnd=1576735837781
12-19-2019 11:41:37 INFO [Thread-6] com.linkedin.drelephant.ElephantRunner : Job queue size is 1
12-19-2019 11:41:37 INFO [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576725381250_0037
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Starting baseline computation
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Fetching jobs for which baseline metrics need to be computed
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Baseline computation complete
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Checking execution status
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Fetching the executions which were running
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Number of executions which were in running state: 0
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Fetching the list of executions completed since last iteration
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Number of executions completed since last iteration: 0
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Updating status of executions completed since last iteration
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Finished updating execution status
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Computing and updating fitness for completed executions
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Fetching completed executions whose fitness are yet to be computed
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Number of completed execution fetched for fitness computation: 0
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Execution metrics updated
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Checking which jobs need new parameter suggestion
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : None of the jobs need new parameter suggestion
12-19-2019 11:42:37 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Updating new parameter suggestion in database
12-19-2019 11:42:37 INFO [Thread-6]

One suggestion for quick debugging ->

Disable AutoTuning(app-conf/AutoTuningConf.xml) for now as this will reduce a lot of useless logs
Enable the DEBUG level for logs (log4j.properties).
Kindly try to grep for 'application_1576725381250_0035' in the logs as fetching logs can take time.
ExceptionStacktrace is necessary to know where is the problem.

Also which Branch you have cloned. If you are using master then you can try SparkFetcher which uses Spark History Server APIs if it would be feasible for you.

Hi Shubham,
not able to understand your last comment. can you please elaborate.
I followed below link to setup Dr Elephant.
https://github.com/linkedin/dr-elephant/wiki/Quick-Setup-Instructions-(Must-Read)

HI Shubham,
I was download Dr elephant in below URL.
wget https://github.com/linkedin/dr-elephant/archive/v2.1.7.tar.gz;
wget https://downloads.typesafe.com/typesafe-activator/1.3.12/typesafe-activator-1.3.12.zip;

Hi Shubham,
Also disabled AutoTuning and Enable the DEBUG level for logs (log4j.properties) in spark.
after this changes ran sample spark job. do not see any other info in dr_elephant.log apart from Analyzing SPARK application_1576725381250_0075 message. also not seen any error in spark log

In the last part of the above comment, I was recommending you to use com.linkedin.drelephant.spark.fetchers.SparkFetcher  instead of com.linkedin.drelephant.spark.fetchers.FSFetcher. The SparkFetcher used Spark REST APIs to fetch application data instead of using the HDFS data. I am more familiar with SparkFetcher'w working.
Can you attach the latest full log file?

Hi Shubham,
Thanks for the Replay.
I have done recommended changes as you mentioned. then after we are see below error. we can able to access page till http://server6.com:18081/api/v1/applications/application_1576650691954_0176/stages/. then after failed stages page shown not found error (error 404 not found ). because of this getting Timed out error while fetching data.
find the error details.
12-19-2019 16:18:33 INFO  [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576650691954_0177
12-19-2019 16:18:33 INFO  [dr-el-executor-thread-2] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Fetching data for application_1576650691954_0177
12-19-2019 16:18:33 INFO  [ForkJoinPool-1-worker-5] com.linkedin.drelephant.spark.fetchers.SparkRestClient : calling REST API at http://server6.com:18081/api/v1/applications/application_1576650691954_0177
12-19-2019 16:18:33 ERROR [ForkJoinPool-1-worker-11] com.linkedin.drelephant.spark.fetchers.SparkRestClient : error reading failedTasks http://server6.com:18081/api/v1/applications/application_1576650691954_0176/stages/failedTasks
javax.ws.rs.NotFoundException: HTTP 404 Not Found
at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1020)
at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:819)
at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92)
at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:701)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444)
at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:697)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
12-19-2019 16:18:33 WARN  [dr-el-executor-thread-0] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Failed fetching data for application_1576650691954_0176. I will retry after some time! Exception Message is: HTTP 404 Not Found
12-19-2019 16:18:33 WARN  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Timed out while fetching data. Exception message is: null
12-19-2019 16:18:33 WARN  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1576650691954_0176] into the retry list.
12-19-2019 16:18:33 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Retry queue size is 96
12-19-2019 16:18:33 INFO  [dr-el-executor]
we are seen this error message for all spark application. not other error message apart from this

@maheshjadhav4-github you are not using Master branch, kindly use that when compiling. You are getting error reading failedTasks as /stages/failedTask is LinkedIn's internal API which is not available in the open-source Spark. Please do switch the branch.

Hi Shubham,
Now i am using Master Branch. while doing compiling getting below error. because of this Build is failed.
[error] Test com.linkedin.drelephant.tuning.PSOParamGeneratorTest.getParamsTest failed: Swarm size did not match expected:<3> but was:<0>
[error] Test com.linkedin.drelephant.tuning.PSOParamGeneratorTest.generateParamSetTest failed: java.lang.RuntimeException: java.lang.NullPointerException
[error]     at play.libs.Json.parse(Json.java:71)
[error]     at com.linkedin.drelephant.tuning.PSOParamGeneratorTest$2.run(PSOParamGeneratorTest.java:119)
[error]     at play.test.Helpers.running(Helpers.java:417)
[error]     at com.linkedin.drelephant.tuning.PSOParamGeneratorTest.generateParamSetTest(PSOParamGeneratorTest.java:86)
[error]     ...
[error] Caused by: java.lang.NullPointerException
[error]     at com.fasterxml.jackson.core.JsonFactory.createParser(JsonFactory.java:822)
[error]     at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2580)
[error]     at play.libs.Json.parse(Json.java:69)
[error]     ... 40 more
[info] com.linkedin.drelephant.tuning.PSOParamGeneratorTest
[info] x getParamsTest
[info] x generateParamSetTest
[info] ScalaTest
[info] Run completed in 29 seconds, 743 milliseconds.
[info] Total number of tests run: 150
[info] Suites: completed 15, aborted 0
[info] Tests: succeeded 150, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[error] Failed: Total 492, Failed 3, Errors 0, Passed 488, Skipped 1
[error] Failed tests:
[error]         com.linkedin.drelephant.tuning.PSOParamGeneratorTest
[error]         com.linkedin.drelephant.tony.fetchers.TonyFetcherTest
[error] (test:test) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 41 s, completed Dec 20, 2019 4:20:35 PM
Build failed...
please help on this.

For now replace play_command $OPTS clean compile test $extra_commands with play_command $OPTS clean compile $extra_commands. We will work on fixing the tests.

HI Shubham,
I removed test  & then after it was successful.
Now i can able to see Mapreduce  jobs but not spark job again . getting below error for spark application.
12-23-2019 08:57:39 INFO  [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576827709947_0629
12-23-2019 08:57:39 INFO  [dr-el-executor-thread-1] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Fetching data for application_1576827709947_0629
12-23-2019 08:57:39 INFO  [ForkJoinPool-1-worker-1] com.linkedin.drelephant.spark.fetchers.SparkRestClient : calling REST API at http://server6.com:18081/api/v1/applications/application_1576827709947_0629
12-23-2019 08:57:44 WARN  [dr-el-executor-thread-1] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Failed fetching data for application_1576827709947_0629. I will retry after some time! Exception Message is: Futures timed out after [5 seconds]
12-23-2019 08:57:44 WARN  [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1576827709947_0629] into the retry list.
12-23-2019 08:58:39 INFO  [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1576827709947_0629
12-23-2019 08:58:39 INFO  [dr-el-executor-thread-2] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Fetching data for application_1576827709947_0629
12-23-2019 08:58:39 INFO  [ForkJoinPool-1-worker-9] com.linkedin.drelephant.spark.fetchers.SparkRestClient : calling REST API at http://server6.com:18081/api/v1/applications/application_1576827709947_0629
12-23-2019 08:58:44 WARN  [dr-el-executor-thread-2] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Failed fetching data for application_1576827709947_0629. I will retry after some time! Exception Message is: Futures timed out after [5 seconds]
12-23-2019 08:58:44 WARN  [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1576827709947_0629] into the retry list.
Also, for TEZ application , getting below error
12-23-2019 03:58:32 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Analyzing TEZ application_1576815296251_0030
12-23-2019 03:58:32 INFO  [ForkJoinPool-1-worker-1] com.linkedin.drelephant.spark.fetchers.SparkRestClient : calling REST API at http://server6.com:18081/api/v1/applications/application_1576815296251_0024
12-23-2019 03:58:32 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.util.ThreadContextMR2 : Executor 1 update interval 30.428733333333334
12-23-2019 03:58:32 ERROR [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : http://server2.com:8188/ws/v1/timeline/TEZ_APPLICATION/tez_application_1576815296251_0030
12-23-2019 03:58:32 ERROR [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : java.io.FileNotFoundException: http://server2.com:8188/ws/v1/timeline/TEZ_APPLICATION/tez_application_1576815296251_0030
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at com.linkedin.drelephant.util.ThreadContextMR2.readJsonNode(ThreadContextMR2.java:81)
at com.linkedin.drelephant.tez.fetchers.TezFetcher$JSONFactory.getProperties(TezFetcher.java:209)
at com.linkedin.drelephant.tez.fetchers.TezFetcher$JSONFactory.access$300(TezFetcher.java:200)
at com.linkedin.drelephant.tez.fetchers.TezFetcher.fetchData(TezFetcher.java:73)
at com.linkedin.drelephant.tez.fetchers.TezFetcher.fetchData(TezFetcher.java:40)
at com.linkedin.drelephant.analysis.AnalyticJob.getAnalysis(AnalyticJob.java:308)
at com.linkedin.drelephant.ElephantRunner$ExecutorJob.run(ElephantRunner.java:390)
at com.linkedin.drelephant.priorityexecutor.RunnableWithPriority$1.run(RunnableWithPriority.java:36)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

Hi Shubham,
Also dr.log file getting below error.
java.lang.NoClassDefFoundError: Could not initialize class org.apache.hadoop.util.JsonSerialization
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.jsonParse(WebHdfsFileSystem.java:477)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$FsPathResponseRunner.getResponse(WebHdfsFileSystem.java:959)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.runWithRetry(WebHdfsFileSystem.java:822)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.access$100(WebHdfsFileSystem.java:649)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner$1.run(WebHdfsFileSystem.java:687)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:683)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getDelegationToken(WebHdfsFileSystem.java:1684)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getDelegationToken(WebHdfsFileSystem.java:365)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getAuthParameters(WebHdfsFileSystem.java:585)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.toUrl(WebHdfsFileSystem.java:638)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractFsPathRunner.getUrl(WebHdfsFileSystem.java:923)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.runWithRetry(WebHdfsFileSystem.java:819)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.access$100(WebHdfsFileSystem.java:649)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner$1.run(WebHdfsFileSystem.java:687)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem$AbstractRunner.run(WebHdfsFileSystem.java:683)
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.listStatus(WebHdfsFileSystem.java:1634)
at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1868)
at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1910)
at com.linkedin.drelephant.util.SparkUtils$class.getLogPathAndCodecName(SparkUtils.scala:252)
at com.linkedin.drelephant.util.SparkUtils$class.pathAndCodecforEventLog(SparkUtils.scala:121)
at com.linkedin.drelephant.util.SparkUtils$.pathAndCodecforEventLog(SparkUtils.scala:312)
at com.linkedin.drelephant.spark.fetchers.SparkLogClient.doFetchData(SparkLogClient.scala:63)
at com.linkedin.drelephant.spark.fetchers.SparkLogClient$$anonfun$fetchData$1.apply(SparkLogClient.scala:49)
at com.linkedin.drelephant.spark.fetchers.SparkLogClient$$anonfun$fetchData$1.apply(SparkLogClient.scala:49)
at com.linkedin.drelephant.spark.fetchers.SparkLogClient$$anon$1.run(SparkLogClient.scala:52)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1710)
at com.linkedin.drelephant.security.HadoopSecurity.doAs(HadoopSecurity.java:109)
at com.linkedin.drelephant.spark.fetchers.SparkLogClient.doAsPrivilegedAction(SparkLogClient.scala:52)
at com.linkedin.drelephant.spark.fetchers.SparkLogClient.fetchData(SparkLogClient.scala:49)
at com.linkedin.drelephant.spark.fetchers.SparkFetcher$$anonfun$doFetchDataUsingRestAndLogClients$1.apply(SparkFetcher.scala:125)
at com.linkedin.drelephant.spark.fetchers.SparkFetcher$$anonfun$doFetchDataUsingRestAndLogClients$1.apply(SparkFetcher.scala:114)
at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
at scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
at scala.concurrent.impl.ExecutionContextImpl$$anon$3.exec(ExecutionContextImpl.scala:107)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)

Hi Shubham
waiting for your response..

@maheshjadhav4-github for the Tez issue, kindly find out why you are getting 404 as this is unexpected behavior.
I was not able to go through the Spark logs due to holiday time. Will try to figure out the issue, but it would be helpful if you can also try to backtrack from logs to the source code.

Hi Shubham,
I am  working on Tez issue, there is issue for Tez Configuration.
Can we work on Spark, why spark application not fetch here.

Hi Shubham,
yarn timeline issue has been resolved. now able to see Tez & Spark jobs in logs but not shown in UI.
Find the error details in elephant logs.
12-26-2019 19:36:17 WARN  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1577280558164_0159] into the retry list.
12-26-2019 19:36:17 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Retry queue size is 28
12-26-2019 19:36:17 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Analyzing TEZ application_1577280558164_0155
12-26-2019 19:36:17 ERROR [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Index: 0, Size: 0
12-26-2019 19:36:17 ERROR [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:657)
at java.util.ArrayList.get(ArrayList.java:433)
at com.linkedin.drelephant.tez.fetchers.TezFetcher.fetchData(TezFetcher.java:125)
at com.linkedin.drelephant.tez.fetchers.TezFetcher.fetchData(TezFetcher.java:40)
at com.linkedin.drelephant.analysis.AnalyticJob.getAnalysis(AnalyticJob.java:308)
at com.linkedin.drelephant.ElephantRunner$ExecutorJob.run(ElephantRunner.java:390)
at com.linkedin.drelephant.priorityexecutor.RunnableWithPriority$1.run(RunnableWithPriority.java:36)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
12-26-2019 19:36:17 WARN  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1577280558164_0155] into the retry list.
12-26-2019 19:36:17 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Retry queue size is 29
12-26-2019 19:36:17 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1577280558164_0116
12-26-2019 19:36:17 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Fetching data for application_1577280558164_0116
12-26-2019 19:36:18 INFO  [ForkJoinPool-1-worker-29] com.linkedin.drelephant.spark.fetchers.SparkRestClient : calling REST API at http://server6.com:18081/api/v1/applications/application_1577280558164_0116
12-26-2019 19:36:22 WARN  [dr-el-executor-thread-2] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Failed fetching data for application_1577280558164_0152. I will retry after some time! Exception Message is: Futures timed out after [5 seconds]
12-26-2019 19:36:22 WARN  [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : Timed out while fetching data. Exception message is: null
12-26-2019 19:36:22 WARN  [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1577280558164_0152] into the retry list.
12-26-2019 19:36:22 INFO  [dr-el-executor-thread-2] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Retry queue size is 30
12-26-2019 19:36:22 INFO  [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : Analyzing SPARK application_1577280558164_0117
12-26-2019 19:36:22 INFO  [dr-el-executor-thread-2] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Fetching data for application_1577280558164_0117
12-26-2019 19:36:22 WARN  [dr-el-executor-thread-1] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Failed fetching data for application_1577280558164_0153. I will retry after some time! Exception Message is: Futures timed out after [5 seconds]
12-26-2019 19:36:22 WARN  [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Timed out while fetching data. Exception message is: null
12-26-2019 19:36:22 WARN  [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Add analytic job id [application_1577280558164_0153] into the retry list.
12-26-2019 19:36:22 INFO  [dr-el-executor-thread-1] com.linkedin.drelephant.analysis.AnalyticJobGeneratorHadoop2 : Retry queue size is 31
12-26-2019 19:36:22 INFO  [ForkJoinPool-1-worker-15] com.linkedin.drelephant.spark.fetchers.SparkRestClient : calling REST API at http://server6.com:18081/api/v1/applications/application_1577280558164_0117

@maheshjadhav4-github from #645 it seems your Spark Job analysis issue is resolved. Also thanks for creating a separate issue for Tez issue, I will have a look at that soon.
@maheshjadhav4-github can you describe here how you resolved the Spark jobs issue, it will be helpful for other users facing the same issue, also since you were using Timeline it would be beneficial.

java.lang.NoClassDefFoundError: Could not initialize class org.apache.hadoop.util.JsonSerialization
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.jsonParse(WebHdfsFileSystem.java:477)

hi，maheshjadhav4        how to fix java.lang.NoClassDefFoundError: Could not initialize class org.apache.hadoop.util.JsonSerialization
at org.apache.hadoop.hdfs.web.WebHdfsFileSystem.jsonParse(WebHdfsFileSystem.java:477)   tks


Missing h in http panic error

Bug description

Link is missing an h
PrismaClientUnknownRequestError2 [PrismaClientUnknownRequestError]:
Invalid `prisma.executeRaw()` invocation:

  PANIC in /root/.cargo/git/checkouts/quaint-9f01e008b9a89c14/bc3aa8a/src/connector/postgres/error.rs:138:29
index out of bounds: the len is 1 but the index is 1

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

ttps://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v12.16.1+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+darwin+++++++++++++%7C%0A%7C+Prisma+Client+++%7C+2.14.0+++++++++++++%7C%0A%7C+Query+Engine++++%7C+query-engine+5d491261d382a2a5ffdc71de17072b0e409f1cc1%7C%0A%7C+Database++++++++%7C+undefined%7C%0A%0A%0A%0A%23%23+Query%0A%60%60%60%0Amutation+%7B%0A++executeRaw%28%0A++++query%3A+%22X%22%0A++++parameters%3A+%22X%22%0A++%29%0A%7D%0A%60%60%60%0A%0A%23%23+Logs%0A%60%60%60%0A++tryLoadEnv+Environment+variables+loaded+from+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2F.env++%0A++tryLoadEnv+Environment+variables+loaded+from+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2F.env++%0A++prisma-client+%7B+clientVersion%3A+%272.14.0%27+%7D++%0A++engine+%7B+cwd%3A+%27%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fprisma%27+%7D++%0A++engine+Search+for+Query+Engine+in+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient++%0A++engine+Search+for+Query+Engine+in+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient++%0A++plusX+Execution+permissions+of+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine++%0A++plusX+Execution+permissions+of+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine++%0A++engine+%7B%0A++engine+++flags%3A+%5B%0A++engine+++++%27--enable-raw-queries%27%2C%0A++engine+++++%27--unix-path%27%2C%0A++engine+++++%27%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%27%0A++engine+++%5D%0A++engine+%7D++%0A++engine+stdout++Starting+a+postgresql+pool+with+13+connections.++%0A++engine+stdout++Started+http+server+on+http%2Bunix%3A%2F%2F%2Fprivate%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock++%0A++engine+Search+for+Query+Engine+in+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient++%0A++prisma-client+prisma.%24executeRaw%28SET+jwt.claims.user_id+%3D+10%2C+%5B%5D%29++%0A++prisma-client+Prisma+Client+call%3A++%0A++plusX+Execution+permissions+of+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine++%0A++prisma-client+prisma.%24executeRaw%28select+jwt.claims.user_id%2C+%5B%5D%29++%0A++prisma-client+Prisma+Client+call%3A++%0A++engine+stdout++PANIC+in+%2Froot%2F.cargo%2Fgit%2Fcheckouts%2Fquaint-9f01e008b9a89c14%2Fbc3aa8a%2Fsrc%2Fconnector%2Fpostgres%2Ferror.rs%3A138%3A29%0Aindex+out+of+bounds%3A+the+len+is+1+but+the+index+is+1++%0A++engine+TypeError%3A+this.currentRequestPromise.cancel+is+not+a+function%0A++engine+++++at+NodeEngine.handlePanic+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A26344%3A36%29%0A++engine+++++at+NodeEngine.setError+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A26290%3A16%29%0A++engine+++++at+LineStream.%3Canonymous%3E+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A26585%3A24%29%0A++engine+++++at+LineStream.emit+%28events.js%3A311%3A20%29%0A++engine+++++at+addChunk+%28_stream_readable.js%3A294%3A12%29%0A++engine+++++at+readableAddChunk+%28_stream_readable.js%3A275%3A11%29%0A++engine+++++at+LineStream.Readable.push+%28_stream_readable.js%3A209%3A10%29%0A++engine+++++at+LineStream.Transform.push+%28_stream_transform.js%3A152%3A32%29%0A++engine+++++at+LineStream._pushBuffer+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A23721%3A19%29%0A++engine+++++at+LineStream._transform+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A23715%3A10%29++%7B%22timestamp%22%3A%22Jan+15+17%3A04%3A51.789%22%2C%22level%22%3A%22ERROR%22%2C%22fields%22%3A%7B%22message%22%3A%22PANIC%22%2C%22reason%22%3A%22index+out+of+bounds%3A+the+len+is+1+but+the+index+is+1%22%2C%22file%22%3A%22%2Froot%2F.cargo%2Fgit%2Fcheckouts%2Fquaint-9f01e008b9a89c14%2Fbc3aa8a%2Fsrc%2Fconnector%2Fpostgres%2Ferror.rs%22%2C%22line%22%3A138%2C%22column%22%3A29%7D%2C%22target%22%3A%22query_engine%22%7D++%0A++engine+%7B%0A++engine+++error%3A+SocketError%3A+closed%0A++engine+++++++at+Socket.onSocketClose+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A24792%3A33%29%0A++engine+++++++at+Socket.emit+%28events.js%3A311%3A20%29%0A++engine+++++++at+Pipe.%3Canonymous%3E+%28net.js%3A668%3A12%29+%7B%0A++engine+++++name%3A+%27SocketError%27%2C%0A++engine+++++code%3A+%27UND_ERR_SOCKET%27%0A++engine+++%7D%0A++engine+%7D++%0A++engine+%7B%0A++engine+++error%3A+Error%3A+connect+ECONNREFUSED+%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%0A++engine+++++++at+PipeConnectWrap.afterConnect+%5Bas+oncomplete%5D+%28net.js%3A1137%3A16%29+%7B%0A++engine+++++errno%3A+%27ECONNREFUSED%27%2C%0A++engine+++++code%3A+%27ECONNREFUSED%27%2C%0A++engine+++++syscall%3A+%27connect%27%2C%0A++engine+++++address%3A+%27%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%27%0A++engine+++%7D%0A++engine+%7D++%0A++engine+Client+Version%3A+2.14.0++%0A++engine+Engine+Version%3A+query-engine+5d491261d382a2a5ffdc71de17072b0e409f1cc1++%0A++engine+Active+provider%3A+postgresql++%0A++engine+%7B%0A++engine+++error%3A+Error%3A+connect+ECONNREFUSED+%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%0A++engine+++++++at+PipeConnectWrap.afterConnect+%5Bas+oncomplete%5D+%28net.js%3A1137%3A16%29+%7B%0A++engine+++++errno%3A+%27ECONNREFUSED%27%2C%0A++engine+++++code%3A+%27ECONNREFUSED%27%2C%0A++engine+++++syscall%3A+%27connect%27%2C%0A++engine+++++address%3A+%27%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%27%0A++engine+++%7D%0A++engine+%7D++%2B1s%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A&title=PANIC+in+%2Froot%2F.cargo%2Fgit%2Fcheckouts%2Fquaint-9f01e008b9a89c14%2Fbc3aa8a%2Fsrc%2Fconnector%2Fpostgres%2Ferror.rs%3A138%3A29%0Aindex+out+of+bounds%3A+the+len+is+1+but+the+index+is+1&template=bug_report.mdhttps://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v12.16.1+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+darwin+++++++++++++%7C%0A%7C+Prisma+Client+++%7C+2.14.0+++++++++++++%7C%0A%7C+Query+Engine++++%7C+query-engine+5d491261d382a2a5ffdc71de17072b0e409f1cc1%7C%0A%7C+Database++++++++%7C+undefined%7C%0A%0A%0A%0A%23%23+Query%0A%60%60%60%0Amutation+%7B%0A++executeRaw%28%0A++++query%3A+%22X%22%0A++++parameters%3A+%22X%22%0A++%29%0A%7D%0A%60%60%60%0A%0A%23%23+Logs%0A%60%60%60%0A++tryLoadEnv+Environment+variables+loaded+from+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2F.env++%0A++tryLoadEnv+Environment+variables+loaded+from+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2F.env++%0A++prisma-client+%7B+clientVersion%3A+%272.14.0%27+%7D++%0A++engine+%7B+cwd%3A+%27%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fprisma%27+%7D++%0A++engine+Search+for+Query+Engine+in+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient++%0A++engine+Search+for+Query+Engine+in+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient++%0A++plusX+Execution+permissions+of+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine++%0A++plusX+Execution+permissions+of+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine++%0A++engine+%7B%0A++engine+++flags%3A+%5B%0A++engine+++++%27--enable-raw-queries%27%2C%0A++engine+++++%27--unix-path%27%2C%0A++engine+++++%27%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%27%0A++engine+++%5D%0A++engine+%7D++%0A++engine+stdout++Starting+a+postgresql+pool+with+13+connections.++%0A++engine+stdout++Started+http+server+on+http%2Bunix%3A%2F%2F%2Fprivate%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock++%0A++engine+Search+for+Query+Engine+in+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient++%0A++prisma-client+prisma.%24executeRaw%28SET+jwt.claims.user_id+%3D+10%2C+%5B%5D%29++%0A++prisma-client+Prisma+Client+call%3A++%0A++plusX+Execution+permissions+of+%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F.prisma%2Fclient%2Fquery-engine-darwin+are+fine++%0A++prisma-client+prisma.%24executeRaw%28select+jwt.claims.user_id%2C+%5B%5D%29++%0A++prisma-client+Prisma+Client+call%3A++%0A++engine+stdout++PANIC+in+%2Froot%2F.cargo%2Fgit%2Fcheckouts%2Fquaint-9f01e008b9a89c14%2Fbc3aa8a%2Fsrc%2Fconnector%2Fpostgres%2Ferror.rs%3A138%3A29%0Aindex+out+of+bounds%3A+the+len+is+1+but+the+index+is+1++%0A++engine+TypeError%3A+this.currentRequestPromise.cancel+is+not+a+function%0A++engine+++++at+NodeEngine.handlePanic+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A26344%3A36%29%0A++engine+++++at+NodeEngine.setError+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A26290%3A16%29%0A++engine+++++at+LineStream.%3Canonymous%3E+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A26585%3A24%29%0A++engine+++++at+LineStream.emit+%28events.js%3A311%3A20%29%0A++engine+++++at+addChunk+%28_stream_readable.js%3A294%3A12%29%0A++engine+++++at+readableAddChunk+%28_stream_readable.js%3A275%3A11%29%0A++engine+++++at+LineStream.Readable.push+%28_stream_readable.js%3A209%3A10%29%0A++engine+++++at+LineStream.Transform.push+%28_stream_transform.js%3A152%3A32%29%0A++engine+++++at+LineStream._pushBuffer+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A23721%3A19%29%0A++engine+++++at+LineStream._transform+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A23715%3A10%29++%7B%22timestamp%22%3A%22Jan+15+17%3A04%3A51.789%22%2C%22level%22%3A%22ERROR%22%2C%22fields%22%3A%7B%22message%22%3A%22PANIC%22%2C%22reason%22%3A%22index+out+of+bounds%3A+the+len+is+1+but+the+index+is+1%22%2C%22file%22%3A%22%2Froot%2F.cargo%2Fgit%2Fcheckouts%2Fquaint-9f01e008b9a89c14%2Fbc3aa8a%2Fsrc%2Fconnector%2Fpostgres%2Ferror.rs%22%2C%22line%22%3A138%2C%22column%22%3A29%7D%2C%22target%22%3A%22query_engine%22%7D++%0A++engine+%7B%0A++engine+++error%3A+SocketError%3A+closed%0A++engine+++++++at+Socket.onSocketClose+%28%2FUsers%2Fm%2FGo%2Fsrc%2Fgithub.com%2Fprisma%2Fissue-4303%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A24792%3A33%29%0A++engine+++++++at+Socket.emit+%28events.js%3A311%3A20%29%0A++engine+++++++at+Pipe.%3Canonymous%3E+%28net.js%3A668%3A12%29+%7B%0A++engine+++++name%3A+%27SocketError%27%2C%0A++engine+++++code%3A+%27UND_ERR_SOCKET%27%0A++engine+++%7D%0A++engine+%7D++%0A++engine+%7B%0A++engine+++error%3A+Error%3A+connect+ECONNREFUSED+%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%0A++engine+++++++at+PipeConnectWrap.afterConnect+%5Bas+oncomplete%5D+%28net.js%3A1137%3A16%29+%7B%0A++engine+++++errno%3A+%27ECONNREFUSED%27%2C%0A++engine+++++code%3A+%27ECONNREFUSED%27%2C%0A++engine+++++syscall%3A+%27connect%27%2C%0A++engine+++++address%3A+%27%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%27%0A++engine+++%7D%0A++engine+%7D++%0A++engine+Client+Version%3A+2.14.0++%0A++engine+Engine+Version%3A+query-engine+5d491261d382a2a5ffdc71de17072b0e409f1cc1++%0A++engine+Active+provider%3A+postgresql++%0A++engine+%7B%0A++engine+++error%3A+Error%3A+connect+ECONNREFUSED+%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%0A++engine+++++++at+PipeConnectWrap.afterConnect+%5Bas+oncomplete%5D+%28net.js%3A1137%3A16%29+%7B%0A++engine+++++errno%3A+%27ECONNREFUSED%27%2C%0A++engine+++++code%3A+%27ECONNREFUSED%27%2C%0A++engine+++++syscall%3A+%27connect%27%2C%0A++engine+++++address%3A+%27%2Ftmp%2Fprisma-309d86ec139dc8c202ae8134.sock%27%0A++engine+++%7D%0A++engine+%7D++%2B1s%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A&title=PANIC+in+%2Froot%2F.cargo%2Fgit%2Fcheckouts%2Fquaint-9f01e008b9a89c14%2Fbc3aa8a%2Fsrc%2Fconnector%2Fpostgres%2Ferror.rs%3A138%3A29%0Aindex+out+of+bounds%3A+the+len+is+1+but+the+index+is+1&template=bug_report.md

If you want the Prisma team to look into it, please open the link above 🙏
To increase the chance of success, please post your schema and a snippet of
how you used Prisma Client in the issue.

    at PrismaClientFetcher.request (/Users/m/Go/src/github.com/prisma/issue-4303/node_modules/@prisma/client/runtime/index.js:78134:15)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  clientVersion: '2.14.0'
}

How to reproduce

const { PrismaClient} = require('@prisma/client')

const client= new PrismaClient()

async function main() {
  await client.$connect()
  const id = 10
  await client.$executeRaw(`SET jwt.claims.user_id = ${id}`)
  const result = await client.$executeRaw(`select jwt.claims.user_id`)
  console.log(result)
}

main().catch(console.error).finally(() => client.$disconnect())

Expected behavior

Should be able to click on the issue to create an issue
Prisma information

Environment & setup

OS:
Database:
Node.js version:
Prisma version:

Environment variables loaded from .env
@prisma/cli          : 2.14.0
@prisma/client       : 2.14.0
Current platform     : darwin
Query Engine         : query-engine 5d491261d382a2a5ffdc71de17072b0e409f1cc1 (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 5d491261d382a2a5ffdc71de17072b0e409f1cc1 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 5d491261d382a2a5ffdc71de17072b0e409f1cc1 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 5d491261d382a2a5ffdc71de17072b0e409f1cc1 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Studio               : 0.332.0

I am unable to reproduce this. Might be specific to your shell/terminal.

I am unable to reproduce this. Might be specific to your shell/terminal.

Can you try using another terminal emulator?

Can you try using another terminal emulator?

Yep, I think you're right. False alarm. Sorry about that!

Yep, I think you're right. False alarm. Sorry about that!


Remove NonNullable LiveData classes

We should remove all NonNull LiveData classes and replace them with the basic counterparts since null checks are already done.

@michaelbukachi removed all NonNull LiveData classes. Cross check the develop branch

Awesome. Will do in the morning.

It's good. Let's wait for issue #65 before merging to master.

I've merged the the pull request.

Okay merging to master and closing this.


Create Mississippi-State

Feed for all things Mississippi State

Hey uhhh I'm pretty sure this is not how publishing a feed works.


Running locally with "grind serve" hangs during build

What happened?
I cloned dart-pad a few weeks ago and have run locally without any problems until recently when it started hanging when I enter grind serve, with output:
grinder running build serve

build
  .../flutter/bin/cache/dart-sdk/bin/pub run build_runner build -r -o web:build --delete-conflicting-outputs

I've left it for up to half an hour and it never gets past this point.  This is new behaviour, previously running grind serve has resulted in (from memory) some build output and "listening on 8080" or something similar.
Steps to reproduce problem
git clone git@github.com:dart-lang/dart-pad.git
cd dart-pad
dart pub get
grind serve

I have cloned a new version just now and tried on a few different computers and I get the same result.
Additional info
Machine
Operating system: macOS
Version: 11.3.1
flutter & dart

• Flutter version 2.3.0-12.1.pre at /Users/nick/SDKs/flutter

• Upstream repository https://github.com/flutter/flutter.git

• Framework revision f9c825981c (9 days ago), 2021-05-18 14:07:52 -0700

• Engine revision 26e217e6c3

• Dart version 2.14.0 (build 2.14.0-edge.a527411e5100a0a4f48c4009087a1b988aa784af)

Steps taken
In case it's useful, I tried running the first line of grind's build() command:
dart run build_runner build -r -o web:build --delete-conflicting-outputs
and got the following
output

[INFO] Generating build script completed, took 421ms
[WARNING] Deleted previous snapshot due to missing asset graph.
[INFO] Creating build script snapshot... completed, took 12.3s
[INFO] Building new asset graph completed, took 1.6s
[INFO] Checking for unexpected pre-existing outputs. completed, took 1ms
[WARNING] json_serializable:json_serializable on lib/workshops/src/github.dart:
Your current analyzer version may not fully support your current SDK version.
Please try upgrading to the latest analyzer by running flutter packages upgrade.
Analyzer language version: 2.12.0
SDK language version: 2.14.0
If you are getting this message and have the latest analyzer please file
an issue at https://github.com/dart-lang/sdk/issues/new with the title
"No published analyzer available for language version 2.14.0".
Please search the issue tracker first and thumbs up and/or subscribe to
existing issues if present to avoid duplicates.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[SEVERE] json_serializable:json_serializable on lib/workshops/src/github.dart:
Bad state: Unexpected diagnostics:
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - Operator declarations must be preceded by the keyword 'operator'.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:18 - A function body must be provided.
/Users/nick/SDKs/flutter/bin/cache/dart-sdk/lib/core/int.dart:117:16 - Methods must have an explicit list of parameters.
[WARNING] No actions completed for 15.1s, waiting on:

json_serializable:json_serializable on lib/workshops/src/fetcher.dart
json_serializable:json_serializable on lib/workshops/src/meta.dart
json_serializable:json_serializable on lib/workshops/src/fetcher_impl.dart
json_serializable:json_serializable on lib/workshops/src/web_server.dart
json_serializable:json_serializable on lib/workshops/src/exceptions.dart
.. and 11 more

[WARNING] No actions completed for 15.1s, waiting on:

json_serializable:json_serializable on lib/workshops/src/fetcher.dart
json_serializable:json_serializable on lib/workshops/src/meta.dart
json_serializable:json_serializable on lib/workshops/src/fetcher_impl.dart
json_serializable:json_serializable on lib/workshops/src/web_server.dart
json_serializable:json_serializable on lib/workshops/src/exceptions.dart
.. and 11 more

[WARNING] No actions completed for 15.0s, waiting on:

json_serializable:json_serializable on lib/workshops/src/fetcher.dart
json_serializable:json_serializable on lib/workshops/src/meta.dart
json_serializable:json_serializable on lib/workshops/src/fetcher_impl.dart
json_serializable:json_serializable on lib/workshops/src/web_server.dart
json_serializable:json_serializable on lib/workshops/src/exceptions.dart
.. and 11 more

[INFO] 55.3s elapsed, 1/17 actions completed.

Thanks! 🙂

Woohoo!  Switching to flutter stable channel did the trick... sorry for the noise! 🔉

I'm guessing this is related to https://github.com/google/dart-neats/issues/132
Just to confirm, you were running on Dart 2.14 or newer?

Hey @domesticmouse!

Just to confirm, you were running on Dart 2.14 or newer?

Correct!  2.14.0
Thanks 🙂


Using Graph

I have seen demos of using the Microsoft Graph to get staged rollout information. Could you please add some references on this page to the instructions for doing this?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3f2a7330-82fa-9c0d-0f34-b2a99ef13c64
Version Independent ID: d941f435-3443-02a1-57c0-7f4173173249
Content: Azure AD Connect: Cloud authentication via staged rollout
Content Source: articles/active-directory/hybrid/how-to-connect-staged-rollout.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@DeanGross
Thanks for your feedback! We will investigate and update as appropriate.

@DeanGross
Thank for submitting this. I have created a work item for it and will send this to engineering so that they can review it and provide me with updated details. I am not sure what the timeline will be, so I am going to close this for now. But once I have an update I will drop it in here and let you know.
Thank you!
Bill
#please-close


Monterey - Maccy does not appear in accessiblity list

Trying to turn on "paste automatically".  A popup will show asking for permission for Accessibility in Security and Privacy.  However, the app is not actually listed in the accessibility app list, and hence no permission can be granted.

Sorry, just realize this has been reported before. You can add the app manually.


Creating Groups in bulk using powershell

I have created a powershell script for creating groups.
I am using the following command in a for loop
New-UnifiedGroup -AccessType Public -Alias $groupIdentity -DisplayName $groupDisplayName -Owner $smtpAddress
I am trying to create a 1000 groups and executing above command for a single time takes around 8 seconds so creating 1000 takes a long time. Is there any command exist using which I can create Groups in bulk just using a single command.

@officedocsbot assign @yogkumgit

Hi @asajrawat211993, thank you for your feedback.
Sorry, there is now way to do it. Single line yes, but not single command.
Are you using something like "Import-Csv file.csv | New-UnifiedGroup -AccessType Public -Alias $.GroupIdentity -DisplayName $.GroupDisplayName -Owner $_.SmtpAddress"?

@dariomws306  Thank you very much for the contribution and sharing this explanation. @asajrawat211993 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Request for providing additional options

To improve firmware upload speed and reliability I propose to add the following parameters to UpgradeOptions:

Window capacity/pipeline depth (number); currently, the default value is 1. a higher value might increase the upload speed.
Byte alignment; currently, the default value of 1 (disabled) is used. Setting this to a value that corresponds to the byte alignment of the device might increase speed.
Request high connection priority (boolean); The Android 'Nordic Device Manager' App requests a high connection priority before starting the upgrade process. See here.

This would be great to see @sander48k.
We do have an item on our backlog to upgrade the underlying libraries so that we can expose these, but we haven't got to it yet.
I did some initial work in https://github.com/PlayerData/react-native-mcu-manager/pull/29 - I'd be happy if you'd like to take over with that?

@ball-hayden ; thanks for the Swift reply! I'll check if I can make some time to implement these changes.

Hi @ball-hayden ; I've been working on this a little this weekend. Now I see that my code changes are almost the same as yours in the branch you mention in #29, which is a good thing :). Only difference is that I made an enum for the byte alignment because that is restricted in iOS.
My first test shows a significant speed improvement on Android (which you also saw already). On iOS, using the latest version 1.2.9, it also seems to work fine although I haven't tested it thoroughly yet. I find it remarkable that it is required to start the update process on the main thread. Do you have any idea what the rationale behind that is?

No. There are many things that confuse me about Nordic's implementation.

The improvements to the update process are in this branch. It would be nice if the new upgrade options are available in the example project but I'm afraid I don't have time for that now. I'll create a PR if you want.

Thanks. Please do open a PR - I'd be happy to review that.


Added KadenaJS package list to README

Reason:
It was ludicrously hard to find a source of information that listed off all of the libraries (And planned libraries) in KadenaJS along with a description of what each one did.
I finally stumbled on the Contributions markdown file.
I just copied the data from there into the readme. The Readme definitely deserves to have that information. I'm not sure if makes sense in the contributions file.
Changes made (preferably with images/screenshots):
Add kadena js package list and descriptions to the main README so people can easily see what each piece does and find what they need faster.
Check off the following:

[x] I have reviewed my changes and run the appropriate tests.
[x] I have have run rush change to add the appropriate change logs.
[x] I have added/edited docs.
[x] I have added tutorials.
[x] I have double checked and DEFINITELY added docs.

I'm going to rebuild this properly.


Create a Using Log4j in Spring Boot guide

As agreed in the site structure document, create a "Using Log4j in Spring Boot" guide such that

Refer to the related sections of the Installation wherever possible (It already contains sufficient Spring Boot coverage)
Mention about lookups, starters, etc.
Target 2.x, port to main

This task was implemented in #2480 and #2487 as a part of MS13 (#2476).


BUG: update median averaging in signal.csd

Separately median-average real and imaginary components of complex
CSDs. This avoids unexpected behavior when np.median is passed a
complex array.

Reference issue
Closes #12669
What does this implement/fix?
Currently, when average='median' is passed to signal.csd, the CSD array is passed directly through np.median. This is fine for PSDs, which are always real, but for complex CSDs the resulting imaginary component is far too large. This is because np.median(Pxy) of a complex array Pxy does not return the same result as np.median(np.real(Pxy)) + 1j*np.median(np.imag(Pxy)), as might have been expected. For median averaging, this fix checks if the CSD array is complex, and if so it separately takes medians of the real and imaginary components and then recombines the result in to a complex median-averaged CSD.

looks like @e-q has some more knowledge/concerns about the exact nature of the fix in the cognature issue, so don't merge this yet

Having looked a little bit at the Wikipedia page about the issue, they mention three ways of computing the median:

Marginal, which just separates, computes median, and recombines (this solution)
Geometric, which is difficult to compute
Centerpoint, which is [also challenging to compute but there is at least one algorithm](file:///home/larsoner/Desktop/Jadhav-Mukhopadhyay1994_Article_ComputingACenterpointOfAFinite.pdf)

Given that what we do now is definitely wrong, I think as long as we document that we use the marginal median it's worth having this. @hadrev could you update the docstring for csd to mention this? Then I think we should merge.
Okay with you @e-q?

Yes, implementing and accurately documenting the marginal calculation is unambiguously better than our current state. Implementation of the other methods would be a welcome enhancement at any future point.

On Feb 22, 2021, at 08:23, Eric Larson<EMAIL_ADDRESS>wrote:

Having looked a little bit at the Wikipedia page about the issue, they mention three ways of computing the median:
Marginal, which just separates, computes median, and recombines (this solution)
Geometric, which is difficult to compute
Centerpoint, which is also challenging to compute but there is at least one algorithm
Given that what we do now is definitely wrong, I think as long as we document that we use the marginal median it's worth having this. @hadrev could you update the docstring for csd to mention this? Then I think we should merge.
Okay with you @e-q?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks all; the docstring is updated. I agree it would be a nice enhancement to have other medians available. The geometric median algorithms seem sufficiently involved that they likely deserve their own function (stats.gmedian, maybe?) that we could call from signal.csd.

Thanks @hadrev !


Different result for the POST call with the same AS3 JSON content

Environment

Application Services Version: 3.35.0 (the same issue connected to 3.34.x)
BIG-IP Version: 16.1.2

Summary
I'm using AS3 JSON for deploying services to BIGIP using Ansible. In some cases (when AS3 JSOn content is not correct from BIGIP point of view) is BIGIP's response different as expected. I'm not sure if this issue is connected to ansible module ansible.builtin.uri or f5-appsvcs-extension, but I think it's the same "POST call with the same JSON content". Maybe somebody can help me with this. I can't find the issue.
Steps To Reproduce
Steps to reproduce the behavior:

Submit the following declaration (see '<IP_ADDRESS>' double definition that is valid separately, but not both in the same content):

{
    "$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/master/schema/3.35.0/as3-schema.json",
    "class": "AS3",
    "action": "deploy",
    "persist": true,
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.35.0",
        "updateMode": "selective",
        "test-as3-01": {
            "class": "Tenant",
            "defaultRouteDomain": 5,
            "Shared": {
                "class": "Application",
                "template": "shared",
                "sf_testweb": {
                    "class": "Pool",
                    "remark": "testing pool",
                    "members": [
                        {
                            "remark": "AS3>Shared: blabla",
                            "servicePort": 8080,
                            "adminState": "enable",
                            "serverAddresses": [
                                "<IP_ADDRESS>"
                            ],
                            "servers": [
                                {
                                    "name": "rserver44",
                                    "address": "<IP_ADDRESS>"
                                }
                            ]
                        },
                        {
                            "remark": "AS3>Shared",
                            "servicePort": 8081,
                            "adminState": "enable",
                            "serverAddresses": [
                                "<IP_ADDRESS>",
                                "<IP_ADDRESS>"
                            ],
                            "servers": []
                        }
                    ]
                }
            }
        }
    }
}

Postman response is correct:

    "results": [
        {
            "code": 422,
            "message": "declaration failed",
            "response": "0107176c:3: Invalid Node, the IP address <IP_ADDRESS>%5 already exists.",
            "host": "localhost",
            "tenant": "test-as3-01",
            "runTime": 6662
        }
    ]

Ansible call response is different (wrong):

  "results": [
    {
      "code": 0,
      "message": "Declaration successfully submitted",
      "tenant": "",
      "host": "",
      "runTime": 0
    }
  ],

Ansible playbook for reproducing:
    - block:
        - name: "Deploy JSON file to device (URI)"
          ansible.builtin.uri:
            url: "https://{{ bigip_host }}:{{ provider.server_port }}/mgmt/shared/appsvcs/declare"
            method: POST
            body: "{{ lookup('file', JSON_FILE ) }}" # << this is absolute path to JSON file
            body_format: json
            status_code: [200, 201, 202, 422]
            timeout: 300
            return_content: true
            force_basic_auth: yes
            user: "{{ provider.user }}"
            password: "{{ provider.password }}"
            validate_certs: "{{ provider.validate_certs }}"
          register: DEPLOY_RESULT
          failed_when: DEPLOY_RESULT.status != 200
          tags:
            - deploy-debug
            - deploy

      rescue:
        - name: "(debug) ERROR: Deploy error"
          debug:
            msg:
              - "RESULTS: {{ DEPLOY_RESULT }}"
          tags:
            - deploy-debug

        - name: "ERROR: Deploy error"
          debug:
            msg:
              - "msg: {{ DEPLOY_RESULT.msg }}"
              - "results: {{ DEPLOY_RESULT.json.results }}"
          tags:
            - deploy-debug
            - deploy

Expected Behavior
The expected is the same result from Postman and Ansible (in both cases it is "the same URI call with the same content").
Actual Behavior
Postman's result and Ansible result's is different in case of 'incorrect' AS3 content. When the content of AS3 JSON is correct, both answers (Postman and Ansible) are the same (correct) result.

This appears to be a problem with the Ansible module and not AS3. Please file an issue with the Anisble module.

This appears to be a problem with the Ansible module and not AS3. Please file an issue with the Anisble module.

@dstokesf5 you are wrong in this case (see my second issue below). That's not "Ansible module issue". I'd like to share my investigation with other users here.
After some investigation I can confirm two issues on big-ip side. In both cases I'm playing with (very simple - only one pool with two members) correct AS3 configuration. You can find results below.
First issue - code 202
Bigip response to POST from Postman and Ansible is code 202 with "declaration successfullu submited", no tenant, no host - BUT no change is made to bigip. That's wrong. See result:
  "results": [
    {
      "code": 0,
      "message": "Declaration successfully submitted",
      "tenant": "",
      "host": "",
      "runTime": 0
    }
  ]

Solution:
bigip restart (restarting only restjavad or other services connected to REST was not helpful).
Note:
This "code 202, with declaration success, with no host and no tenant" is common for cases of trouble on bigip side. tcpdump on bigip shows "no declaration content" coming to "rest engine" (the same for postman and/or ansible). I think bigip was in "some strange state". After reboot is situation fixed. I have open service request on f5 support for this.
Second issue - Ansible with http basic authentication
REST calls authentication is possible by two ways:

http basic authentication method
token-based authentication

Both methods are working with local defined user (for Postman and Ansible with builtin.uri module described above). This is very common example on f5 labs. But for external user (authentication against tacacs/radius/...) is HTTP Basic not working! That's the core issue with Ansible module 'uri'.
This is confirmed by Postman - basic authentication with external user is not working. We are using 'netops user' defined on tacacs and therefore is our ansible call failing. I can't confirm, if it starts failing after upgrade f5-appsvc to latest version 3.35.0, but I think before (3.34.0) it was working (we need 3.35.0, because we need names for pool members and this feature is supported starting 3.35.0).
Solution:
Changing Ansible task from http basic to token based authentication is the solution. Now, is playbook's task with 'ansible.builtin.uri' module for POST-ing AS3 content working correctly (with token for authentication).
Ansible playbook with token based authentication here (Maybe for somebody can be helpful)
    - block:
        - name: "Get auth token"
          ansible.builtin.uri:
            url: "https://{{ bigip_host }}:{{ provider.server_port }}/mgmt/shared/authn/login"
            method: POST
            body: '{"username": "{{provider.user}}", "password": "{{provider.password}}", "loginProviderName": "tmos" }'
            body_format: json
            status_code: [200]
            timeout: 20
            return_content: true
            validate_certs: "{{ provider.validate_certs }}"
          register: AUTH_RESULT
          failed_when: AUTH_RESULT.status != 200
          check_mode: no

        - name: "DEBUG: Auth token"
          debug:
            msg:
              - "token:  {{ AUTH_RESULT.json.token.token }}"

        - name: "Token timeout to 5 min"
          ansible.builtin.uri:
            url: "https://{{ bigip_host }}:{{ provider.server_port }}/mgmt/shared/authz/tokens/{{AUTH_RESULT.json.token.token}}"
            method: PATCH
            body: '{ "timeout":"300" }'
            body_format: json
            headers:
              X-F5-Auth-Token: "{{ AUTH_RESULT.json.token.token }}"
            status_code: [200]
            timeout: 20
            return_content: true
            validate_certs: "{{ provider.validate_certs }}"
          check_mode: no

      when:
        - active_member is defined
        - active_member == true

      rescue:
        - name: "ERROR: Authentication fail"
          debug:
            msg:
              - "status:  {{ AUTH_RESULT.status }}"
              - "results: {{ AUTH_RESULT.json }}"

    - block:

        - name: "Deploy JSON file to device (URI)"
          ansible.builtin.uri:
            url: "https://{{ bigip_host }}:{{ provider.server_port }}/mgmt/shared/appsvcs/declare?controls.dryRun={{ansible_check_mode}}"
            method: POST
            body: "{{ lookup('file', JSON_FILE ) }}"
            headers:
              X-F5-Auth-Token: "{{ AUTH_RESULT.json.token.token }}"
            body_format: json
            status_code: [200]
            timeout: 300
            return_content: true
            validate_certs: "{{ provider.validate_certs }}"
          register: DEPLOY_RESULT
          failed_when: DEPLOY_RESULT.status != 200
          # no_log: true
          check_mode: no
          when:
            - active_member is defined
            - active_member == true
            - AUTH_RESULT.json.token.token is defined

        - name: "OK: Deploy result"
          debug:
            msg:
              - "status:  {{ DEPLOY_RESULT.status }}"
              - "msg:     {{ DEPLOY_RESULT.msg }}"
              - "results: {{ DEPLOY_RESULT.json.results }}"
          when:
            - active_member is defined
            - active_member == true
            - DEPLOY_RESULT.status is defined and DEPLOY_RESULT.status == 200

      rescue:
        - name: "(debug) ERROR: Deploy error"
          debug:
            msg:
              - "RESULTS: {{ DEPLOY_RESULT }}"

        - name: "ERROR: Deploy error"
          debug:
            msg:
              - "status:  {{ DEPLOY_RESULT.status }}"
              - "msg:     {{ DEPLOY_RESULT.msg }}"
              - "results: {{ DEPLOY_RESULT.json }}"

# good solution is to delete auth token after deploying AS3 content.
# I this case is timeout shorten from 1200sec (10 mins) to 600sec (5min) without deleting token by ansible.

A 202 status code means AS3 has accepted the request, but is still processing it. It looks like what you are seeing is AS3 switching from synchronous processing to asynchronous processing. It does that to avoid timeouts imposed by restnoded and/or restjavad.
From the Warnings, Notes, & Tips page:

Even if you have asynchronous mode set to false, after 45 seconds AS3 sets asynchronous mode to true (API swap), and returns an async response. This allows you to use GET to poll for status (you should see a 202 status until the declaration is complete). This typically occurs only with very large declarations or most declarations to BIG-IQ; if the declaration completes in less than 45 seconds, AS3 does not modify asynchronous mode.

API documentation for more information on 202 status code responses: https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/refguide/apidocs.html#tag/Configuration

Daniel, thank you for this! Good to know details about code 202. It's very helpful for me. Do you think, is there any reason to (always) POST declaration with pre-set async=true parameter? Is there any reason or benefit to prefer async=true against (default) async=false?
Maybe you are right and AS3 switched to async mode after 45 seconds (but in my case is AS3 content for test reason very short). Currently is hard to confirm it, but I changed my playbook - added new task after existing 'deploy'. It works very well - when response (from deploy task) is code 202, new task will wait and periodically check task by task ID until "success" (or response code != 200 or 202).
This is the additional task (initial DEPLOY_RESULT is coming from previous 'deploy' task):
        - name: "{{pb_prfx}}-03-03: Wait for async result"
          ansible.builtin.uri:
            url: "https://{{ bigip_host }}:{{ provider.server_port }}/mgmt/shared/appsvcs/task/{{DEPLOY_RESULT.json.id}}?controls.dryRun={{ansible_check_mode}}"
            method: GET
            headers:
              X-F5-Auth-Token: "{{ AUTH_RESULT.json.token.token }}"
            status_code: [200, 202]
            timeout: 300
            return_content: true
            validate_certs: "{{ provider.validate_certs }}"
          register: DEPLOY_RESULT
          failed_when: DEPLOY_RESULT.status != (200 or 202)
          until: DEPLOY_RESULT.json.results.0.message == "success"
          retries: 5
          delay: 10
          no_log: true
          check_mode: no
          tags:
            - deploy
            - deploy-debug
          when:
            - active_member is defined
            - active_member == true
            - DEPLOY_RESULT.status is defined and DEPLOY_RESULT.status == 202
            - DEPLOY_RESULT.json.id is defined

        - name: "OK: Deploy result (after async wait)"
          debug:
            msg:
              - "status:  {{ DEPLOY_RESULT.status }}"
              - "msg:     {{ DEPLOY_RESULT.msg | default('') }}"
              - "results: {{ DEPLOY_RESULT.json.results | default('') }}"
              - "id:      {{ DEPLOY_RESULT.json.id | default('') }}"
          when:
            - active_member is defined
            - active_member == true
            - DEPLOY_RESULT.status is defined
            - DEPLOY_RESULT.status == 200