Hi Debashis, Is sqlline started on the same machine? Perhaps sqlline ate all the available memory but the system decided to kill Ignite. Could you split incoming data into relatively small chunks and try it out?
вт, 30 окт. 2018 г. в 23:07, debashissinha <[email protected]>: > < > http://apache-ignite-users.70518.x6.nabble.com/file/t1918/20181031_005158.jpg> > > < > http://apache-ignite-users.70518.x6.nabble.com/file/t1918/20181031_005224.jpg> > > < > http://apache-ignite-users.70518.x6.nabble.com/file/t1918/20181031_004447.jpg> > > < > http://apache-ignite-users.70518.x6.nabble.com/file/t1918/20181031_004532.jpg> > > < > http://apache-ignite-users.70518.x6.nabble.com/file/t1918/20181031_004559.jpg> > > > Hi All, > I would request help from anyone who can assist me in a critical error. > I am trying to benchmark ignite on single node without tcp discovery > enabled > with tpcds benchmark data. > For this I am using customer table(image attached) and loading 5 gb of csv > file through sql line. > > The config( image attached) is for 20 gb of default data region with wal > mode none and eviction mode is only lru . I have also enabled native > persistence . Also in my ignite.sh script I am adding G1GC option in jvm > opts. > > After almost 1.63 gb of data getting inserted and which corresponds to > roughly 12000000 rows of data ignite is silently restarting giving an error > kill ignite.sh line 181 with jvm opts. The error for this is attached. > > I am having the following config > no of cpus 2 > heap memory 1 gb > data region max size(off heap size) 20 gb. > Cluster mode enabled. > > Can some one kindly advise me where I am going wrong. > > Thanks & Regards > Debashis Sinha > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Ivan Pavlukhin
