|
Size: 3368
Comment:
|
Size: 2836
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Procedure TmIngestion during ILT== | == Pacs Database Setup during ILT == attachment:PacsDataDis.jpg attachment:dbsetup4.jpg * email from Tilmann : This is were replication would come in. Replication can be used to re-route data to a second database-node while maintaining links to and from the first database node (all in the same database system, and therefore transparent to all applications). Please remember that there are currently some issues with mixing replication/propagation. This is described in the DBA-Manual under current restrictions (Issue 0.18, chapter 8.4, section 2, bullet 2 and 3). When is ILT testing planned to start? By when would you require the issues to be resolved? In case ILT produces < 250GB data, I recommend to use a single database node. == Procedure TmIngestion during ILT == |
| Line 22: | Line 38: |
| > tmingestion < /dev/null >& /dev/null & | > tmingestion < /dev/null >& /dev/null & |
| Line 32: | Line 48: |
| =========== | ============== #hcss.test.database = accesslayer2${var.database.server} |
| Line 34: | Line 52: |
| var.database.server = @pacs1 | var.database.server = @pacs1.mpe-garching.mpg.de # The name of the database. #var.database.devel = pacspreilt var.database.devel = pacspreilt@pacs1 |
| Line 36: | Line 58: |
| # The name of the database. var.database.devel = pacsilt1@pacs1 |
# The directory where the raw mib is located. #var.mib.raw = ${var.mib.data}/4.4 hcss.access.instrumentmodel =PACS #Replication hcss.store.factory = herschel.versant.store.ReplStoreFactoryImpl #hcss.store.factory = herschel.versant.store.StoreFactoryImpl hcss.ccm.mission.config = democonfig |
| Line 39: | Line 67: |
| # Mission configuration #hcss.ccm.mission.config = CQMconfig hcss.ccm.mission.config = democonfig # The location of the MIB #var.mib.raw = ${user.home}/data/mib/pacs/merged/MIB-AUX-DATA # -------------- TM Ingestion # Replication #hcss.store.factory = herschel.versant.store.ReplStoreFactoryImpl # Database name hcss.tmingest.database = ${var.database.devel} # Router server hcss.tmingest.server = hos4-d # Router port hcss.tmingest.port = 9877 # Router reconnect hcss.tmingest.routerretry = 60000 # Router client name hcss.tmingest.name = PacsTelemetryIngestion # HIFI packet processor hcss.tmingest.tmpacketprocessor.hifi = N hcss.tmingest.tmpacketprocessor.hifi.name = herschel.tmproc.fifo.HifiTmPacketProcessor # PACS packet processor hcss.tmingest.tmpacketprocessor.pacs = N hcss.tmingest.tmpacketprocessor.pacs.name = herschel.tmproc.fifo.PacsTmPacketProcessor # SPIRE packet processor hcss.tmingest.tmpacketprocessor.spire = N hcss.tmingest.tmpacketprocessor.spire.name = herschel.tmproc.fifo.SpireTmPacketProcessor #Store commit hcss.tmingest.transactions = 200 # Store timer - commit in milliseconds every 2 min hcss.tmingest.timerduration = 120000 # -------------- TM Ingestion (Inst Apids) hcss.tmingest.apid1024 = N hcss.tmingest.apid1026 = Y hcss.tmingest.apid1028 = N hcss.tmingest.apid1030 = N hcss.tmingest.apid1153 = Y hcss.tmingest.apid1155 = Y |
# TM Ingestion hcss.tmingest.tmpacketprocessor.pacs.name = herschel.pacs.spu.PacsTmPacketProcessor hcss.tmingest.fifo.threadsleepduration = 1 hcss.tmingest.server = irsun01 hcss.tmingest.transactions = 100 hcss.tmingest.tmpacketprocessor.pacs = Y hcss.tmingest.port = 9877 hcss.tmingest.name = TelemetryIngestion hcss.tmingest.retry = 600 hcss.tmingest.fifo.queueinitialsize = 2000 hcss.tmingest.apid1156 = Y |
| Line 78: | Line 79: |
| hcss.tmingest.apid1159 = Y hcss.tmingest.apid1284 = N hcss.tmingest.apid1286 = N # TM Ingestion (S/C Apids) # TM Ingestion (EGSE Apids) # DBASE # pcss # Simulator # BoloSimulator # SpectrSimulator # Variables |
hcss.tmingest.apid1160 = Y hcss.tmingest.apid1161 = Y hcss.tmingest.apid1162 = Y hcss.tmingest.apid1163 = Y hcss.tmingest.apid1164 = Y |
| Line 90: | Line 85: |
| #Access hcss.access.router.host = irsun01 hcss.access.router.port = 9877 |
|
| Line 91: | Line 89: |
| #The tool uses the following properties to control the MissionConfiguration: hcss.ccm.mission.basic.models = { HIFI.FLIGHT, PACS.FLIGHT, SPIRE.FLIGHT} hcss.ccm.mission.basic.tp_registry = true # For # 12.09.05 end |
# For CUS hcss.cus.instrument = PACS hcss.cus.database = sftcode@pacs1.mpe-garching.mpg.de |
| Line 97: | Line 93: |
| var.mib.raw=${user.home}/mib # TcPacketDumper.router.hostname=hos4-d TcPacketDumper.router.portnumber=9877 TcPacketDumper.router.clientname=TcPacketDumper TmPacketDumper.router.hostname=hos4-d TmPacketDumper.router.portnumber=9877 TmPacketDumper.router.clientname=TmPacketDumper # hcss.cus.instrument=PACS # hcss.ccshandler.instrumentName=PACS |
|
| Line 110: | Line 94: |
== Indexing the Database == Make sure that you have enough space in the database left: {{{ dbtool -space -volume -all <dbname> }}} Free space should be at least 20%. {{{ java -Xmx512M herschel.access.db.CreateIndexes <dbname> }}} Alternatively, using the versant commands: {{{ dbtool -index -create -btree herschel.versant.ccm.TmSourcePacketImpl _time <dbname> }}} |
Pacs Database Setup during ILT
attachment:PacsDataDis.jpg attachment:dbsetup4.jpg
- email from Tilmann :
- This is were replication would come in. Replication can be used to re-route data to a second database-node while maintaining links to and from the first database node (all in the same database system, and therefore transparent to all applications). Please remember that there are currently some issues with mixing replication/propagation. This is described in the DBA-Manual under current restrictions (Issue 0.18, chapter 8.4, section 2, bullet 2 and 3). When is ILT testing planned to start? By when would you require the issues to be resolved?
In case ILT produces < 250GB data, I recommend to use a single database node.
- This is were replication would come in. Replication can be used to re-route data to a second database-node while maintaining links to and from the first database node (all in the same database system, and therefore transparent to all applications). Please remember that there are currently some issues with mixing replication/propagation. This is described in the DBA-Manual under current restrictions (Issue 0.18, chapter 8.4, section 2, bullet 2 and 3). When is ILT testing planned to start? By when would you require the issues to be resolved?
Procedure TmIngestion during ILT
Log into TmIngestion computer
> ssh -X oper@pacs1
Check whether any TmIngestion is running
> ps -elf | grep tmingestion
- Check settings (APIDs/ Router/ Database) in property file :
> emacs .pcss/props > Example attached
start TmIngestion
> tmingestion or > tmingestion < /dev/null >& /dev/null &
- Check whether we get packets
> db2tty -d pacseqmimt1 | grep TmSource
.pcss/props
==============
#hcss.test.database = accesslayer2${var.database.server}
# The name of the computer where the versant server runs.
var.database.server = @pacs1.mpe-garching.mpg.de
# The name of the database.
#var.database.devel = pacspreilt
var.database.devel = pacspreilt@pacs1
# The directory where the raw mib is located.
#var.mib.raw = ${var.mib.data}/4.4
hcss.access.instrumentmodel =PACS
#Replication
hcss.store.factory = herschel.versant.store.ReplStoreFactoryImpl
#hcss.store.factory = herschel.versant.store.StoreFactoryImpl
hcss.ccm.mission.config = democonfig
# TM Ingestion
hcss.tmingest.tmpacketprocessor.pacs.name = herschel.pacs.spu.PacsTmPacketProcessor
hcss.tmingest.fifo.threadsleepduration = 1
hcss.tmingest.server = irsun01
hcss.tmingest.transactions = 100
hcss.tmingest.tmpacketprocessor.pacs = Y
hcss.tmingest.port = 9877
hcss.tmingest.name = TelemetryIngestion
hcss.tmingest.retry = 600
hcss.tmingest.fifo.queueinitialsize = 2000
hcss.tmingest.apid1156 = Y
hcss.tmingest.apid1157 = Y
hcss.tmingest.apid1160 = Y
hcss.tmingest.apid1161 = Y
hcss.tmingest.apid1162 = Y
hcss.tmingest.apid1163 = Y
hcss.tmingest.apid1164 = Y
#Access
hcss.access.router.host = irsun01
hcss.access.router.port = 9877
# For CUS
hcss.cus.instrument = PACS
hcss.cus.database = sftcode@pacs1.mpe-garching.mpg.de