weixin_30553777

hive bug

SHELL$ hive -S -e “set” | grep warehouse
hive.metastore.warehouse.dir=/user/hive/warehouse
hive.warehouse.subdir.inherit.perms=false

Status: Running (Executing on YARN cluster with App id application_1510723060011_0082)

--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 .......... SUCCEEDED 1 1 0 0 0 0
Map 10 ......... SUCCEEDED 1 1 0 0 0 0
Map 2 .......... SUCCEEDED 1 1 0 0 0 0
Map 3 .......... SUCCEEDED 1 1 0 0 0 0
Map 4 .......... SUCCEEDED 1 1 0 0 0 0
Map 5 .......... SUCCEEDED 1 1 0 0 0 0
Map 6 .......... SUCCEEDED 1 1 0 0 0 0
Map 8 .......... SUCCEEDED 21 21 0 0 0 0
Map 9 .......... SUCCEEDED 2 2 0 0 0 0
Reducer 7 ...... SUCCEEDED 1 1 0 0 0 0
--------------------------------------------------------------------------------
VERTICES: 10/10 [==========================>>] 100% ELAPSED TIME: 13.72 s
--------------------------------------------------------------------------------
Loading data to table bridge.sods_to_cio_libor_hold partition (biz_date=20170628)
Failed with exception java.io.IOException: rename for src path: hdfs://mycluster/apps/hive/warehouse/bridge.db/sods_to_cio_libor_hold/biz_date=20170628/.hive-staging_hive_2017-11-16_10-06-19_248_4976600282215103377-1/-ext-10000/000008_0 to dest path:hdfs://mycluster/apps/hive/warehouse/bridge.db/sods_to_cio_libor_hold/biz_date=20170628/000008_0 returned false
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.MoveTask

om bridge got value #279
17/11/18 16:55:48 [main]: DEBUG ipc.ProtobufRpcEngine: Call: submitDAG took 370ms
17/11/18 16:55:48 [main]: INFO client.TezClient: Submitted dag to TezSession, sessionName=HIVE-f8697cdf-5cb6-4d3b-9ea6-db5bc976d944, applicationId=application_1510723060011_0609, dagName=Insert overwrite table bridge.sod...'X_CNBD'(Stage-1)
17/11/18 16:55:48 [main]: DEBUG service.AbstractService: Service: org.apache.hadoop.yarn.client.api.impl.YarnClientImpl entered state INITED
17/11/18 16:55:48 [main]: DEBUG service.AbstractService: Service: org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl entered state INITED
17/11/18 16:55:48 [main]: DEBUG ssl.FileBasedKeyStoresFactory: CLIENT TrustStore: /etc/security/clientKeys/all.jks
17/11/18 16:55:48 [main]: DEBUG impl.TimelineClientImpl: Cannot load customized ssl related configuration. Fallback to system-generic settings.
java.io.FileNotFoundException: /etc/security/clientKeys/all.jks (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.apache.hadoop.security.ssl.ReloadingX509TrustManager.loadTrustManager(ReloadingX509TrustManager.java:168)
at org.apache.hadoop.security.ssl.ReloadingX509TrustManager.(ReloadingX509TrustManager.java:86)
at org.apache.hadoop.security.ssl.FileBasedKeyStoresFactory.init(FileBasedKeyStoresFactory.java:211)
at org.apache.hadoop.security.ssl.SSLFactory.init(SSLFactory.java:151)
at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.initSslConnConfigurator(TimelineClientImpl.java:510)
at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.initConnConfigurator(TimelineClientImpl.java:486)
at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.serviceInit(TimelineClientImpl.java:272)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:163)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.tez.client.TezYarnClient.init(TezYarnClient.java:46)
at org.apache.tez.dag.api.client.DAGClientImpl.(DAGClientImpl.java:90)
at org.apache.tez.client.TezClient.submitDAGSession(TezClient.java:581)
at org.apache.tez.client.TezClient.submitDAG(TezClient.java:466)
at org.apache.hadoop.hive.ql.exec.tez.TezTask.submit(TezTask.java:446)
at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:181)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1745)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1491)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:739)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
17/11/18 16:55:48 [main]: INFO impl.TimelineClientImpl: Timeline service address: http://cnsz131375:8188/ws/v1/timeline/
17/11/18 16:55:48 [main]: DEBUG service.AbstractService: Service: org.apache.hadoop.yarn.client.api.impl.AHSClientImpl entered state INITED
17/11/18 16:55:48 [main]: DEBUG security.UserGroupInformation: PrivilegedAction as:bridge (auth:SIMPLE) from:org.apache.hadoop.yarn.client.RMProxy.getProxy(RMProxy.java:163)
17/11/18 16:55:48 [main]: DEBUG ipc.YarnRPC: Creating YarnRPC for org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC
17/11/18 16:55:48 [main]: DEBUG ipc.HadoopYarnProtoRPC: Creating a HadoopYarnProtoRpc proxy for protocol interface org.apache.hadoop.yarn.api.ApplicationClientProtocol
17/11/18 16:55:48 [main]: DEBUG ipc.Client: getting client out of cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:48 [main]: INFO client.AHSProxy: Connecting to Application History server at cnsz131375/10.25.167.173:10200
17/11/18 16:55:48 [main]: DEBUG security.UserGroupInformation: PrivilegedAction as:bridge (auth:SIMPLE) from:org.apache.hadoop.yarn.client.AHSProxy.getProxy(AHSProxy.java:49)
17/11/18 16:55:48 [main]: DEBUG ipc.YarnRPC: Creating YarnRPC for org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC
17/11/18 16:55:48 [main]: DEBUG ipc.HadoopYarnProtoRPC: Creating a HadoopYarnProtoRpc proxy for protocol interface org.apache.hadoop.yarn.api.ApplicationHistoryProtocol
17/11/18 16:55:48 [main]: DEBUG ipc.Client: getting client out of cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:48 [main]: DEBUG service.AbstractService: Service org.apache.hadoop.yarn.client.api.impl.AHSClientImpl is started
17/11/18 16:55:48 [main]: DEBUG hdfs.BlockReaderLocal: dfs.client.use.legacy.blockreader.local = false
17/11/18 16:55:48 [main]: DEBUG hdfs.BlockReaderLocal: dfs.client.read.shortcircuit = true
17/11/18 16:55:48 [main]: DEBUG hdfs.BlockReaderLocal: dfs.client.domain.socket.data.traffic = false
17/11/18 16:55:48 [main]: DEBUG hdfs.BlockReaderLocal: dfs.domain.socket.path = /seabox/var/lib/hadoop-hdfs/dn_socket
17/11/18 16:55:48 [main]: DEBUG hdfs.HAUtil: No HA service delegation token found for logical URI hdfs://mycluster
17/11/18 16:55:48 [main]: DEBUG hdfs.BlockReaderLocal: dfs.client.use.legacy.blockreader.local = false
17/11/18 16:55:48 [main]: DEBUG hdfs.BlockReaderLocal: dfs.client.read.shortcircuit = true
17/11/18 16:55:48 [main]: DEBUG hdfs.BlockReaderLocal: dfs.client.domain.socket.data.traffic = false
17/11/18 16:55:48 [main]: DEBUG hdfs.BlockReaderLocal: dfs.domain.socket.path = /seabox/var/lib/hadoop-hdfs/dn_socket
17/11/18 16:55:48 [main]: DEBUG retry.RetryUtils: multipleLinearRandomRetry = MultipleLinearRandomRetry[500x2000ms]
17/11/18 16:55:48 [main]: DEBUG ipc.Client: getting client out of cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:48 [main]: DEBUG sasl.DataTransferSaslUtil: DataTransferProtocol not using SaslPropertiesResolver, no QOP found in configuration for dfs.data.transfer.protection
17/11/18 16:55:48 [main]: DEBUG ipc.Client: The ping interval is 60000 ms.
17/11/18 16:55:48 [main]: DEBUG ipc.Client: Connecting to cnsz131375/10.25.167.173:8020
17/11/18 16:55:48 [IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge: starting, having connections 8
17/11/18 16:55:48 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge sending #280
17/11/18 16:55:48 [IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge got value #280
17/11/18 16:55:48 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getFileInfo took 2ms
17/11/18 16:55:48 [main]: DEBUG impl.FileSystemTimelineWriter: yarn.timeline-service.client.fd-flush-interval-secs=10, yarn.timeline-service.client.fd-clean-interval-secs=60, yarn.timeline-service.client.fd-retain-secs=300, yarn.timeline-service.entity-file.fs-support-append=true, yarn.timeline-service.entity-group-fs-store.active-dir=/ats/active
17/11/18 16:55:48 [main]: DEBUG service.AbstractService: Service org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl is started
17/11/18 16:55:48 [main]: DEBUG service.AbstractService: Service org.apache.hadoop.yarn.client.api.impl.YarnClientImpl is started
17/11/18 16:55:48 [main]: INFO log.PerfLogger:

17/11/18 16:55:48 [main]: INFO SessionState:

17/11/18 16:55:48 [main]: INFO log.PerfLogger:
17/11/18 16:55:48 [main]: INFO log.PerfLogger:
17/11/18 16:55:48 [main]: DEBUG ipc.Client: The ping interval is 60000 ms.
17/11/18 16:55:48 [main]: DEBUG ipc.Client: Connecting to cnsz131375/10.25.167.173:8032
17/11/18 16:55:48 [main]: WARN ipc.Client: Failed to connect to server: cnsz131375/10.25.167.173:8032: retries get failed due to exceeded maximum allowed retries number: 0
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
at org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
at org.apache.hadoop.ipc.Client.call(Client.java:1449)
at org.apache.hadoop.ipc.Client.call(Client.java:1396)
at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
at com.sun.proxy.$Proxy27.getApplicationReport(Unknown Source)
at org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getApplicationReport(ApplicationClientProtocolPBClientImpl.java:191)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:278)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:194)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:176)
at com.sun.proxy.$Proxy28.getApplicationReport(Unknown Source)
at org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.getApplicationReport(YarnClientImpl.java:436)
at org.apache.tez.client.TezYarnClient.getApplicationReport(TezYarnClient.java:89)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.getAppReport(DAGClientRPCImpl.java:231)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.createAMProxyIfNeeded(DAGClientRPCImpl.java:251)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.getDAGStatus(DAGClientRPCImpl.java:96)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatusViaAM(DAGClientImpl.java:367)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatusInternal(DAGClientImpl.java:227)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatus(DAGClientImpl.java:275)
at org.apache.hadoop.hive.ql.exec.tez.TezTask$SyncDagClient.getDAGStatus(TezTask.java:616)
at org.apache.hadoop.hive.ql.exec.tez.TezJobMonitor.monitorExecution(TezJobMonitor.java:295)
at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:186)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1745)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1491)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:739)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
17/11/18 16:55:48 [main]: DEBUG ipc.Client: closing ipc connection to cnsz131375/10.25.167.173:8032: Connection refused
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
at org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
at org.apache.hadoop.ipc.Client.call(Client.java:1449)
at org.apache.hadoop.ipc.Client.call(Client.java:1396)
at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
at com.sun.proxy.$Proxy27.getApplicationReport(Unknown Source)
at org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getApplicationReport(ApplicationClientProtocolPBClientImpl.java:191)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:278)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:194)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:176)
at com.sun.proxy.$Proxy28.getApplicationReport(Unknown Source)
at org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.getApplicationReport(YarnClientImpl.java:436)
at org.apache.tez.client.TezYarnClient.getApplicationReport(TezYarnClient.java:89)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.getAppReport(DAGClientRPCImpl.java:231)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.createAMProxyIfNeeded(DAGClientRPCImpl.java:251)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.getDAGStatus(DAGClientRPCImpl.java:96)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatusViaAM(DAGClientImpl.java:367)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatusInternal(DAGClientImpl.java:227)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatus(DAGClientImpl.java:275)
at org.apache.hadoop.hive.ql.exec.tez.TezTask$SyncDagClient.getDAGStatus(TezTask.java:616)
at org.apache.hadoop.hive.ql.exec.tez.TezJobMonitor.monitorExecution(TezJobMonitor.java:295)
at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:186)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1745)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1491)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:739)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
17/11/18 16:55:48 [main]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8032 from bridge: closed
17/11/18 16:55:48 [main]: DEBUG retry.RetryInvocationHandler: Exception while invoking ApplicationClientProtocolPBClientImpl.getApplicationReport over rm1. Trying to failover immediately.
java.net.ConnectException: Call From cnsz131372/10.25.167.170 to cnsz131375:8032 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:801)
at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:732)
at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1556)
at org.apache.hadoop.ipc.Client.call(Client.java:1496)
at org.apache.hadoop.ipc.Client.call(Client.java:1396)
at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
at com.sun.proxy.$Proxy27.getApplicationReport(Unknown Source)
at org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getApplicationReport(ApplicationClientProtocolPBClientImpl.java:191)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:278)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:194)
at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:176)
at com.sun.proxy.$Proxy28.getApplicationReport(Unknown Source)
at org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.getApplicationReport(YarnClientImpl.java:436)
at org.apache.tez.client.TezYarnClient.getApplicationReport(TezYarnClient.java:89)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.getAppReport(DAGClientRPCImpl.java:231)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.createAMProxyIfNeeded(DAGClientRPCImpl.java:251)
at org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.getDAGStatus(DAGClientRPCImpl.java:96)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatusViaAM(DAGClientImpl.java:367)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatusInternal(DAGClientImpl.java:227)
at org.apache.tez.dag.api.client.DAGClientImpl.getDAGStatus(DAGClientImpl.java:275)
at org.apache.hadoop.hive.ql.exec.tez.TezTask$SyncDagClient.getDAGStatus(TezTask.java:616)
at org.apache.hadoop.hive.ql.exec.tez.TezJobMonitor.monitorExecution(TezJobMonitor.java:295)
at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:186)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:160)
at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:89)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1745)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1491)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1289)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1156)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1146)
at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:216)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:168)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:379)
at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:739)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:684)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:624)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
at org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
at org.apache.hadoop.ipc.Client.call(Client.java:1449)
... 42 more
17/11/18 16:55:48 [main]: INFO client.ConfiguredRMFailoverProxyProvider: Failing over to rm2
17/11/18 16:55:48 [main]: DEBUG security.UserGroupInformation: PrivilegedAction as:bridge (auth:SIMPLE) from:org.apache.hadoop.yarn.client.RMProxy.getProxy(RMProxy.java:163)
17/11/18 16:55:48 [main]: DEBUG ipc.YarnRPC: Creating YarnRPC for org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC
17/11/18 16:55:48 [main]: DEBUG ipc.HadoopYarnProtoRPC: Creating a HadoopYarnProtoRpc proxy for protocol interface org.apache.hadoop.yarn.api.ApplicationClientProtocol
17/11/18 16:55:48 [main]: DEBUG ipc.Client: getting client out of cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:48 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131376/10.25.167.174:8032 from bridge sending #282
17/11/18 16:55:48 [IPC Client (1990421361) connection to cnsz131376/10.25.167.174:8032 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131376/10.25.167.174:8032 from bridge got value #282
17/11/18 16:55:48 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getApplicationReport took 0ms
17/11/18 16:55:48 [main]: DEBUG rpc.DAGClientRPCImpl: App: application_1510723060011_0609 in state: RUNNING
17/11/18 16:55:48 [main]: DEBUG client.TezClientUtils: Connecting to Tez AM at cnsz131372/10.25.167.170:43571
17/11/18 16:55:48 [main]: DEBUG security.UserGroupInformation: PrivilegedAction as:bridge (auth:SIMPLE) from:org.apache.tez.client.TezClientUtils.getAMProxy(TezClientUtils.java:908)
17/11/18 16:55:48 [main]: DEBUG ipc.Client: getting client out of cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:48 [main]: DEBUG rpc.DAGClientRPCImpl: GetDAGStatus via AM for app: application_1510723060011_0609 dag:dag_1510723060011_0609_1
17/11/18 16:55:48 [main]: DEBUG ipc.Client: The ping interval is 60000 ms.
17/11/18 16:55:48 [main]: DEBUG ipc.Client: Connecting to cnsz131372/10.25.167.170:43571
17/11/18 16:55:48 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge: starting, having connections 9
17/11/18 16:55:48 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #283
17/11/18 16:55:48 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #283
17/11/18 16:55:48 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getDAGStatus took 165ms
17/11/18 16:55:48 [main]: INFO log.PerfLogger:
Status: Running (Executing on YARN cluster with App id application_1510723060011_0609)

17/11/18 16:55:48 [main]: INFO SessionState: Status: Running (Executing on YARN cluster with App id application_1510723060011_0609)

--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITIALIZING -1 0 0 -1 0 0
Map 2 INITIALIZING -1 0 0 -1 0 0
Map 3 INITIALIZING -1 0 0 -1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
Map 2 INITED 1 0 0 1 0 0
Map 3 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0p: application_1510723060011_0609 dag:dag_1510723060011_0609_1
Map 2 INITED 1 0 0 1 0 0t (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #284
Map 3 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0p: application_1510723060011_0609 dag:dag_1510723060011_0609_1
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0/1 Map 3: 0/1 Map 4: 0/1 Map 5: 0/1 Map 6: 0/1 Map 8: 0/21 Map 9: 0/2 Reducer
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
Map 1 INITIALIZING -1 0 0 -1 0 0
Map 10 INITED 1 0 0 1 0 0
Map 2 INITED 1 0 0 1 0 0
Map 3 INITED 1 0 0 1 0 0p: application_1510723060011_0609 dag:dag_1510723060011_0609_1
Map 4 INITED 1 0 0 1 0 0t (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #294
Map 5 INITED 1 0 0 1 0 0
Map 6 INITED 1 0 0 1 0 0
Map 8 INITED 21 0 0 21 0 0
Map 9 INITED 2 0 0 2 0 0p: application_1510723060011_0609 dag:dag_1510723060011_0609_1
Reducer 7 INITED 2 0 0 2 0 0t (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #295
--------------------------------------------------------------------------------
VERTICES: 00/10 [>>--------------------------] 0% ELAPSED TIME: 2.44 s
--------------------------------------------------------------------------------
VERTICES STATUS TOTAL COMPLETED RUNNING PENDING FAILED KILLED
--------------------------------------------------------------------------------
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 1
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #298
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #298T handler]: DEBUG rpc.DAGClientRPCImpl: TryKill for app: application_1510723060011_0609 dag:dag_1510723060011_0609_1
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 19ms0421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #296
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 10z131372/10.25.167.170:43571 fr17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #299
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #299: DEBUG rpc.DAGClientRPCImpl: GetDAGStatus via AM for app: application_1510723060011_0609 dag:dag_1510723060011_0609_1
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 1ms90421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #297
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 2sz131372/10.25.167.170:43571 fr17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #300
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #300
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 1ms
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 3
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #301
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #301
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 0ms
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 4
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #302
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #302
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 1ms
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 5
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #303
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #303
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 0ms
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 6
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #304
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #304
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 1ms
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 8
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #305
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #305
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 0ms
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Map 9
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #306
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #306
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 1ms
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetVertexStatus via AM for app: application_1510723060011_0609 dag: dag_1510723060011_0609_1 vertex: Reducer 7
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #307
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #307
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getVertexStatus took 0ms
Map 1 KILLED -1 0 0 -1 0 0
Map 10 KILLED 1 0 0 1 0 0
Map 2 KILLED 1 0 0 1 0 0
Map 3 KILLED 1 0 0 1 0 0
Map 4 KILLED 1 0 0 1 0 0
Map 5 KILLED 1 0 0 1 0 0
Map 6 KILLED 1 0 0 1 0 0
Map 8 KILLED 21 0 0 21 0 0
Map 9 KILLED 2 0 0 2 0 0
Reducer 7 KILLED 2 0 0 2 0 0
--------------------------------------------------------------------------------
VERTICES: 00/10 [>>--------------------------] 0% ELAPSED TIME: 2.69 s
--------------------------------------------------------------------------------
Status: Killed
17/11/18 16:55:51 [main]: INFO SessionState: Status: Killed
Job received Kill while in RUNNING state.
17/11/18 16:55:51 [main]: ERROR SessionState: Job received Kill while in RUNNING state.
Vertex killed, vertexName=Map 8, vertexId=vertex_1510723060011_0609_1_09, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1510723060011_0609_1_09 [Map 8] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 8, vertexId=vertex_1510723060011_0609_1_09, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1510723060011_0609_1_09 [Map 8] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Map 1, vertexId=vertex_1510723060011_0609_1_08, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1510723060011_0609_1_08 [Map 1] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 1, vertexId=vertex_1510723060011_0609_1_08, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1510723060011_0609_1_08 [Map 1] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Reducer 7, vertexId=vertex_1510723060011_0609_1_05, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:2, Vertex vertex_1510723060011_0609_1_05 [Reducer 7] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Reducer 7, vertexId=vertex_1510723060011_0609_1_05, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:2, Vertex vertex_1510723060011_0609_1_05 [Reducer 7] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Map 10, vertexId=vertex_1510723060011_0609_1_01, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_01 [Map 10] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 10, vertexId=vertex_1510723060011_0609_1_01, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_01 [Map 10] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Map 5, vertexId=vertex_1510723060011_0609_1_02, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_02 [Map 5] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 5, vertexId=vertex_1510723060011_0609_1_02, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_02 [Map 5] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Map 4, vertexId=vertex_1510723060011_0609_1_03, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_03 [Map 4] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 4, vertexId=vertex_1510723060011_0609_1_03, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_03 [Map 4] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Map 6, vertexId=vertex_1510723060011_0609_1_04, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_04 [Map 6] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 6, vertexId=vertex_1510723060011_0609_1_04, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_04 [Map 6] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Map 9, vertexId=vertex_1510723060011_0609_1_00, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:2, Vertex vertex_1510723060011_0609_1_00 [Map 9] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 9, vertexId=vertex_1510723060011_0609_1_00, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:2, Vertex vertex_1510723060011_0609_1_00 [Map 9] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Map 3, vertexId=vertex_1510723060011_0609_1_06, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_06 [Map 3] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 3, vertexId=vertex_1510723060011_0609_1_06, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_06 [Map 3] killed/failed due to:DAG_KILL]
Vertex killed, vertexName=Map 2, vertexId=vertex_1510723060011_0609_1_07, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_07 [Map 2] killed/failed due to:DAG_KILL]
17/11/18 16:55:51 [main]: ERROR SessionState: Vertex killed, vertexName=Map 2, vertexId=vertex_1510723060011_0609_1_07, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_07 [Map 2] killed/failed due to:DAG_KILL]
DAG did not succeed due to DAG_KILL. failedVertices:0 killedVertices:10
17/11/18 16:55:51 [main]: ERROR SessionState: DAG did not succeed due to DAG_KILL. failedVertices:0 killedVertices:10
17/11/18 16:55:51 [main]: INFO log.PerfLogger:
17/11/18 16:55:51 [main]: DEBUG rpc.DAGClientRPCImpl: GetDAGStatus via AM for app: application_1510723060011_0609 dag:dag_1510723060011_0609_1
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge sending #308
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131372/10.25.167.170:43571 from bridge got value #308
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: getDAGStatus took 1ms
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge sending #309
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge got value #309
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: delete took 1ms
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge sending #310
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge got value #310
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: delete took 0ms
17/11/18 16:55:51 [main]: DEBUG ipc.Client: stopping client from cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:51 [main]: DEBUG service.AbstractService: Service: org.apache.hadoop.yarn.client.api.impl.YarnClientImpl entered state STOPPED
17/11/18 16:55:51 [main]: DEBUG ipc.Client: stopping client from cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:51 [main]: DEBUG ipc.Client: stopping client from cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:51 [main]: DEBUG service.AbstractService: Service: org.apache.hadoop.yarn.client.api.impl.AHSClientImpl entered state STOPPED
17/11/18 16:55:51 [main]: DEBUG ipc.Client: stopping client from cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:51 [main]: DEBUG service.AbstractService: Service: org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl entered state STOPPED
17/11/18 16:55:51 [main]: DEBUG impl.FileSystemTimelineWriter: Closing cache
17/11/18 16:55:51 [main]: DEBUG ipc.Client: stopping client from cache: org.apache.hadoop.ipc.Client@a77614d
17/11/18 16:55:51 [main]: INFO hooks.ATSHook: Created ATS Hook
17/11/18 16:55:51 [main]: INFO log.PerfLogger:
17/11/18 16:55:51 [main]: INFO log.PerfLogger:
17/11/18 16:55:51 [ATS Logger 0]: INFO hooks.ATSHook: Received post-hook notification for :bridge_20171118165543_29ad0d2b-ae72-466b-9139-210b176ff364
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask. Job received Kill while in RUNNING state.Vertex killed, vertexName=Map 8, vertexId=vertex_1510723060011_0609_1_09, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1510723060011_0609_1_09 [Map 8] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 1, vertexId=vertex_1510723060011_0609_1_08, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1510723060011_0609_1_08 [Map 1] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Reducer 7, vertexId=vertex_1510723060011_0609_1_05, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:2, Vertex vertex_1510723060011_0609_1_05 [Reducer 7] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 10, vertexId=vertex_1510723060011_0609_1_01, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_01 [Map 10] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 5, vertexId=vertex_1510723060011_0609_1_02, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_02 [Map 5] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 4, vertexId=vertex_1510723060011_0609_1_03, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_03 [Map 4] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 6, vertexId=vertex_1510723060011_0609_1_04, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_04 [Map 6] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 9, vertexId=vertex_1510723060011_0609_1_00, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:2, Vertex vertex_1510723060011_0609_1_00 [Map 9] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 3, vertexId=vertex_1510723060011_0609_1_06, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_06 [Map 3] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 2, vertexId=vertex_1510723060011_0609_1_07, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_07 [Map 2] killed/failed due to:DAG_KILL]DAG did not succeed due to DAG_KILL. failedVertices:0 killedVertices:10
17/11/18 16:55:51 [main]: ERROR ql.Driver: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask. Job received Kill while in RUNNING state.Vertex killed, vertexName=Map 8, vertexId=vertex_1510723060011_0609_1_09, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1510723060011_0609_1_09 [Map 8] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 1, vertexId=vertex_1510723060011_0609_1_08, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1510723060011_0609_1_08 [Map 1] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Reducer 7, vertexId=vertex_1510723060011_0609_1_05, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:2, Vertex vertex_1510723060011_0609_1_05 [Reducer 7] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 10, vertexId=vertex_1510723060011_0609_1_01, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_01 [Map 10] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 5, vertexId=vertex_1510723060011_0609_1_02, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_02 [Map 5] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 4, vertexId=vertex_1510723060011_0609_1_03, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_03 [Map 4] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 6, vertexId=vertex_1510723060011_0609_1_04, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_04 [Map 6] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 9, vertexId=vertex_1510723060011_0609_1_00, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:2, Vertex vertex_1510723060011_0609_1_00 [Map 9] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 3, vertexId=vertex_1510723060011_0609_1_06, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_06 [Map 3] killed/failed due to:DAG_KILL]Vertex killed, vertexName=Map 2, vertexId=vertex_1510723060011_0609_1_07, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to DAG_KILL, failedTasks:0 killedTasks:1, Vertex vertex_1510723060011_0609_1_07 [Map 2] killed/failed due to:DAG_KILL]DAG did not succeed due to DAG_KILL. failedVertices:0 killedVertices:10
17/11/18 16:55:51 [main]: DEBUG ql.Driver: Shutting down query Insert overwrite table bridge.sods_to_cio_libor_hold partition(biz_date=20170606)
SELECT 'CNY',
'3002' AS COMPANY_REPORT, --数据上报公司
'3002' AS COMPANY_MANAGER, --投资管理公司
'3002' AS COMPANY_OWNER, --投资主体公司
P1.MAPPING_KEY AS BUSINESS_LINE, --业务线
CASE
WHEN T1.TRDTYPE in ('42', '82', '84') THEN '01001002'
WHEN T1.TRDTYPE in ('43', '83', '85') THEN '01001003'
END AS DETAIL_ASSET_TYPE, --明细资产分类
CASE p2.mapping_key
WHEN '005' THEN '001'
ELSE '001'
END AS FUND_SOURCE, --资金来源, 把005修改成001后上报，001保持不变
P.PORTFOLIO_UNITS AS PORTFOLIO_UNITS, --投资组合
T1.I_CODE AS SECURITY_ID, --证券代码,给流水号
T1.I_CODE AS SECURITY_NAME, --证券名称,给流水号
nvl(T20.TARGET_CODE,'OTHER') AS MARKET_NO, --市场代码
nvl(T20.TARGET_NAME,'其他') AS MARKET_NAME, --市场名称
oc.partyname AS COUNTER_PARTY, --交易对手名称
T1.partyid AS COUNTER_PARTY_ID, --交易对手组织机构代码
T2.AMOUNT AS HOLDING_UNITS, --持仓数量PAR_VALUE
T2.AMOUNT AS BOOK_BALANCE_N, --财务账面余额_本币AMOUNT
T2.AMOUNT AS BOOK_BALANCE_B, --财务账面余额_本币AMOUNT
T2.AMOUNT AS FINANCIAL_COST_ACCOUNT_N, --参考财务成本_原币AMOUNT
T2.AMOUNT AS FINANCIAL_COST_ACCOUNT_B, --参考财务成本_本币AMOUNT
round(ABS((T2.AIAMOUNT / T2.TERM * ((datediff(TO_DATE('2017-06-30'),TO_DATE(T2.FSTSETDATE)))+1)) ), 2) ACCRUE_INTEREST_N, --应计利息_原币
round(ABS((T2.AIAMOUNT / T2.TERM * ((datediff(TO_DATE('2017-06-30'),TO_DATE(T2.FSTSETDATE)))+1)) ), 2) ACCRUE_INTEREST_B --应计利息_本币
FROM bridge.FBMS_A_TTRD_OTC_TRADE_IB T1
INNER JOIN bridge.FBMS_A_TTRD_OTC_IBLB_IB T2 ON T2.I_CODE = T1.INTORDID
AND T2.M_TYPE = T1.M_TYPE
AND T2.A_TYPE = T1.A_TYPE
AND T2.ENDSETDATE > TO_DATE('2017-06-30') --投资组合映射主表
left join (select v1.accountid, v2.murex_leaf, v2.Third_Business_Line as business_line, v2.portfolio_units, v2.fund_source, v2.account_class
from bridge.BRIDGE_APP_PORTFOLIOACCOUNT_ib v1
inner join bridge.bridge_murex_leaf_config v2 on v1.portfolioid = v2.murex_leaf
and ascii(v2.is_send_group) = -26
and v1.biz_date = v2.biz_date
where '20170630' = v2.biz_date) p on p.accountid = t1.secu_accid
--业务线
left join (select col_name, tabname_cn as chinese_name, tabno as mapping_key from bridge.bridge_murex_leaf_mapping_ib where col_name = 'BUSINESS_LINE' and '20170630' = biz_date) p1 on p.business_line = p1.chinese_name
--资金来源
left join (select col_name, tabname_cn as chinese_name, tabno as mapping_key from bridge.bridge_murex_leaf_mapping_ib where col_name = 'FUND_SOURCE' and '20170630' = biz_date) p2 on p.fund_source = p2.chinese_name
--会计分类
left join (select col_name, tabname_cn as chinese_name, tabno as mapping_key from bridge.bridge_murex_leaf_mapping_ib where col_name = 'ACCOUNT_CLASS' and '20170630' = biz_date) p3 on p.account_class = p3.chinese_name
--交易对手(交易对手SUMMIT使用的是衡泰的数据源，衡泰是从交易中心获取的，可以通用)
left join (select max(partyname) as partyname, partyid from bridge.FBMS_A_TTRD_OTC_COUNTERPARTY_IB where '20170630' = biz_date group by partyid) oc on t1.partyid = oc.partyid

left join bridge.bridge_security_to_cio_mapping_ib T20
on T1.M_TYPE = T20.SOURCE_CODE
and T20.SOURCE_SYSTEM_CODE = 'FBMS'
and T20.MAPPING_TYPE ='MARKET_NO'
and T20.SOURCE_COLUMN_NAME = 'M_TYPE'
and T20.SOURCE_TABLE_NAME = 'FBMS_A_TTRD_OTC_TRADE_IB'
and T20.biz_date='20170630'
WHERE T1.ORDSOURCE NOT IN ('4', '11') --过滤掉投顾指令单
AND T1.ORDSTATUS = '7'
AND T1.A_TYPE in ('SPT_IBOR')
AND T1.M_TYPE = 'X_CNBD'

17/11/18 16:55:51 [ATS Logger 0]: DEBUG security.UserGroupInformation: PrivilegedAction as:bridge (auth:SIMPLE) from:org.apache.hadoop.yarn.client.api.impl.TimelineWriter.doPosting(TimelineWriter.java:112)
17/11/18 16:55:51 [main]: INFO ql.Driver: Resetting the caller context to
17/11/18 16:55:51 [ATS Logger 0]: DEBUG impl.TimelineWriter: POST to http://cnsz131375:8188/ws/v1/timeline/
17/11/18 16:55:51 [main]: INFO metadata.Hive: Dumping metastore api call timing information for : execution phase
17/11/18 16:55:51 [main]: DEBUG metadata.Hive: Total time spent in each metastore function (ms): {isCompatibleWith_(HiveConf, )=0}
17/11/18 16:55:51 [main]: INFO log.PerfLogger:
17/11/18 16:55:51 [main]: INFO log.PerfLogger:
17/11/18 16:55:51 [main]: INFO log.PerfLogger:
17/11/18 16:55:51 [main]: DEBUG ql.Driver: Shutting down query Insert overwrite table bridge.sods_to_cio_libor_hold partition(biz_date=20170606)
SELECT 'CNY',
'3002' AS COMPANY_REPORT, --数据上报公司
'3002' AS COMPANY_MANAGER, --投资管理公司
'3002' AS COMPANY_OWNER, --投资主体公司
P1.MAPPING_KEY AS BUSINESS_LINE, --业务线
CASE
WHEN T1.TRDTYPE in ('42', '82', '84') THEN '01001002'
WHEN T1.TRDTYPE in ('43', '83', '85') THEN '01001003'
END AS DETAIL_ASSET_TYPE, --明细资产分类
CASE p2.mapping_key
WHEN '005' THEN '001'
ELSE '001'
END AS FUND_SOURCE, --资金来源, 把005修改成001后上报，001保持不变
P.PORTFOLIO_UNITS AS PORTFOLIO_UNITS, --投资组合
T1.I_CODE AS SECURITY_ID, --证券代码,给流水号
T1.I_CODE AS SECURITY_NAME, --证券名称,给流水号
nvl(T20.TARGET_CODE,'OTHER') AS MARKET_NO, --市场代码
nvl(T20.TARGET_NAME,'其他') AS MARKET_NAME, --市场名称
oc.partyname AS COUNTER_PARTY, --交易对手名称
T1.partyid AS COUNTER_PARTY_ID, --交易对手组织机构代码
T2.AMOUNT AS HOLDING_UNITS, --持仓数量PAR_VALUE
T2.AMOUNT AS BOOK_BALANCE_N, --财务账面余额_本币AMOUNT
T2.AMOUNT AS BOOK_BALANCE_B, --财务账面余额_本币AMOUNT
T2.AMOUNT AS FINANCIAL_COST_ACCOUNT_N, --参考财务成本_原币AMOUNT
T2.AMOUNT AS FINANCIAL_COST_ACCOUNT_B, --参考财务成本_本币AMOUNT
round(ABS((T2.AIAMOUNT / T2.TERM * ((datediff(TO_DATE('2017-06-30'),TO_DATE(T2.FSTSETDATE)))+1)) ), 2) ACCRUE_INTEREST_N, --应计利息_原币
round(ABS((T2.AIAMOUNT / T2.TERM * ((datediff(TO_DATE('2017-06-30'),TO_DATE(T2.FSTSETDATE)))+1)) ), 2) ACCRUE_INTEREST_B --应计利息_本币
FROM bridge.FBMS_A_TTRD_OTC_TRADE_IB T1
INNER JOIN bridge.FBMS_A_TTRD_OTC_IBLB_IB T2 ON T2.I_CODE = T1.INTORDID
AND T2.M_TYPE = T1.M_TYPE
AND T2.A_TYPE = T1.A_TYPE
AND T2.ENDSETDATE > TO_DATE('2017-06-30') --投资组合映射主表
left join (select v1.accountid, v2.murex_leaf, v2.Third_Business_Line as business_line, v2.portfolio_units, v2.fund_source, v2.account_class
from bridge.BRIDGE_APP_PORTFOLIOACCOUNT_ib v1
inner join bridge.bridge_murex_leaf_config v2 on v1.portfolioid = v2.murex_leaf
and ascii(v2.is_send_group) = -26
and v1.biz_date = v2.biz_date
where '20170630' = v2.biz_date) p on p.accountid = t1.secu_accid
--业务线
left join (select col_name, tabname_cn as chinese_name, tabno as mapping_key from bridge.bridge_murex_leaf_mapping_ib where col_name = 'BUSINESS_LINE' and '20170630' = biz_date) p1 on p.business_line = p1.chinese_name
--资金来源
left join (select col_name, tabname_cn as chinese_name, tabno as mapping_key from bridge.bridge_murex_leaf_mapping_ib where col_name = 'FUND_SOURCE' and '20170630' = biz_date) p2 on p.fund_source = p2.chinese_name
--会计分类
left join (select col_name, tabname_cn as chinese_name, tabno as mapping_key from bridge.bridge_murex_leaf_mapping_ib where col_name = 'ACCOUNT_CLASS' and '20170630' = biz_date) p3 on p.account_class = p3.chinese_name
--交易对手(交易对手SUMMIT使用的是衡泰的数据源，衡泰是从交易中心获取的，可以通用)
left join (select max(partyname) as partyname, partyid from bridge.FBMS_A_TTRD_OTC_COUNTERPARTY_IB where '20170630' = biz_date group by partyid) oc on t1.partyid = oc.partyid

17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge sending #311
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge got value #311
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: delete took 1ms
17/11/18 16:55:51 [IPC Parameter Sending Thread #0]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge sending #312
17/11/18 16:55:51 [IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge]: DEBUG ipc.Client: IPC Client (1990421361) connection to cnsz131375/10.25.167.173:8020 from bridge got value #312
17/11/18 16:55:51 [main]: DEBUG ipc.ProtobufRpcEngine: Call: delete took 1ms
17/11/18 16:55:51 [main]: INFO log.PerfLogger:
17/11/18 16:55:51 [main]: INFO log.PerfLogger:
hive> 17/11/18 16:56:11 [LeaseRenewer:bridge@mycluster]: DEBUG hdfs.LeaseRenewer: Lease renewer daemon for [] with renew id 1 executed
17/11/18 16:56:13 [LeaseRenewer:bridge@mycluster]: DEBUG hdfs.LeaseRenewer: Lease renewer daemon for [] with renew id 1 expired
17/11/18 16:56:13 [LeaseRenewer:bridge@mycluster]: DEBUG hdfs.LeaseRenewer: Lease renewer daemon for [] with renew id 1 exited

转载于:https://www.cnblogs.com/qiuhong10/p/7842996.html

你可能感兴趣的:(hive bug)

nosql数据库技术与应用知识点皆过客，揽星河 NoSQL nosql 数据库大数据数据分析数据结构非关系型数据库
Nosql知识回顾大数据处理流程数据采集(flume、爬虫、传感器)数据存储(本门课程NoSQL所处的阶段)Hdfs、MongoDB、HBase等数据清洗(入仓)Hive等数据处理、分析(Spark、Flink等)数据可视化数据挖掘、机器学习应用(Python、SparkMLlib等)大数据时代存储的挑战(三高)高并发(同一时间很多人访问)高扩展(要求随时根据需求扩展存储)高效率(要求读写速度快)
ARM V8 base instruction -- Debug instructions xiaozhiwise Assembly arm
/**Debuginstructions*/BRK#imm16进入monitormodedebug，那里有on-chipdebugmonitorcodeHLT#imm16进入haltmodedebug，连接有外部调试硬件
ARMv8 Debug __pop_ ARMv8 ARM64 架构 linux 运维
内容来自DEN0024A_v8_architecture_PG.pdf本质ARMv8Debug是什么历史在ARMv4开始被引入,并已发展成一系列广泛的调试(debug1)和跟踪(trace)功能ARMv6和ARMv7-a新增了自托管调试(debug2)和性能评测(trace-enhance)ARMv8处理器提供硬件功能侵入式:调试工具能够对核心活动提供显著级别的控制非侵入式:以非侵入性方式收集有关
【ARM Cortex-M 系列 2.3 -- Cortex-M7 Debug event 详细介绍】主公讲 ARM #ARM 系列 arm开发 debug event
请阅读【嵌入式开发学习必备专栏】文章目录Cortex-M7DebugeventDebugeventsCortex-M7Debugevent在ARMCortex-M7架构中，调试事件（DebugEvent）是由于调试原因而触发的事件。一个调试事件会导致以下几种情况之一发生：进入调试状态：如果启用了停滞调试（HaltingDebug），一个调试事件会使处理器在调试状态下停滞。通过将DHCSR.C_DE
JavaScript 中，深拷贝（Deep Copy）和浅拷贝（Shallow Copy）跳房子的前端前端面试 javascript 开发语言 ecmascript
在JavaScript中，深拷贝（DeepCopy）和浅拷贝（ShallowCopy）是用于复制对象或数组的两种不同方法。了解它们的区别和应用场景对于避免潜在的bugs和高效地处理数据非常重要。以下是对深拷贝和浅拷贝的详细解释，包括它们的概念、用途、优缺点以及实现方式。1.浅拷贝（ShallowCopy）概念定义：浅拷贝是指创建一个新的对象或数组，其中包含了原对象或数组的基本数据类型的值和对引用数
【Bugs】Python：“ModuleNotFoundError: No module named ‘XXX‘” 系'辞工具箱 python bug anaconda
问题描述Python使用库的前提是必须已安装了相应的库，往往利用“命令行指令”实现安装，一般安装解法类似。但，还是具有延伸问题，本博客对此作记录。【1】Nomodulenamed‘seaborn’(1.1):情况1：为Anaconda安装【图1-2】.定位Anaconda路径【图3】.Anaconda路径加入Path>&
ARMV8体系结构简介：概述简单同学 ARMV8体系结构 ARMV8
1.前言本文主要概括的介绍ARMV8体系结构定义了哪些内容，概括的说：ARM体系结构定义了PE的行为，不会定义具体的实现ARM体系结构也定义了debug体系结构和trace体系结构ARM体系结构采用RISC指令集（1）长度一致的寄存器；（2）load/store架构，数据处理操作只能对寄存器内容进行处理，不会直接对内存的内容进行处理；（3）简单寻址方式，load/store地址来源于寄存器或指令域
浅谈MapReduce Android路上的人 Hadoop 分布式计算 mapreduce 分布式框架 hadoop
从今天开始，本人将会开始对另一项技术的学习，就是当下炙手可热的Hadoop分布式就算技术。目前国内外的诸多公司因为业务发展的需要，都纷纷用了此平台。国内的比如BAT啦，国外的在这方面走的更加的前面，就不一一列举了。但是Hadoop作为Apache的一个开源项目，在下面有非常多的子项目，比如HDFS，HBase,Hive，Pig,等等，要先彻底学习整个Hadoop，仅仅凭借一个的力量，是远远不够的。
C语言---程序设计练习题目及学习方法1 Wanyu677 C语言 c语言学习方法算法
学习方法要多练习在这些题目中的代码和题目自己动手去敲练习也是在熟悉语法，写代码第一步就是熟悉语法练习是在锻炼编程思维，把实际问题转换为代码的能力学会画图画图去理解内存，理解指针这些比较难懂的知识画图可以更好的理清思路辅助理解，强化理解学会调试借助调试，更好的理解代码和感知代码找出代码中的bug和程序逻辑（1）自增自减运算符inta=5,b,c,i=10;b=a++;c=++b;printf("a=
史上最全git命令,git回滚,git命令大全騒周其他 git
git命令大全一、Git整体理解二、由暂存区本地仓库三、由本地仓->远程仓库四、冲突处理五、Git分支操作六、bug的分支七、feature分支八、暂存的使用九、远程仓的操作十、标签的使用十一、Git配置全局信息十二、Linux的一些简单操作和一些符号的解释十三、符号解释十四、显示安装详细信息十五、gitconfig十六、Gitclone十七、Gitinit十八、gitstatus十九、gitre
Android shell 常用 debug 命令晨春计 Audio debug android linux
目录1、查看版本2、am命令3、pm命令4、dumpsys命令5、sed命令6、log定位查看APK进程号7、log定位使用场景1、查看版本1.1、Android串口终端执行getpropro.build.version.release#获取Android版本uname-a#查看linux内核版本信息uname-r#单独查看内核版本1.2、linux服务器执行lsb_release-a#查看Lin
CTF-bugku-crypto-[7+1+0]-base64解码之后做偏移沧海一粟日尽其用算法安全 python
CTF-bugku-crypto-[7+1+0]-base64解码之后做偏移1.题目2.解题思路2.1base64编码原理2.2解题思路2.2.1base64解码找规律2.2.2破解思路3.解题脚本4.flag5.附EASCII码表1.题目提示信息：7+1+0？格式bugku{xxxxx}密文：4nXna/V7t2LpdLI44mn0fQ==要求：破解密文获得flag2.解题思路2.1base64
odoo 开源版/企业版/社区版的对比分析 lijianhua_9712 odoo odoo
odoo的三个版本1开源版开发者odoo限制功能版本优点功能稳定，bug少缺点限制功能，进销存勉强可用2企业版开发者odoo中型企业功能优点功能稳定，bug少缺点授权费用昂贵3社区版开发者社区(1700余名专家）大型企业功能优点功能丰富，社区不受odoo公司控制，社区开发者基本都是资深erp技术专家，增加了大量细致功能缺点存在一些bug为什么用odoo社区版，不用odoo企业版呢1odoo企业版是
Presto【基础 01】简介+架构+数据源+数据模型 2401_84254343 程序员架构
一个Catalog包含Schema和Connector。例如，配置JMX的Catalog，通过JXMConnector访问JXM信息。当执行一条SQL语句时，可以同时运行在多个Catalog。Presto处理table时，是通过表的完全限定（fully-qualified）名来找到Catalog。例如，一个表的权限定名是hive.test_data.test，则test是表名，test_data是
python+adb 0o一人情 adb命令 Python项目 python 开发语言
#!/usr/bin/pythonenv#-*-coding:utf-8-*-importosimportsysimportsubprocessfromtimeimportsleepimportlogginglogging.basicConfig(level=logging.DEBUG)classScreenCapture():defget_screen_size(self):"""获取手机分辨率
大数据毕业设计hadoop+spark+hive知识图谱租房数据分析可视化大屏租房推荐系统 58同城租房爬虫房源推荐系统房价预测系统计算机毕业设计机器学习深度学习人工智能 2401_84572577 程序员大数据 hadoop 人工智能
做了那么多年开发，自学了很多门编程语言，我很明白学习资源对于学一门新语言的重要性，这些年也收藏了不少的Python干货，对我来说这些东西确实已经用不到了，但对于准备自学Python的人来说，或许它就是一个宝藏，可以给你省去很多的时间和精力。别在网上瞎学了，我最近也做了一些资源的更新，只要你是我的粉丝，这期福利你都可拿走。我先来介绍一下这些东西怎么用，文末抱走。（1）Python所有方向的学习路线（
麻雀虽小，五脏俱全 - Java工具类库 - Hutool waiter_chen
Hutool官网：https://www.hutool.cn官方参考文档：https://www.hutool.cn/docsAsetoftoolsthatkeepJavasweet.——Htool特点通过静态方法封装，类函数式语言般，降低学习成本，提高工作效率整合多方用户需求，减少代码搜索成本，避免网络上参差不齐的代码出现导致的bugutil包提供多方公用类和公用工具方法，节省开发封装时间，减少
【十八】【QT开发应用】标签页QTabWidget的常见用法妖精七七_ QT开发应用 qt 开发语言
#include"widget.h"//包含自定义的widget头文件#include//包含QHBoxLayout头文件，用于水平布局#include//包含QTabWidget头文件，用于创建标签页控件#include//包含QDebug头文件，用于调试输出widget::widget(QWidget*parent)//widget类的构造函数:QWidget(parent)//调用基类QWi
JavaScript 基础 - 第15天 +码农快讯+ JavaScript学习笔记 javascript 前端开发语言
文章目录JavaScript基础-第15天深浅拷贝浅拷贝深拷贝通过JSON序列化实现js库lodash实现深拷贝通过递归实现深拷贝异常处理throwtry...catchdebugger处理this改变thiscallapplybindthis指向性能优化防抖（debounce）手写防抖函数节流（throttle）手写节流函数JavaScript基础-第15天深浅拷贝浅拷贝浅拷贝：把对象拷贝给一个
ansible安全优化篇 happy_king_zi 运维自动化配置管理安全 ansible 安全 devops
一、安全概况对与一台全新安装的服务器，尤其是直接面向公网的服务器来说：最重要的一项配置就是安全配置。针对非授权连接和截取通信信息等攻击行为，避免攻击手段带来的危害，处理方法有以下方法：使用安全加密的通信方式——使用https加密传输；禁止root用户远程登录并充分利用sudo；移除非必需的软件，只开发需要用到的端口；遵守权限最小化原则；及时更新操作系统和软件——修复旧版本的bug，并使用新版本的最
2020-11-12 写单片机内存的脚本 nc openocd 事务自动测试 linuxScripter
这是写单片机内存的脚本：z@z-ThinkPad-T400:~/zworkT400/EDA_heiche/zREPOgit/simple-gcc-stm32-project$catz.wholeRun.oneCase.cmdcattmp6.toWrite|awk'{system("echomwb"$1""$2"|nclocalhost4444");}'catUSER/DEBUG/debug.h|g
【ADB】adb、shell的介绍 "啦啦啦" adb shell adb shell
目录adb命令和shell命令的关系adb命令shell命令shell脚本shell脚本运行的环境是什么.sh脚本和.bat脚本有什么区别这两个脚本使用的命令和语法是一样的吗adb命令和shell命令的关系ADB（AndroidDebugBridge）命令和Shell命令都是用于与操作系统交互的命令行工具，但它们的使用环境和目标设备不同。ADB是一种调试工具，主要用于从计算机连接和操作Androi
简化安卓操作：利用ADB命令返回主页、首页等操作开心呆哥 android adb
介绍：在日常使用安卓设备时，经常需要返回到主页或者首页。虽然通过手动点击设备上的按钮可以轻松实现，但对于一些需要频繁进行此操作的场景，这种方式可能显得有些繁琐。幸运的是，利用ADB（AndroidDebugBridge）命令，我们可以在不触摸设备的情况下轻松地返回到主页、首页等操作，从而提高操作效率。本文将介绍如何利用ADB命令来实现这些操作，让您的安卓设备操作更加便捷。正文：1.返回主页：要通过
使用 ADB 命令在 Android 设备上进行截屏开心呆哥 adb android
在Android开发和调试过程中，截取设备屏幕是一项非常有用的功能。ADB（AndroidDebugBridge）是一个强大的工具，可以帮助我们与Android设备进行通信和调试。本文将介绍如何使用ADB命令在Android设备上进行截屏。1.准备工作在开始之前，确保你已经完成以下准备工作：在计算机上安装好AndroidSDK，并且配置好了ADB。连接你的Android设备到计算机，并确保ADB能
【Qt】之【Bug】LNK2019: 无法解析的外部符号 __imp_FindWindowW Htht111 Qt bug qt bug 开发语言
QTerror:LNK2019:无法解析的外部符号__imp__SendMessageW@类型的错误以及pragmacomment的作用（用法）添加头文件出错的cpp文件加入以下代码#pragmacomment(lib,"User32.lib")ps：尝试pro添加-lUser32，没用
python-logging库冰美式QAQ python学习
1.logging模块简介logging模块是Python内置的标准模块，主要用于输出运行日志，可以设置输出日志的等级、日志保存路径、日志输出格式等2.logging库日志级别级别级别数值使用时机DEBUG10详细信息，常用于调试INFO20程序正常运行过程中产生的一些信息WARNING30警告用户，虽然程序还在正常工作，但有可能发生错误ERROR40由于更严重的问题，程序已不能执行一些功能了CR
2019-08-01 Sophia_Lu
JavaScript调试使用debugger进行打断点JavaScript严格模式(usestrict)它不是一条语句，但是是一个字面量表达式，在JavaScript旧版本中会被忽略。"usestrict"的目的是指定代码在严格条件下执行。严格模式下你不能使用未声明的变量。
Dev-C++头文件小Bug 蒟蒻pzjdsg666 bug c语言 c++
Dev-C++应该是大家最常用的C++软件了吧，但它有几个小Bug。1、“万能头”众所周知，“万能头”在官方比赛中不能使用（你要用没人拦着你~呵呵），但在Dev-C++可以使用。所以，我们可以省掉好多头文件！如下：#includeusingnamespacestd;2、C语言头文件在Dev-C++中，你竟然可以使用C语言头文件（惊不惊喜~意不意外~）如下：#include3、iostream竟然包
大数据之flink与hive 星辰_mya 大数据 flink hive
其实吧我不太想写flink，因为线上经验确实不多，这也是我需要补的地方，没有条件创造条件，先来一篇吧flink：高性能低延迟流批一体的分布式计算框架基于事件时间对实时数据精准处理快速响应支持批处理，高效离线分析和数据挖掘数据仓库的引擎丰富数据源/接收器，集成多种数据存储格式和源，比较常见就是咱们今天的主题hive了checkpoint恢复机制，故障恢复快速恢复计算任务分布式弹性扩展，据业务灵活增加
hive血缘关系之输入表与目标表的解析 zxfBdd hive 大数据治理大数据
接了一个新需求：需要做数据仓库的血缘关系。正所谓兵来将挡水来土掩，那咱就动手吧。血缘关系是数据治理的一块，其实有专门的第三方数据治理框架，但考虑到目前的线上环境已经趋于稳定，引入新的框架无疑是劳民伤财，伤筋动骨，所以就想以最小的代价把这个事情给做了。目前我们考虑做的血缘关系呢只是做输入表和输出表，最后会形成一张表与表之间的链路图。这个东西的好处就是有助于仓库人员梳理业务，后面可能还会做字段之间的血
SAX解析xml文件小猪猪08 xml
1.创建SAXParserFactory实例 2.通过SAXParserFactory对象获取SAXParser实例 3.创建一个类SAXParserHander继续DefaultHandler，并且实例化这个类 4.SAXParser实例的parse来获取文件 public static void main(String[] args) { //
为什么mysql里的ibdata1文件不断的增长？ brotherlamp linux linux运维 linux资料 linux视频 linux运维自学
我们在 Percona 支持栏目经常收到关于 MySQL 的 ibdata1 文件的这个问题。当监控服务器发送一个关于 MySQL 服务器存储的报警时，恐慌就开始了 —— 就是说磁盘快要满了。一番调查后你意识到大多数地盘空间被 InnoDB 的共享表空间 ibdata1 使用。而你已经启用了 innodbfileper_table，所以问题是： ibdata1存了什么？当你启用了 i
Quartz-quartz.properties配置 eksliang quartz
其实Quartz JAR文件的org.quartz包下就包含了一个quartz.properties属性配置文件并提供了默认设置。如果需要调整默认配置，可以在类路径下建立一个新的quartz.properties，它将自动被Quartz加载并覆盖默认的设置。下面是这些默认值的解释 #-----集群的配置 org.quartz.scheduler.instanceName =
informatica session的使用 18289753290 workflow session log Informatica
如果希望workflow存储最近20次的log，在session里的Config Object设置，log options做配置，save session log :sessions run ;savesessio log for these runs:20 session下面的source 里面有个tracing
Scrapy抓取网页时出现CRC check failed 0x471e6e9a != 0x7c07b839L的错误酷的飞上天空 scrapy
Scrapy版本0.14.4 出现问题现象： ERROR: Error downloading <GET http://xxxxx CRC check failed 解决方法 1.设置网络请求时的header中的属性'Accept-Encoding': '*;q=0' 明确表示不支持任何形式的压缩格式，避免程序的解压
java Swing小集锦永夜-极光 java swing
1.关闭窗体弹出确认对话框 1.1 this.setDefaultCloseOperation (JFrame.DO_NOTHING_ON_CLOSE); 1.2 this.addWindowListener ( new WindowAdapter () { public void windo
强制删除.svn文件夹随便小屋 java
在windows上，从别处复制的项目中可能带有.svn文件夹，手动删除太麻烦，并且每个文件夹下都有。所以写了个程序进行删除。因为.svn文件夹在windows上是只读的，所以用File中的delete()和deleteOnExist()方法都不能将其删除，所以只能采用windows命令方式进行删除
GET和POST有什么区别？及为什么网上的多数答案都是错的。 aijuans get post
如果有人问你，GET和POST，有什么区别？你会如何回答？我的经历前几天有人问我这个问题。我说GET是用于获取数据的，POST，一般用于将数据发给服务器之用。这个答案好像并不是他想要的。于是他继续追问有没有别的区别？我说这就是个名字而已，如果服务器支持，他完全可以把G
谈谈新浪微博背后的那些算法 aoyouzi 谈谈新浪微博背后的那些算法
本文对微博中常见的问题的对应算法进行了简单的介绍，在实际应用中的算法比介绍的要复杂的多。当然，本文覆盖的主题并不全，比如好友推荐、热点跟踪等就没有涉及到。但古人云“窥一斑而见全豹”，希望本文的介绍能帮助大家更好的理解微博这样的社交网络应用。微博是一个很多人都在用的社交应用。天天刷微博的人每天都会进行着这样几个操作：原创、转发、回复、阅读、关注、@等。其中，前四个是针对短博文，最后的关注和@则针
Connection reset 连接被重置的解决方法百合不是茶 java 字符流连接被重置
流是java的核心部分,,昨天在做android服务器连接服务器的时候出了问题,就将代码放到java中执行,结果还是一样连接被重置被重置的代码如下; 客户端代码; package 通信软件服务器; import java.io.BufferedWriter; import java.io.OutputStream; import java.io.O
web.xml配置详解之filter bijian1013 java web.xml filter
一.定义 <filter> <filter-name>encodingfilter</filter-name> <filter-class>com.my.app.EncodingFilter</filter-class> <init-param> <param-name>encoding<
Heritrix Bill_chen 多线程 xml 算法制造配置管理
作为纯Java语言开发的、功能强大的网络爬虫Heritrix，其功能极其强大，且扩展性良好，深受热爱搜索技术的盆友们的喜爱，但它配置较为复杂，且源码不好理解，最近又使劲看了下，结合自己的学习和理解，跟大家分享Heritrix的点点滴滴。 Heritrix的下载（http://sourceforge.net/projects/archive-crawler/）安装、配置，就不罗嗦了，可以自己找找资
【Zookeeper】FAQ bit1129 zookeeper
1.脱离IDE，运行简单的Java客户端程序 #ZkClient是简单的Zookeeper~$ java -cp "./:zookeeper-3.4.6.jar:./lib/*" ZKClient 1. Zookeeper是的Watcher回调是同步操作，需要添加异步处理的代码 2. 如果Zookeeper集群跨越多个机房，那么Leader/
The user specified as a definer ('aaa'@'localhost') does not exist 白糖_ localhost
今天遇到一个客户BUG，当前的jdbc连接用户是root，然后部分删除操作都会报下面这个错误：The user specified as a definer ('aaa'@'localhost') does not exist 最后找原因发现删除操作做了触发器，而触发器里面有这样一句 /*!50017 DEFINER = ''aaa@'localhost' */ 原来最初
javascript中showModelDialog刷新父页面 bozch JavaScript 刷新父页面 showModalDialog
在页面中使用showModalDialog打开模式子页面窗口的时候，如果想在子页面中操作父页面中的某个节点，可以通过如下的进行： window.showModalDialog('url',self,‘status...’); // 首先中间参数使用self 在子页面使用w
编程之美-买书折扣 bylijinnan 编程之美
import java.util.Arrays; public class BookDiscount { /**编程之美买书折扣书上的贪心算法的分析很有意思，我看了半天看不懂，结果作者说，贪心算法在这个问题上是不适用的。。下面用动态规划实现。哈利波特这本书一共有五卷，每卷都是8欧元，如果读者一次购买不同的两卷可扣除5%的折扣，三卷10%，四卷20%，五卷
关于struts2.3.4项目跨站执行脚本以及远程执行漏洞修复概要 chenbowen00 struts WEB安全
因为近期负责的几个银行系统软件，需要交付客户，因此客户专门请了安全公司对系统进行了安全评测，结果发现了诸如跨站执行脚本，远程执行漏洞以及弱口令等问题。下面记录下本次解决的过程以便后续 1、首先从最简单的开始处理，服务器的弱口令问题，首先根据安全工具提供的测试描述中发现应用服务器中存在一个匿名用户，默认是不需要密码的，经过分析发现服务器使用了FTP协议，而使用ftp协议默认会产生一个匿名用
[电力与暖气]煤炭燃烧与电力加温 comsci
在宇宙中,用贝塔射线观测地球某个部分,看上去,好像一个个马蜂窝,又像珊瑚礁一样,原来是某个国家的采煤区..... 不过,这个采煤区的煤炭看来是要用完了.....那么依赖将起燃烧并取暖的城市,在极度严寒的季节中...该怎么办呢? &nbs
oracle O7_DICTIONARY_ACCESSIBILITY参数 daizj oracle
O7_DICTIONARY_ACCESSIBILITY参数控制对数据字典的访问.设置为true,如果用户被授予了如select any table等any table权限,用户即使不是dba或sysdba用户也可以访问数据字典.在9i及以上版本默认为false,8i及以前版本默认为true.如果设置为true就可能会带来安全上的一些问题.这也就为什么O7_DICTIONARY_ACCESSIBIL
比较全面的MySQL优化参考 dengkane mysql
本文整理了一些MySQL的通用优化方法，做个简单的总结分享，旨在帮助那些没有专职MySQL DBA的企业做好基本的优化工作，至于具体的SQL优化，大部分通过加适当的索引即可达到效果，更复杂的就需要具体分析了，可以参考本站的一些优化案例或者联系我，下方有我的联系方式。这是上篇。 1、硬件层相关优化 1.1、CPU相关在服务器的BIOS设置中，可
C语言homework2，有一个逆序打印数字的小算法 dcj3sjt126com c
#h1# 0、完成课堂例子 1、将一个四位数逆序打印 1234 ==> 4321 实现方法一： # include <stdio.h> int main(void) { int i = 1234; int one = i%10; int two = i / 10 % 10; int three = i / 100 % 10;
apacheBench对网站进行压力测试 dcj3sjt126com apachebench
ab 的全称是 ApacheBench ，是 Apache 附带的一个小工具，专门用于 HTTP Server 的 benchmark testing ，可以同时模拟多个并发请求。前段时间看到公司的开发人员也在用它作一些测试，看起来也不错，很简单，也很容易使用，所以今天花一点时间看了一下。通过下面的一个简单的例子和注释，相信大家可以更容易理解这个工具的使用。
2种办法让HashMap线程安全 flyfoxs java jdk jni
多线程之--2种办法让HashMap线程安全多线程之--synchronized 和reentrantlock的优缺点多线程之--2种JAVA乐观锁的比较( NonfairSync VS. FairSync) HashMap不是线程安全的,往往在写程序时需要通过一些方法来回避.其实JDK原生的提供了2种方法让HashMap支持线程安全.
Spring Security（04）——认证简介 234390216 Spring Security 认证过程
认证简介目录 1.1 认证过程 1.2 Web应用的认证过程 1.2.1 ExceptionTranslationFilter 1.2.2 在request之间共享SecurityContext 1
Java 位运算 Javahuhui java 位运算
// 左移( << ) 低位补0 // 0000 0000 0000 0000 0000 0000 0000 0110 然后左移2位后，低位补0： // 0000 0000 0000 0000 0000 0000 0001 1000 System.out.println(6 << 2);// 运行结果是24 // 右移( >> ) 高位补"
mysql免安装版配置 ldzyz007 mysql
1、my-small.ini是为了小型数据库而设计的。不应该把这个模型用于含有一些常用项目的数据库。 2、my-medium.ini是为中等规模的数据库而设计的。如果你正在企业中使用RHEL,可能会比这个操作系统的最小RAM需求(256MB)明显多得多的物理内存。由此可见，如果有那么多RAM内存可以使用，自然可以在同一台机器上运行其它服务。 3、my-large.ini是为专用于一个SQL数据
MFC和ado数据库使用时遇到的问题你不认识的休道人 sql C++mfc
=================================================================== 第一个 =================================================================== try{ CString sql; sql.Format("select * from p
表单重复提交Double Submits rensanning double
可能发生的场景： *多次点击提交按钮 *刷新页面 *点击浏览器回退按钮 *直接访问收藏夹中的地址 *重复发送HTTP请求（Ajax）（1）点击按钮后disable该按钮一会儿，这样能避免急躁的用户频繁点击按钮。这种方法确实有些粗暴，友好一点的可以把按钮的文字变一下做个提示，比如Bootstrap的做法： http://getbootstrap.co
Java String 十大常见问题 tomcat_oracle java 正则表达式
　1.字符串比较，使用“==”还是equals()? 　　"=="判断两个引用的是不是同一个内存地址(同一个物理对象)。　　equals()判断两个字符串的值是否相等。　　除非你想判断两个string引用是否同一个对象，否则应该总是使用equals()方法。　　如果你了解字符串的驻留(String Interning)则会更好地理解这个问题。　　
SpringMVC 登陆拦截器实现登陆控制 xp9802 springMVC
思路，先登陆后，将登陆信息存储在session中，然后通过拦截器，对系统中的页面和资源进行访问拦截，同时对于登陆本身相关的页面和资源不拦截。实现方法： 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23