fix momery bug btop_tiktokrv btop_tiktokrv_gaid

azkaban/dm/pseudo_package_to_other_business/btop_tiktokrv.sh

@@ -30,7 +30,7 @@ spark-submit --class mobvista.dmp.datasource.dm.BtopTiktokrv \
  --conf spark.default.parallelism=3000 \
  --conf spark.sql.shuffle.partitions=3000 \
  --conf spark.network.timeout=720s \
- --master yarn --deploy-mode cluster  --executor-memory 8g --driver-memory 6g  --executor-cores 5  --num-executors 70 \
+ --master yarn --deploy-mode cluster  --executor-memory 8g --driver-memory 10g  --executor-cores 5  --num-executors 70 \
  ../../${JAR} -begin_day ${begin_day}   -begin_day02 ${begin_day02}  -end_day ${end_day} -output01 ${OUTPUT_PATH01}  -output02 ${OUTPUT_PATH02}  -output03 ${OUTPUT_PATH03} -output04 ${OUTPUT_PATH04} -coalesce 200
 
 

azkaban/dm/pseudo_package_to_other_business/btop_tiktokrv_gaid.sh

@@ -29,7 +29,7 @@ spark-submit --class mobvista.dmp.datasource.dm.BtopTiktokrvGaid \
  --conf spark.sql.shuffle.partitions=3000 \
  --conf spark.driver.maxResultSize=4g \
  --conf spark.network.timeout=720s \
- --master yarn --deploy-mode cluster  --executor-memory 8g --driver-memory 6g  --executor-cores 5  --num-executors 70 \
+ --master yarn --deploy-mode cluster  --executor-memory 8g --driver-memory 10g  --executor-cores 5  --num-executors 70 \
  ../../${JAR} -begin_day ${begin_day}   -begin_day02 ${begin_day02}  -end_day ${end_day} -output01 ${OUTPUT_PATH01}  -output02 ${OUTPUT_PATH02}  -output03 ${OUTPUT_PATH03}  -coalesce 200