source: trunk/params/wave_serverV.d @ 6401

Revision 6401, 8.3 KB checked in by stefan, 4 years ago (diff)

updated 7.8 params

  • Property svn:eol-style set to native
  • Property svn:executable set to *
  • Property svn:keywords set to Author Date Id Revision
Line 
1#
2#         Wave ServerV Configuration File
3#
4#   Note:  All directories defined in this configuration file must already
5#       exit or WaveServerV will die.
6#
7MyModuleId    MOD_WAVESERVERV # wave_server's module id
8RingName      WAVE_RING        # name of transport ring to get data from
9LogFile       1                # 1=write log file to disk; 0=don't
10                               # 2=write to module log but not stderr/stdout
11HeartBeatInt  15               # seconds between heartbeats to statmgr
12ServerIPAdr   0.0.0.0          # IP address of machine running wave_server
13                               # 0.0.0.0 binds to all local available IPs
14ServerPort    16022            # port for receiving requests & sending waves
15GapThresh     1.5              # threshhold for gap declaration
16                               # (in sampling periods)
17
18#
19
20SocketTimeout 11000  # Timeout length in MILLISECONDS for socket calls
21                     # This is for calls sending responses back to the
22                     # client. Values should be a few seconds, certainly
23                     # less than one minute.
24
25
26ClientTimeout  60000 # Optional.  Not recommended feature but it does work.
27                     # Timeout in MILLISECONDS for response from client.
28                     # Threads that have not heard anything from their client
29                     # in this period will exit.
30                     # Comment out or set to -1 if you don't want to
31                     # kill threads of silent clients.
32
33
34# Each tank file has an associated in-memory index.  On re-start, the
35# index image on disk must be updated to match the tank.  The more out
36# of date the on-disk index is, the longer it takes to rebuild.  Rebuild
37# times can be from milliseconds to minutes per tank, depending how large
38# the tank is and how old the index is.
39# Set IndexUpdate to the length in time in seconds between
40# updates to disk.  The larger the update interval, the longer
41# a crash recovery will take.  The smaller the update interval
42# the more disk I/O that is required for wave_server to operate,
43# and thus the slower it will operate, once it has reached I/O
44# saturation.
45
46IndexUpdate   10               
47                   
48
49# Similar to an Index, each tank has TANK structure that depicts the tank.
50# The tank structure is maintained in memory, and periodically written to
51# disk.  The TANK structure tracks the status of the tank.  Any data written
52# to the tank since the last time the TANK structure was written to disk
53# is effectively lost.  TankStructUpdate is the interval in seconds that the
54# Tank Structure file on disk is updated.  The higher the interval, the more
55# the tank data is that is potentially lost in a crash, the lower the interval
56# the more the disk I/O that is required for wave_server to operate.
57
58TankStructUpdate 1
59
60# The file where TANK structures are stored
61
62TankStructFile  j:\data\usgs\datafiles\p1000-1.str
63
64# I open many files, one tracedata file for each SCNL channel to serve
65# At 500 bytes/second, 1 channel requires 41.2 megabytes per day.
66# NOTE: Record size must be multiple of 4 bytes or wave_serverV will crash
67# with data misalignment.
68# Also, record size must not be greater than MAX_TRACEBUF_SIZ, currently 4096,
69# (defined in tracebuf.h)
70#
71#           SCNL      Record       Logo                  File Size   Index Size       File Name     New       
72#          names       size  (TYPE_TRACEBUF2 only)         (megabytes) (max breaks)     (full path)      Tank     
73
74Tank    GUID --- NC -- 528   ${EW_INST_ID} MOD_WILDCARD       1         10000         j:\data\usgs\datafiles\p1001.tnk
75Tank    IRG1 T   NC -- 528   ${EW_INST_ID} MOD_WILDCARD       1         10000         j:\data\usgs\datafiles\p1002.tnk
76Tank    IRG2 T   NC -- 528   ${EW_INST_ID} MOD_WILDCARD       1         10000         j:\data\usgs\datafiles\p1003.tnk
77
78
79# Advanced Options
80# YES = 1, NO = 0, NO = (default)
81
82#RedundantTankStructFiles  Set to 1 to use redundant tank struct files. (Recommended)
83RedundantTankStructFiles 1
84
85#RedundantIndexFiles  Set to 1 to use redundant tank index files. (Recommended)
86RedundantIndexFiles      1
87
88
89# Must be set if RedundantTankStructFiles = 1
90#TankStructFile2  /tmp/p1000-2.str
91TankStructFile2  j:\data\usgs\datafiles\p1000-2.str
92
93
94#InputQueueLen:  The number of messages to buffer.  Messages are buffered
95#in a queue.  They are added to the queue when they are pulled off of an
96#earthworm message ring, they are removed from the queue when the main
97#thread is ready to process them.  Depending on the CPU and disk speed
98#of the machine you are using, this number should be about twice the
99#number of tanks you are trying to serve.  Slower machines may need
100#larger queues.
101InputQueueLen 4000
102
103
104###################################
105#           Other Optional Commands
106
107
108#MaxMsgSize: Optional command to tell wave_server about TRACEBUF2 messages
109# that could be larger than any going to tanks for this server. This
110# may happen if you have two wave_servers and TRACEBUF2 sources that
111# produce different size messages, e.g., ref2ew messages are 1064 bytes.
112MaxMsgSize 4096
113
114# Debug - optional value of the debug flag. Higher debug
115#    levels include all debug messages from the lower levels,
116#    plus more. WARNING: Debug files can get VERY VERY LARGE.
117#
118#   While the scope of each Debug level may vary, following
119#    values are accepted:
120#
121# Debug 1 ==>  Basic user level: will periodically log
122#    message queue watermarks and print the server thread status
123#    table.
124#
125# Debug 2 ==> Advanced user level: Everything from lower debug 
126#    levels plus additional information which could be used
127#    to troubleshoot installation problems.
128#
129# Debug 3 ==> Advanced programmer level: Everything from lower debug 
130#    levels plus additional information about the execution flow,
131#    and other low-level debugging information.
132#
133#
134#  NOTE: This command is optional. The absence of Debug means that
135#        only error conditions will be logged and reported.
136#
137#Debug 1
138
139#SocketDebug Set to 1 to get SOCKET_ew debug statements
140SocketDebug 0
141
142#PleaseContinue  Set to 1 to have wave_server continue, even if
143#  there are errors during initialization. That means if you do
144#  NOT set this value, then wave_serverV will stop running when
145#  a problem is found in a single tank. All the good remaining
146#  tanks therefore will be unavailable. (Default behavior.)
147#
148# PleaseContinue 1
149
150#ReCreateBadTanks Set to 1 to have bad tanks re-created from scratch.
151#ReCreateBadTanks 1
152
153#SecondsBetweenQueueErrorReports   Minimum period of time between error
154#  reports to statmgr due to the internal message queue being lapped,
155#  and thus messages being lost.  Default is 60 seconds
156#SecondsBetweenQueueErrorReports 30
157
158#MaxServerThreads  Maximum of server threads to deploy to handle client
159#  requests.  Default is 10.
160#MaxServerThreads 10
161
162#QueueReportInterval  The minimum number of seconds between
163#  reports on internal queue high and low water marks.  The default is 30.
164#QueueReportInterval 5
165
166#AbortOnSingleTankFailure  Set to 0 to have wave_server continue even
167#if there is a fatal error on a tank during normal processing.
168#if this flag is not set to 0, wave_server will die if any type of
169#IO error occurs on any tank.  If set to 1 wave_server will not exit
170#unless there is a server wide error.
171#AbortOnSingleTankFailure 1
172
173#TruncateTanksTo1GBAndContinue  Uncomment entry to have wave_server truncate
174# any tanks that are >1GB down to 1GB in size.  1GB is the maximum save tank
175# size in wave_serverV.  This will NOT affect EXISTING TANKS, only new ones
176# listed in the config file.
177#TruncateTanksTo1GBAndContinue
178
179# This section to deal with out-of-order data packets:
180
181#UsePacketSyncDb Uncomment entry and set to 1 to use embedded db functionality
182# to manage asychronous trace buffer packets. Currently this is either on or off
183# for all SNCLs.
184#UsePacketSyncDb 1
185
186#PacketSyncDbFile - Specifies name of database file to use. If not specified
187# and UsePacketSyncDb == 1 then the default PCKTSYNC.SL3DB is used.
188#PacketSyncDbFile "TB2PACKETS.SL3DB"
189
190#PurgePacketSyncD Uncomment and specify one of the following to control
191# how long out of sync data is kept in the database if UsePacketSyncDb=1.
192# 1 : Purge data on startup
193# 0 : Do not purge data on startup. Obsolete data is intermittently purged
194# during the operation of wave_serverV is UsePacketSyncDb is 1.
195#PurgePacketSyncDb 1
Note: See TracBrowser for help on using the repository browser.