Support running multiple record engines as a pool

Downloads & Instructions
nickk
Silicondust
Posts: 15520
Joined: Tue Jan 13, 2004 9:39 am

Support running multiple record engines as a pool

Post by nickk » Thu May 16, 2019 5:41 pm

We have just released our support for running multiple record engines where they act together as a pool.

If you fill up your NAS now you can add another NAS :)

Beta download page:
viewtopic.php?f=126&t=20613

Recording on Windows: To upgrade the record engine service download and run the Windows installer from the beta download page.

Recording on Mac: To upgrade the record engine service download and run the Mac install from the beta download page.

Recording on a Linux based NAS: From a Windows machine run HDHomeRun Setup and enabled "Check for beta updates when checking for updates" on the Advanced tab. Switch back to the DVR tab and click NAS Install. The NAS Install process will download and install the latest beta release.

Recording on Android: The Android release will be out shortly.

To check things are working go to http://my.hdhomerun.com/ - check the the RECORD engine version is the latest beta (20190516beta2). All record engines must be upgraded.

Which record engine will record:

Generally whichever record engine has the most free space will do the recording.

If a record engine is already recording the channel and the new recording overlaps due to padding then this record engine will do the overlapping recording if it can. This allows a single tuner to be used for overlapping recordings on the same channel.

If a record engine reaches its concurrent stream limit then another record engine will take over additional concurrent streams. The default limit is 16 for Windows/Mac/Linux/BSD.

Advanced notes:

The StorageID in the conf file must be specified (and must be unique). The record engine will automatically create and add a StorageID to the conf file if it has write access to the file.

To limit the number of concurrent recordings set RecordStreamsMax in the conf file (on Windows, in the registry in HKEY_LOCAL_MACHINE\Software\Silicondust\HDHomeRun\DVR as a DWORD). Once this limit is reached another record engine will take over additional concurrent recordings. The default/max is 16.

signcarver
Expert
Posts: 8128
Joined: Wed Jan 24, 2007 1:04 am
Device ID: 131B34B7 13231F92 1070A18E 1073ED6F

Re: NEW - support running multiple record engines as a pool

Post by signcarver » Thu May 16, 2019 5:59 pm

Do all (updated) engines take into account what other engines have when it comes to determining if it has already been recorded?

nickk
Silicondust
Posts: 15520
Joined: Tue Jan 13, 2004 9:39 am

Re: NEW - support running multiple record engines as a pool

Post by nickk » Thu May 16, 2019 6:01 pm

signcarver wrote:
Thu May 16, 2019 5:59 pm
Do all (updated) engines take into account what other engines have when it comes to determining if it has already been recorded?
Yep :)

Beerman
Posts: 1430
Joined: Thu May 21, 2015 7:05 pm

Re: NEW - support running multiple record engines as a pool

Post by Beerman » Thu May 16, 2019 6:57 pm

Can you choose the primary drive to record too? And, once installed, can it be set back to just one Record engine.

nickk
Silicondust
Posts: 15520
Joined: Tue Jan 13, 2004 9:39 am

Re: NEW - support running multiple record engines as a pool

Post by nickk » Thu May 16, 2019 7:15 pm

Beerman wrote:
Thu May 16, 2019 6:57 pm
Can you choose the primary drive to record too? And, once installed, can it be set back to just one Record engine.
There isn't a primary record engine as such.

You can add or remove record engines at any time. To remove a record engine while keeping the recordings sorted by that record engine you just need to copy the files to one of the remaining record engines.

Nick

signcarver
Expert
Posts: 8128
Joined: Wed Jan 24, 2007 1:04 am
Device ID: 131B34B7 13231F92 1070A18E 1073ED6F

Re: NEW - support running multiple record engines as a pool

Post by signcarver » Thu May 16, 2019 7:46 pm

Along such notes, instead of moving content over, is a "null" entry first in the RecordPath to indicate a storage only engine still permissible? Would it be "better" to define 0 as the max stream limit (or was 0 for no limit)?

Beerman
Posts: 1430
Joined: Thu May 21, 2015 7:05 pm

Re: NEW - support running multiple record engines as a pool

Post by Beerman » Thu May 16, 2019 7:54 pm

I've got it installed and have both a Synology and QNAP but after installation, I see this:
https://imgur.com/KqsDpuW

nickk
Silicondust
Posts: 15520
Joined: Tue Jan 13, 2004 9:39 am

Re: NEW - support running multiple record engines as a pool

Post by nickk » Thu May 16, 2019 7:57 pm

Beerman wrote:
Thu May 16, 2019 7:54 pm
I've got it installed and have both a Synology and QNAP but after installation, I see this:
https://imgur.com/KqsDpuW
You need to run NAS Install from HDHomeRun Setup to upgrade the record engine on each NAS.
To get the latest beta (needed for this new feature) you also need to tick the beta option on the Advanced tab of HDHomeRun Setup before running NAS Install from the DVR tab.

Nick

Beerman
Posts: 1430
Joined: Thu May 21, 2015 7:05 pm

Re: NEW - support running multiple record engines as a pool

Post by Beerman » Thu May 16, 2019 7:58 pm

That worked-thanks!

DebbieFL33
Posts: 879
Joined: Sun Dec 20, 2015 4:17 pm
Device ID: 1318CAEB

Re: NEW - support running multiple record engines as a pool

Post by DebbieFL33 » Thu May 16, 2019 9:12 pm

signcarver wrote:
Thu May 16, 2019 7:46 pm
Along such notes, instead of moving content over, is a "null" entry first in the RecordPath to indicate a storage only engine still permissible? Would it be "better" to define 0 as the max stream limit (or was 0 for no limit)?
I have the same question...as my current setup is two engines with one using a null entry first in the record path. This setup has worked for the past several years to combine all of my recordings from two different NAS drives.

nickk
Silicondust
Posts: 15520
Joined: Tue Jan 13, 2004 9:39 am

Re: NEW - support running multiple record engines as a pool

Post by nickk » Fri May 17, 2019 6:48 am

signcarver wrote:
Thu May 16, 2019 7:46 pm
Along such notes, instead of moving content over, is a "null" entry first in the RecordPath to indicate a storage only engine still permissible? Would it be "better" to define 0 as the max stream limit (or was 0 for no limit)?
That is a good question. I think setting RecordStreamsMax=0 would be the best approach.

Nick

Bobstr
Posts: 93
Joined: Mon Oct 22, 2012 2:07 pm
Device ID: 131CCFEA, 1314A87C
Location: Seattle area

Re: NEW - support running multiple record engines as a pool

Post by Bobstr » Fri May 17, 2019 11:06 am

Great new add.

Thanks

marks
Posts: 116
Joined: Fri Aug 11, 2017 8:52 am

Re: NEW - support running multiple record engines as a pool

Post by marks » Fri May 17, 2019 1:53 pm

I agree, great new feature. Nice to know if I want to add a second NAS someday the HDHR DVR it will work on both.

I wonder for those who have NVIDIA shields if there can be multiple HDHR DVRs on those also. Since the forum announcement mentioned Android support would be added later for multiple HDHR DVRs I assume this would mean NVIDIA shield also.

demonrik
Posts: 1104
Joined: Mon May 04, 2015 10:03 am
Device ID: 10736454, 1073A35A, 1075C377

Re: NEW - support running multiple record engines as a pool

Post by demonrik » Fri May 17, 2019 2:11 pm

Cool to get this at last.
QNAP, Synology and Asustor packages all updated with new record engine, and for the new Parameter (and UI to set it)

Beerman
Posts: 1430
Joined: Thu May 21, 2015 7:05 pm

Re: NEW - support running multiple record engines as a pool

Post by Beerman » Fri May 17, 2019 6:51 pm

I need to do a little checking about but I noticed that after installing the multiple record engines I'm getting duplicate recordings in both NAS's. I obviously did something wrong.

Post Reply