https://sourceware.org/systemtap/examples/keyword-index.html#SIGNALS can help you track it down. On Wed, May 23, 2018 at 12:13 PM, Liuhao <liu.haoA@xxxxxxx> wrote: > Command: > ceph-objectstore-tool –debug --data-path /var/lib/ceph/osd/ceph-2/ --journal-path /var/lib/ceph/osd/ceph-2/journal --type filestore --pgid 3.ea --op export --file 3_ea.txt > > output: > Read #3:f729941a~582994ef:::benchmark_data_node1_3956424_object4920:head# > Read #3:f72d6086~6106b4ef:::benchmark_data_node1_361200_object7407:head# > Read #3:f732363b~dc6c4cef:::benchmark_data_node1_3956424_object1875:head# > Read #3:f73fa296~6945fcef:::benchmark_data_node1_3943756_object477:head# > Read #3:f743f062~460fc2ef:::benchmark_data_node1_3970155_object912:head# > Read #3:f74455ec~37aa22ef:::benchmark_data_node1_3956424_object963:head# > Terminated ←------- this is problem, why receive sigterm? > root@node1:~# > > solution: > add SIGTERM handler func, then the eport is ok. > > Output: > Read #3:976a1001~800856e9:::benchmark_data_node1_3970155_object1004:head# > Read #3:976a9397~e9c956e9:::benchmark_data_node1_361200_object8713:head# > Read #3:976aa572~4ea556e9:::benchmark_data_node1_361200_object5612:head# > recieve sigterm times: 1 ←--------receive sigterm > Read #3:976c5f76~6efa36e9:::benchmark_data_node1_361200_object9111:head# > Read #3:9778f9a8~159f1ee9:::benchmark_data_node1_3943756_object3512:head# > Read #3:977ae37a~5ec75ee9:::benchmark_data_node1_3970155_object1342:head# > Read #3:977c9fb8~1df93ee9:::benchmark_data_node1_361200_object11208:head# > Read #3:977cb944~229d3ee9:::benchmark_data_node1_361200_object9210:head# > Read #3:977f10f3~cf08fee9:::benchmark_data_node1_3956424_object3822:head# > Export successful > > Question: > why os originate SIGTERM signal? How to find the reason of SIGTERM? > > SIGTERM usually means the application takes up a lot of system resources. > But when use ceph-objectstore-tool, system resource occuqancy is not high by top. -- Cheers, Brad -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
